There are some interesting statements regarding the timeboxes of Sprints exacerbating dependency issues. Other than the anecdotal, what objective measures can you point to to support this statement?
Donald G. Reinertsen, author of Principles of Product Development Flow, highlights the benefits of batch reduction that Sprint timeboxes bring. With this fixed timebox, along with other areas such fixed number of people in a team, natural variability decreases. Would a better approach be to add Kanban to Scrum's Sprints or XP's iterations, for example, rather than replacing them with Kanban, as Yuval Yeret author of Holy Land Kanban (2012) suggests?
Thank you for sharing so many good thoughts, David!
Thank you very much David for providing insight on how to approach Dependency Management in a more simpler and Pragmatic way.
Glad you enjoyed it!
There are some interesting statements regarding the timeboxes of Sprints exacerbating dependency issues. Other than the anecdotal, what objective measures can you point to to support this statement?
Donald G. Reinertsen, author of Principles of Product Development Flow, highlights the benefits of batch reduction that Sprint timeboxes bring. With this fixed timebox, along with other areas such fixed number of people in a team, natural variability decreases. Would a better approach be to add Kanban to Scrum's Sprints or XP's iterations, for example, rather than replacing them with Kanban, as Yuval Yeret author of Holy Land Kanban (2012) suggests?