LACE (CCSQ Lean Agile Center of Excellence)

Page tree

Versions Compared

Old Version 21

changes.mady.by.user Louis Fouejieu

Saved on

compared with

New Version 22

changes.mady.by.user Louis Fouejieu

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


Iteration Review

Foundation 
    • Timebox: 1-2 hrs/2 weeks iteration 
    • Purpose: Provides the true measure of progress by showing working product increment 
    • Attendees: PO, SM, Agile Team, and stakeholders invited by the PO 
    • Facilitator: SM or PO 
    • Preparation:  
      • The review is prepared as a team (PO & team) to avoid PPT presentation in favor of demoing in a staging environment. If necessary, consider adding a ticket to the team backlog for review preparation 
      • Agree on the DONE stories/enablers to be demoed, their order of presentation, and the presenter 


Meeting Flow
  1. Review business context and Iteration Goals 
  2. Demo and solicit feedback on each Story, spike, refactor, NFR 
  3. Discuss stories & enablers not completed and why 
  4. Identify risks, impediments, and share any insights that could impact a future planning/release 
  5. Revise team backlog and Team PI Objectives as needed 
Recommended Practices
  •  Invited Business stakeholders are present 
  •  The meeting is kick-offed by the PO who presents PI objectives addressed during the iteration with their corresponding iteration goals 
  •  Only DONE stories/enablers (passes DoD) are demoed in an environment similar to production if possible or as specified in the DoD 
  •  Agile team members are invited to contribute - to demo individual stories/enablers when independent business value 
  •  Business stakeholders are engaged: they are invited to provide feedback and share new insights 
  •  Remaining PI Objectives, PI scope, potential risks, and trade-off or reprioritization opportunities are discussed 
  •  The team's accomplishments are acknowledged by the invited stakeholders  
  •  The team is proud of their accomplishments and can celebrate 
  •  The team backlog is updated based on feedback and new insights collected 
  •  Stories/enablers not completed are moved to the backlog for reprioritization 
Notes from HCD Observations

Observation Day  

Duration: 1h

Attendees: Meaghan Hudak (SM), Rob Fay, Chelsea Brigg, Amy Castellani, Howard Montgomery, and Brandy Barnette


  • SM kicked off the meeting by asking who volunteer to demo
  • All team members demoed one after another
    • Team member demoed all their work including uncompleted work items
  • Questions were asked (mainly by 1 participant) and answered, and some dialogues took place between team membermembers
  • The PO/PM acknowledged the team's accomplishments and provided feedback at the end of the meeting
  • It was great to see each team member all team members participating in the demo
  • Opportunities missed:
    • Kicked Kick-off by presenting the PI Objectives or OKRs and team commitments or goals for the Sprint
    • Presents Present some of the metrics (burndown, CFD, ...) to show how the iteration went
    • Present insights from the sprint such as challenges, impediments, or blockers
    • Present all the stories completed that will be demoed
    • Provide an order of demofor the demo
    • Lack of PO/PM engagement => more a Demo than a Review!
  • Great presentations, good team enthusiasm, and energy: Team was proud of the work accomplished!

...