Exploring the new “Rock Crusher” from IIBA®
There are a few problems and gaps with agile that I have struggled with and the IIBA®’s new Rock Crusher is intriguing as it addresses them.
The Product Backlog source of requirements for a Scrum Team to select from; it’s owned, managed, maintained, and ordered by the Product Owner.
There are a few problems and gaps with agile that I have struggled with and the IIBA®’s new Rock Crusher is intriguing as it addresses them.
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!
This time on “More Agile Great Debates”: incomplete backlogs, improvements, “special” Sprints, people swapping, and cross-functionality.
Part 3 of my blog series covering “More Agile Great Debates” delves into five more debate topics that I hope will spark some conversations.
My previous “Great Agile Debates” have proven extremely popular, so I thought I would add to this body of knowledge with a new blog series.
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.
My clients ask: “How do we deal with Production Support issues in Agile when our Scrum Team supports both the product and its development?”
Ideally, your Scrum Team includes full-time people with the right cross-functional skills; but if you have part-timers, you’ll have problems.
There should be no “special” Sprints in Scrum. The goal of every iteration is to create a working increment that is potentially releasable.