Keep up to date with every new upload!

Join free & follow LeadingAgile SoundNotes
Share
  • 4 weeks ago
Should You Limit the Size of Work Brought Into a Sprint? w/ Scott Sehlhorst & Andrew Young

Should You Limit the Size of Work Brought Into a Sprint? w/ Scott Sehlhorst & Andrew Young

In this episode of SoundNotes, we tackle the question of whether or not it's a good idea for the Development Team to limit the size of work brought into a Sprint. Many teams consider this to be a valuable practice during Sprint Planning or when creating a Definition of Ready. The goal is to make sure that the Development Team is not committing work into a Sprint that they cannot complete during the course of a Sprint. This often shows up as something like “Nothing bigger than an 8” (for teams using Fibonacci to estimate User Story Points). While this practice can be valuable for the Development Team, it also has an impact on the Product Owner and how they prepare work for Sprint Planning.
During the podcast, LeadingAgile SVP and Executive Consultant, Scott Sehlhorst and Senior Consultant Andrew Young talk with Dave about whether or not this practice actually helps and how it can become an impediment for the Product Owner who is trying to plan out work for the Release.
Note from Dave:

Comments