Capacity Driven Sprint Planning



  • I have recently taken over as Scrum Master for a team.

    I plan on implementing capacity driven sprint planning.

    The challenge is, we have several User Stories (that should've been classified as Tasks IMO) that have carried over into multiple sprints.

    Let's say I have 3 "User Stories" that each have spilled over into at least 3 continuous sprints due to their monolithic nature, vagueness of requirements, and inevitable expansion of work.

    Would my first task be to get the PO and team together to slice up these types of User Stories during grooming?

    It would seem that the first step in implementing capacity driven sprint planning would be to groom the backlog into items fitting the INVEST ideal, so that we can adequately fit items into the capacity.

    Am I on the right track?



  • I think you are on right track of breaking down the work items. Here is what you can do

    Option 1: If user stories are based on "business need", do not split them further. But create meaningful tasks from team's inputs. Based on the availability of each team member, create tasks that are achievable within 1 sprint. Ensure the "Definition of Done" for tasks and user story is defined in grooming meetings in agreement with Product Owner.

    Option 2: Create "Features" based on "business intent". Create sub user stories based on the "capacity" of the team. Every sprint team can size the user stories. Ensure that during grooming the team defines the criteria for "measuring the progress" of user story. For example, if team decides the user story size = 10points. Team agrees that every day they can make a progress of 0.5 point, then you can easily track the progress of work on daily basis.

    Hope this helps.



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2