How do resetting work boundaries and effective work flow decisions affect your Agile transformation? How do you expand the boundaries of your value stream? What’s the real cost of distributed teams? Where does the core decision making happen? All these factors can cause your Agile transformation to stall. Here’s why.
It’s been an exercise in scaling at Adobe, without using any of the major scaling frameworks. It doesn’t mean it’s been less effective. It started from grass root level. Find out how did it scale across multiple teams and products. Especially how the role of the Product Owner evolved from a feature council.
Many teams find it hard to sell the idea of addressing the technical debt to their Product Owner and management. Technical debt results in longer release cycles and higher maintenance costs. It makes responding to change very painful and slow. Here’s how you can use to highlight business impacts of the technical debt.
This is Leanpub bundle and it consists of four books that can help you do really useful and amazing Retrospectives. You’ll lean plenty of new ideas, tips, and techniques to become even more proficient.
Is it the knowledge of how Agile works? Is it experience in Agile? Or is it the ability to listen empathically, to listen without judgement or any agenda and with the ability to understand other person’s perspective? Here’s a very interesting take on this.
User stories are a very effective and useful medium to describe requirements. But we don’t need to be held hostage by user stories. If it doesn’t make sense to write user stories, then don’t. It won’t make you any less Agile and won’t take any of the Agile benefits away. And there’s no user story police, right? Mike Cohn describes a few scenarios where writing user stories is not, well, very useful.
What should a good Daily Scrum lead to? How about planning at a daily level and negotiation of the scope, internal and external impediments? And more? These discussions happen mainly outside the Daily Scrum, but the Daily Scrum is where these discussions come to surface. Find out more.
Pair programming has its critics. But have you really tried it? It’s not only useful for writing code, the concept of pair programming is as applicable to testing, analysis and even creating excel spreadsheet. What if you can learn pair programming technique without writing any code? Here’s a fun exercise that can help you do that.
AGILE, LEADERSHIP
Workflow Modes That Lead to Failure in Agile Transformation
How do resetting work boundaries and effective work flow decisions affect your Agile transformation? How do you expand the boundaries of your value stream? What’s the real cost of distributed teams? Where does the core decision making happen? All these factors can cause your Agile transformation to stall. Here’s why.
https://www.rallydev.com
How Scrum Adoption Went Viral at Adobe
It’s been an exercise in scaling at Adobe, without using any of the major scaling frameworks. It doesn’t mean it’s been less effective. It started from grass root level. Find out how did it scale across multiple teams and products. Especially how the role of the Product Owner evolved from a feature council.
http://www.agileforall.com
TEAM
How to Manage Technical Debt from a Business Perspective?
Many teams find it hard to sell the idea of addressing the technical debt to their Product Owner and management. Technical debt results in longer release cycles and higher maintenance costs. It makes responding to change very painful and slow. Here’s how you can use to highlight business impacts of the technical debt.
http://blog.co-learning.be
Supercharge Your Retrospective With these 4 Books
This is Leanpub bundle and it consists of four books that can help you do really useful and amazing Retrospectives. You’ll lean plenty of new ideas, tips, and techniques to become even more proficient.
http://www.benlinders.com
SCRUM MASTER
What’s the Most Critical Skill for Scrum Masters?
Is it the knowledge of how Agile works? Is it experience in Agile? Or is it the ability to listen empathically, to listen without judgement or any agenda and with the ability to understand other person’s perspective? Here’s a very interesting take on this.
https://www.inspectandadapt.com
PRODUCT OWNER
Why All Requirements Don’t Need to be User Stories
User stories are a very effective and useful medium to describe requirements. But we don’t need to be held hostage by user stories. If it doesn’t make sense to write user stories, then don’t. It won’t make you any less Agile and won’t take any of the Agile benefits away. And there’s no user story police, right? Mike Cohn describes a few scenarios where writing user stories is not, well, very useful.
http://www.mountaingoatsoftware.com
TEAM
Does Your Daily Scrum Lead to These 5 Discussions?
What should a good Daily Scrum lead to? How about planning at a daily level and negotiation of the scope, internal and external impediments? And more? These discussions happen mainly outside the Daily Scrum, but the Daily Scrum is where these discussions come to surface. Find out more.
http://blog.3back.com
TEAM, DEVELOPER
Learn Pair Programming By Playing a Game
Pair programming has its critics. But have you really tried it? It’s not only useful for writing code, the concept of pair programming is as applicable to testing, analysis and even creating excel spreadsheet. What if you can learn pair programming technique without writing any code? Here’s a fun exercise that can help you do that.
http://agilecomplexificationinverter.blogspot.com
Share this: