Did you know that the value of facilitating retrospectives is also valuable at scale? In other words, facilitating cross-organizational retrospectives. Improvement is necessary to create better business outcomes. Relentless improvement should be a prime directive in every Lean-Agile organization.
In particular, if you are working within a Lean-Agile SAFe® portfolio you may be familiar with some of the following retrospectives. Others may not be so obvious. The point of which is that we should retro our performance for significant activities/ceremonies. When there are obvious bottlenecks in the system, do a retro, and use wisdom when this is not the case. And remember the easiest way to fail at a retrospective is to neglect to create improvement stories that make their way into the backlog.
Portfolio context:
- Team
- Iteration retrospective
- Daily Stand-up/Scrum retrospective (focus on this ceremony)
- Iteration planning retrospective
- Review/demo retrospective
- Backlog / Kanban system retrospective
- Program
- Iteration retrospective
- System Demo retrospective
- PI System Demo retrospective
- Program Backlog Workshop retrospective
- Inspect & Adapt Program Increment retrospective
- Backlog / Kanban system retrospective
- Large Solution
- Iteration retrospective
- Solution Demo retrospective
- PI Solution Demo retrospective
- Pre-PI Planning retrospective
- Post-PI Planning retrospective
- Solution Backlog Workshop retrospective
- Inspect & Adapt Program Increment retrospective
- Backlog / Kanban system retrospective
- Portfolio
- Portfolio Backlog Workshop (aka Epic Review & Specification Workshop) retrospective
- Lean Portfolio Management retrospective
- Value Stream Workshop retrospective (Yes, the enterprise should have a regular cadenced workshop to evaluate and/or re-evaluate value streams)
- Backlog / Kanban system retrospective
blogagility.com 