As a coach to one of the Scrum teams that I knew would get a boost from it and also knowing the continued friction between this Scrum team and their managers, I decided to introduce this to everyone over a free lunch-and-learn session. What did that lead to — the expected — some speculation, good questions and answers, and the need for a follow-up in-person session for the managers (without the team members being present).
As a next step, I did two things.
- As the Scrum team was quite keen to do this, they asked if they could initiate to create a first draft of the Delegation Board and perhaps at least brainstorm on some Key Decision Areas. And in the meantime, once their Coach (me) persuaded their managers on this amazing technique, the team would be ready by then to share this Key Decision Areas list with the managers. Of course we agreed that was a smart way forward.
- Then I had a one-to-multiple session with the managers, helping them understand that delegation was not about them losing control. We also worked on them understanding what it meant for them as managers and how it benefited their transformation into the agile world. Of course they had already googled up on Jurgen Appelo, visited the Management 3.0 website and read up a bit on the Delegation Board and Delegation Poker, but did need more convincing.
So then it was time for them to see this kind of self-organization in action.
The team was ready with its first draft of the board of Key Decision Areas that included:
- Selection of Tool – Project Management
- Selection of Tool – Dev and Test Stack
- Core Working Hours and Holidays
- Global Team Governance
- Hardware procurement
- Release planning
- Collaboration across upstream and downstream partners / teams – internal/external
- Team events planning and budgets
- and a handful more
We then brought out a Flipchart paper, put these key areas to the left side in a column using Post-Its and put out the array of seven delegation levels across the top.
With some managers persuaded, while some were still skeptical, I did manage to bring everyone together in the session with the following objectives:
- Agree on the delegation level for the already identified Key Decision Areas (using Delegation Poker) and
- Add / remove any Decision Areas we together didn’t agree on
How did we play Delegation Poker?
- Each player (in this case, members of both the Scrum team and the management team) was given a deck of seven Delegation Poker Cards each.
- A person picked a Key Decision Area and talked about the details around that area
- Each player chose one of the seven delegation cards privately, thinking and reflecting on how he / she would delegate the decision in that particular situation.
- When all players were ready with their decision, they revealed their hands.
- The players with the highest and lowest cards explained the reasoning behind their selection.
If there was no consensus yet after Step 5, then Steps 3 through 5 were repeated until consensus was gained and the whole team picked another Key Decision Area with Step 2.
The outcome made the Delegation Board look like this. Later the managers included two additional Key Decision Areas.
Learning and actions:
- Clear increase in the team’s ability to deliver with clear boundaries
- Transparent and collaborative agreements set the foundation to openness and building trust
- Collaboration with transparency strengthened
- Trust improved over time
- Greater insight into decision-making and boundaries
- Managers started to understand how this was not at all about losing control
- Together they stopped thinking of each other as team and manager, but instead collaborated as One team on the conflicting Decision Areas. If any doubts / questions, they were brought up openly in weekly meets.
- This empowerment was now viewed to be a reflexive relationship between both managers and the team
- In terms of next actions,
- The managers now want to take this up for use / experiment with their supervisors and perhaps 1 Vendor. And they invited the Coach (me) to help!
- The team is taking it to the next level by building a Delegation board with their Product Owner.
Have you used the Delegation Board? Or another tool to clarify roles and influence? Share your experience in the comments below!
3 thoughts on "How to make the Delegation Board work for your team"
Thanks Sarika for this excercise. this will surely be helpful during the ‘Forming’ stage of the team. This will reduce the length of ‘Storming’
I have also used your MindMap tech within my team which helped the team to know eachother and also respect each other more.
Congratulations Arika, what an amazing tool.
wondering if keeping the push for concensus if not reached initially is the best way to go to reach agreement in case. Decision inertia could be threatned. One alternative would be to define a decision protocol with the managers as a complement to delegation . I have found that decision making when left unhandled properly is one of those creepy hidden snakes that ends biting us hard and slows down organisational flow in general.
Comments are closed.