You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 4
Next »
For each : participants profiles, goals, cadence, responsible
- Ceremonies
- Team level
- Daily
- Iteration Review
- Retro
- Planning
- Train level
- PI planning
- I&A Week
- System Demo
Team Level
Ceremony | Goals | Attendees | Schedule | Owner | | Outputs | Tips! |
|---|
| Daily meeting | - Synchronize with your peers on your work today
- Explain you've achieved yesterday
- Ask for help if needed
| - Agile team members (mandatory)
- SM for facilitation (not mandatory)
- PO for inputs (not mandatory)
| | - SM for organization,
- Team members for content
- PO not mandatory
| Quick presentation from everyone | Jira tickets | Keep it short but you can have a 15' "after meet" in order to deep dive into some conversation if needed. |
| Sprint Review | - Review KPIs
- Review user stories delivered with live demo when possible
- Get feedback
| - Agile team members (mandatory)
- STK for feedback ( Product manager, managers + RTE, PM if appropriate)
| - At the end of every sprint
- 60' max
| - SM for organization,
- Team members for content presentation,
- PO for delivery
| - KPIs update
- Demo
- User stories DONE
| - Feedbacks from STK for improvements
- Priorities changes if needed
| Make it interactive with a live demo! And on the last day of the week, so it has a flavor of completion. |
| Iteration Retro | - Improve way of working
- Take actions and give feedback to management if needed
| - Agile Team members
- PO not mandatory
| - At the end of the sprint or before the sprint planning
- Between 60' and 90'
| - SM for organization,
- Team members for discussion
| Items well done, Improvements to do
| 2 concrete actions of improvement to implement next sprint into the backlog, with owners | No manager allowed in order to free the speech of everyone. Pushing the improvements into the backlog makes it really actionable |
| Planning | - Check capacity
- Plan next iteration
- Review dependencies and risks
| - Agile Team members
- Stakeholders if needed
| - At the beginning of every sprint
- 60' or more, as much as needed
| - PO for content
- SM for facilitation
| Next Iteration features and user stories understood and partially refined | Next Iteration features & user stories sized, refined and assigned
| Have your planning right after the weekend, to start with a fresh day |
| Refinement | Features presented and explained by to team members to split into user stories | - Agile team members (mandatory)
- PO for inputs (not mandatory)
- SM for facilitation (not mandatory)
| - Every week, to prepare for the next iteration(s)
| - PO for content
- SM for facilitation (not mandatory)
| - Next Iteration features explained by PO
- Questions from team members to be sure to fully understand the future priorities
| Next Iteration features & user stories clarified. Can be partially sized | The much you pre-sized US here, the less time you spend during planning |
