Product Owner: Meetings

Reading path for Product Owner

  1. Overview of roles by level
  2. Responsibilities
  3. Practices
  4. Meetings for the Product Owner
  5. Alternatives for the Product Owner
  6. Resources for the Product Owner

Related resources

 
Provide Feedback
Scope of the meeting Schedule Issues
Backlog Refinement 1-3 times weekly Discuss:

  • Progress and scope adjustments
  • Priority, sequence, capacity impacts

Where the backlog must be updated due to changing events during the iteration, update the backlog accordingly

  • Do everything possible to defer backlog adjustments until the next Iteration Planning Meeting
Iteration 0 Planning As needed, before a release Teams resourced and ready for iteration

MBIs, Features, stories align with vision

Features sequenced, acceptance criteria defined

Architectural issues identified

Team environment set up

Reporting and metrics established

See also Iteration 0 Checklist in Checklists
Iteration Planning Just before the first iteration The iteration backlog and committed list

Sizing, ranking, acceptance criteria

Needs of the team environment

Commitments

For details about the Product Owner’s responsibilities in this meeting, see Facilitate Iteration Planning Meeting and Conduct the Iteration Planning Meeting.

See also Iteration Planning Meeting Checklist in Checklists
Daily Stand-up (Team Progress) Daily Attend

Build awareness of the issues and impediments the team is experiencing when implementing value items (e.g., stories)

For more details about the Product Owner’s responsibilities in this meeting, see Daily Stand-ups.
Product Demonstration and Review Just after last iteration Progress on committed work

Stakeholder engagement

Acceptance of stories

For details about the Product Owner’s responsibilities in this meeting, see Conduct the Product Demonstration and Review.

See also Product Demonstration and Review in Checklists
Iteration Retrospective End of iteration Attend, if:

  • The Product Owner is not also a Product Manager or other manager “over” the team.
  • The team is secure enough to operate in an open, peer-driven way with the Product Owner present.

Participate like any team member (for details about team members’ responsibilities in this meeting, see Conduct Iteration Retrospective.