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!
Unlike Projects, which are temporary endeavors, Products are like living things, with a full life cycle from inception to sunsetting; while a Product exists it should have a backlog.
Mystery stories? No points, no details, no naming conventions, technical tasks, ad hoc requests… Help! My Sprint Backlog is out of Control!
In this episode of “More Agile Great Debates,” I tackle five more topics: Generalist vs. Specialist, Quality, Canceling Sprints, and more!
In the fourth installment of my blog series on “More Agile Great Debates,” I dive into another five topics that people like to argue about.
Part 3 of my blog series covering “More Agile Great Debates” delves into five more debate topics that I hope will spark some conversations.
Technical Debt is often neglected, but it’s like building a house of cards – eventually, something will give, and it will all collapse.
The right way to write User Stories is from a user’s perspective, taking a thin vertical slice through all the horizontal system layers.
Without a caring, competent Product Owner, most products will fail to come to fruition, earn and retain market share, and evolve.
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 have long advocated that Scrum Teams have a “Definition of Ready”; if you don’t have one, there are many potential negative consequences.
A “Definition of Done” is a commitment to deliver a working increment meeting defined quality criteria to ensure the increment is complete.