If business analysis is where we come up with ideas, then product development process is the factory that makes the vision real. What did we take from agile and how is it different today from 15 years ago? The magic word of today is SCALE. And the king of Scale is SAFe.
This is a resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives. Retrospectives play a crucial role in software teams. They are the time specifically put aside to reflect on how the team is performing and what can be done to improve.
Diagrams are always useful focal points for starting discussions, and that's one reason I like using the starfish diagram for a retrospective. This particular retrospective technique helps people by getting them to reflect on varying degrees of things that they want to bring up, without having it fit into the black or white category of 'What Went Well' or 'Not So Well' so I think it scales a little bit better.
The retrospective timeline is a useful exercise for gaining a better understanding and a richer context for a particular retrospective. This means that this exercise becomes less useful when you do retrospectives more frequently and especially useful when doing a retrospective spanning longer periods or you run retrospectives less frequently.
