Help! My Team’s Sprint Backlog is Out of Control!
Mystery stories? No points, no details, no naming conventions, technical tasks, ad hoc requests… Help! My Sprint Backlog is out of Control!
A Sprint is a container for all the other events of Scrum, and is the heartbeat of the framework; the time-box for Sprints is 1-4 weeks.
Mystery stories? No points, no details, no naming conventions, technical tasks, ad hoc requests… Help! My Sprint Backlog is out of Control!
In the second part of my blog series on “Agile’s Great Debates,” learn about five more agile topics that people argue about and disagree on.
Not delivering a “done” increment at the end of a Sprint can cause many negative consequences. It’s a bad habit and won’t make anyone happy.
Technical Debt is often neglected, but it’s like building a house of cards – eventually, something will give, and it will all collapse.
My clients ask: “How do we deal with Production Support issues in Agile when our Scrum Team supports both the product and its development?”
There should be no “special” Sprints in Scrum. The goal of every iteration is to create a working increment that is potentially releasable.
So, you have a Scrum Team. But does your team have all the necessary cross-functional skills to get to a “done” increment each Sprint?
I can’t tell you how many organizations I have worked with that had employees who confused the Sprint Review with the Sprint Retrospective.
It’s easy to sink into a comfortable but bad or boring routine with your agile Retrospectives, but it doesn’t have to be that way. Learn how!
A “Definition of Done” is a commitment to deliver a working increment meeting defined quality criteria to ensure the increment is complete.