Scrum under pressure
Well, when the pressure is high, management quickly turns to old resources. So we cancel the sprint review session, the retrospective and let go of the sprint cadence. We still do plans and so do the daily stand-up. On top of this, just a stand up in the afternoon to determine the progress. And if that is not enough, a daily report via e-mail to the management.
I really felt sorry for my scrum master colleague. He was completely back in his project manager role, and with success. After the holiday, the goal was achieved and the panic was over.
Goal achieved, scrum died
Management was very complimentary; good commitment, being able to steer a lot, we were “in control”. The reaction of my colleague scrum master was also clear: “I NEVER want to work like this again. This has cost the team and me an unnecessary amount of energy ”.
Resuscitation
That is why we are now organizing a retrospective with management and team to see what we can learn from the past period. Of course we want to know which needs of management have been met who apparently fulfill our scrum method less well. However, we also want to look for more Agile ways to deliver the desired results with less energy.
Agile Manifesto as a retrospective tool
As a method we have devised to use the Agile Manifesto as a thermometer to plot the methods and to come up with more effective alternatives.

- Step 1: Silently write on sticky notes in 5 minutes the working methods that we have applied and that contributed to the success.


- Step 2: Place the notes on the left or right side of the Agile Manifesto (does this note suit People and interaction, Processes and tools, Working software, etc.)


- Step 3: Together see what we learn from the distribution. Can we come up with methods that yield the desired result with less energy (more Agile).
Curious what insights that will provide? Do you recognize this and how would you approach it?
Change guide at Lagant, now in the role of Scrummaster Coach.
