Why?
- The team reflects on their own process.
- Inspect their behaviour and adapt for future iterations.
- Address any issues / tensions about previous iteration in order to begin the next iteration on a clean slate.
When?
- At end of Iteration (after the Iteration Review).
- Maximum one hour per week of Iteration length.
Who?
- Team Lead – Facilitates
- Business Analyst
- Developer
- Tester
- Relevant Stakeholders by invite only
Inputs:
Anything useful from the current Iteration.
Outputs:
- A maximum of 3 items to improve upon is best practice.
- The aim is to incrementally change how the team works together as a team in order to improve, not to start everything from scratch.
- Feedback from the end user and other relevant stakeholders.
Business Analyst Involvement:
- Share learnings from iteration with team.
- Ensure learnings are incorporated into future iterations.
BA Agile Framework 