“What’s the difference between velocity and performance with Scrum teams?” is one of the most frequently asked questions in my Professional Scrum Master classes. Velocity is just an indication of a development team’s ability to turn product backlog items into potentially-releasable increments each sprint. Velocity is not an indicator of performance because performance implies that […]
Thoughts, ideas, and inspiration for becoming more agile in your personal and professional lives by exploring the values and principles of Agile.
This post is part of the Scrum Whys blog series. “A product owner can be a member of only one Scrum team”“A product owner must compose every user story”“A product owner creates all of the requirements for a development team”“A product owner is the only person that should talk to our customers”“There are no business […]
‘Scrum Doesn’t Give You the Kitchen Sink’ is part of the Scrum Whys blog series. Pop quiz. Which of the following is the most accurate description of Scrum? Scrum is a comprehensive approach for product development, and it has the best patterns for success. Scrum is a set of recommendations that should be used as […]
“Why does Scrum require that you only have one person ‘own’ a product?”“Why do we have to be done with something in a month or less? That would make our testing process really inefficient.”“Why is everyone on a development team called a ‘developer’? Why is it called a development team anyways? My teams don’t build […]
Many Agile coaches believe they know best. They believe teams must follow a certain set of steps and do things a certain way, and if they do, those teams will be more productive, happy, and successful than ever. There’s a problem with thinking that way. That style of thinking is part of what got many […]