“The ideal work planning process should always provide the development team with best thing to work on next, no more and no less.”
(Full Story: Scrum-ban | Lean Software Engineering)
“The ideal work planning process should always provide the development team with best thing to work on next, no more and no less.”
(Full Story: Scrum-ban | Lean Software Engineering)
Because, when the discussions don’t occur, the technical group takes all the responsibility for the product: for what to build, when to build it, and for how to build it. And that means we have let the rest of the business abdicate all of their responsibility for their part of the product. That’s not the partnership agile promises us, nor is the transparency agile promises us.
(Full Story: When You Have No Product Owner At All)
Vision + Team as inputsProduct + Team Capability as outputsAn Initial Product Backlog that feeds into the Sprint CycleWithin the Sprint Cycle we have all the tasks that make up a sprint – planning, sprint backlog, product increment, sprint review, sprint retrospective, updated product backlog
(Full Story: A new and improved Scrum Diagram)