Moving ScrumNot to Nexus
I’ve read the Nexus Guide for more than 10 times.
I’m excited as it justified some of my own experience.
I think moving to Nexus is more easy than moving to Scrum for me.
One of my Scaled Scrum experience is a contracted project.
There are three Scrum team from three contractor.
The PO is from the Company.
I’m one of the Scrum Masters.
As I’m older than the other Scrum Masters, they give me a top hat:
- The Chief Scrum Master.
Yes, there is no Chief Scrum Master defined in Scrum.
Formerly, it’s ScrumNot.
We had Scrum of Scrums via con-call, and had Daily Scrum for each team.
Finally, what I want to share here are our special Sprint Review and Sprint Retrospective.
At Sprint Review, per my road show experiences in Microsoft DPE team, I coach the teams to held a road show style event for PO and stakeholders. There are 2 advantages:
1. It may not be possible to show all completed work in detail.
2. It moves the event from one of “verification of functionality” towards one of “delighting our users”.
There will always be a happy ending.
After the Sprint Review, the Sprint Retrospective consists of three meetings.
Of course, it’s ScrumNot formerly.
The first part is a happy lunch. There were always two or more round tables. Without exception, the big round table is for the Scrum Masters and senior developers of each team. During the lunch, we had an open discussion. That’s Chinese style social activities. The other developers also share the experiences each other.
Before we went to the real Retrospective, the attendees of the Big Round Table would held a formal discussion for the progress of the current Sprint, one of the Scrum Masters always went through the discussion results and ensured each comment being confirmed by attendees.
The second part consists of each Scrum Team holding their own Sprint Retrospective as defined in Scrum Guide. The issues from part one should be an input to the meeting.
The final, all the teams meet again. (This is also different from Nexus.)
Appropriate representatives from the Scrum discuss and agree on how to visualize and track the identified actions. During the discussion, the team members could help the representatives as requested or needed.
This is my own experience.
It’s ScrumNot.
It’s NexusNot.
But it works for me.
Of course, I’ll try to adapt my practices to follow the Nexus guide in the next project.
Any input will be appreciated!
Posted By Ching-Pei Li on 31 Aug 2015 10:28 PM
The final, all the teams meet again. (This is also different from Nexus.)
Appropriate representatives from the Scrum discuss and agree on how to visualize and track the identified actions. During the discussion, the team members could help the representatives as requested or needed.
Thank you for sharing your experience.
What you describe is not that different from Nexus, it's almost an exact copy:
"The final, third part is an opportunity for appropriate representatives from the Scrum Teams to meet again and agree on how to visualize and track the identified actions. This allows the Nexus as a whole to adapt."
Remember that it is more important to help the team find out what works best for them than to make them follow a rule. When you identify a deviation from a rule, think about what the purpose of that rule is, which value it supports (transparency, reduce of waste, risk mitigation etc.) and what dysfunction it is that causes the rule to be hard to implement. Then you have the key to improvement.
Posted By Ludwig Harsch on 01 Sep 2015 03:10 AM
Remember that it is more important to help the team find out what works best for them than to make them follow a rule. When you identify a deviation from a rule, think about what the purpose of that rule is, which value it supports (transparency, reduce of waste, risk mitigation etc.) and what dysfunction it is that causes the rule to be hard to implement. Then you have the key to improvement.
Thanks for your valuable feedback and input.
In the next few days, I'd like to share my experiences about Sprint Review for Scaled Scrum Teams. You will be appreciated to give me some valuable feedback.
Due to my poor English, I have to spend at least half a day to write a simple topic. ;)