Should PO define execution order of stories in a Sprint?



  • In one scrum team, the PO expects stories to be executed in a defined order in the sprint. This PO usually arranges stories in top-down order and expects stories to be executed in the same order.

    I personally felt uncomfortable with this approach, believing the team should be given the freedom to decide the execution order for maximum productivity.

    1. Is it the right thing to do?
    2. Is there any downside of doing this?


  • No, the Product Owner shouldn't be defining the execution of work during a Sprint.

    At the Sprint Planning event, the Product Owner and Developers collaborate to craft a Sprint Goal, select Product Backlog Items for development, and the Developers create an initial plan for achieving the Sprint Goal and delivering the work. These three elements are the Sprint Backlog for the Sprint.

    The Developers are accountable for the Sprint Backlog. The plan is created "by and for the Developers". Although the Product Owner is involved in crafting the Sprint Goal and influences the selected Product Backlog Items based on ordering the Product Backlog, the Developers select the work, create the plan, and revise the plan at the Daily Scrum (and more frequently, if necessary).

    If the Product Owner is exercising control over the Sprint Backlog and the daily work of the Developers, that could indicate micromanaging and perhaps a lack of trust. It also indicates that the team is not self-organizing and self-managing.




Suggested Topics

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