Learn about purchasing for teams

Join Certified Scrum Trainer® John McFadyen for a 12-part video series exploring the scrum event known as the sprint retrospective. Throughout the series, he’ll share tips and tricks for creating impactful, engaging, and effective sprint retrospectives for your teams.
For tip #10, McFayden shares the Timeline retrospective exercise. This is one he’s used often over the years when wanting to explore the cause and effect of why things happen. The Timeline is great for understanding when something on the team may have broken down or when something positive occurred.
The timeline you create can be a sprint, a quarter, or even a year long. If you have a particular problem your team is trying to solve, go back to when you believe that problem began.
McFayden shares how he used this exercise with a team that was successful and doing great work, but they couldn’t understand why the code build would occasionally break. By putting a timeline together, they began to recognize the pattern of when a new person joins the team, the build breaks. This awareness led the team to discuss the problem openly without placing blame. They discovered that they needed to alter the onboarding process so new team members understood their process.
While this team was already high-performing, they knew there was still room for improvement. By going through the Timeline activity, they were able to solve a problem that wouldn’t have easily been solved.
The Timeline exercise is simple to facilitate. By using different color sticky notes for each role or part of the process, pattern recognition is easy to spot. The product owner may use purple stickies to indicate actions, whereas a tester might use another color.
The Timeline retrospective is a great activity if you want to look back at the end of the year or to solve a particular problem.
Key Takeaways: