Category: Scrum 101
Why Scrum Doesn’t Give You the Kitchen Sink
‘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…
5 ways an agile team manager can improve velocity
A common question we hear from managers and senior leaders is how they can improve the velocity of their development teams. Many agile professionals redirect that manager’s attention to attributes other than output, commonly toward value, because they assume the wrong question is being asked. I totally agree one has to examine the value a…
The ‘Scrum Whys’ Blog Series
“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…
There is just One Shocking Thing Many Agile Coaches Are Getting Wrong
Many Agile coaches and Scrum Masters 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 is just One Shocking Thing Many Agile Coaches Are Getting Wrong. There’s a…
Three Dysfunctional Sprint Burn-Down Charts of Scrum Teams
Why use a Sprint Burn-down chart? A Sprint burn-down chart is a great way for a team to measure their own progress in a Sprint. It helps to maintain a sustainable pace by visualizing progress. It helps to pay attention to finishing rather than starting work. And it helps produce team level transparency, much like…