Updated
What should executives stop doing to help their Scrum teams?
Stop overriding the people Scrum puts in charge of the work. According to the Scrum Guide, the entire organization must respect the Product Owner's decisions, and the Scrum Team decides who does what, when, and how. My take: also stop calling everything priority one, splitting people across teams, and asking for status reports.
What the Scrum Guide says
The Scrum Team is "self-managing, meaning they internally decide who does what, when, and how."
The Scrum Team is also "structured and empowered by the organization to manage their own work."
On the Product Owner: "For Product Owners to succeed, the entire organization must respect their decisions." Read the Scrum Team section of the Interactive Scrum Guide.
What I see in practice
In Second Team I wrote about the leader who says, “I’m too involved in the day-to-day stuff.” My advice was simple: spend that time building a real leadership team with your peers, not doing your team’s work.
Then let go of the how. From Delegate Outcomes: “Tell your team what needs to be accomplished and why, and then let them figure out the how.”
And look up, not down. In Align Peers I wrote that leaders who defend their own departments end up “trying to force alignment at the bottom that should have already existed at the top.” As I put it on my First Team page: “Dysfunction rolls downhill.”
Common mistakes
- Calling every project “Priority #1.” Teams pick whatever is loudest.
- Assigning the same person to several teams, so no team ever has its people full time.
- Naming a Product Owner who cannot say no (I call it a Product Owner Proxy), or overruling the real one.
- Telling the team how to do the work instead of what is needed and why.
- Asking for status reports. In Cancel Syncs I wrote: “You confuse reporting on work with actually doing the work.”
What to do this week
- Ask each of your direct reports for the top three priorities for the quarter. If the lists differ, agree on one list with your peers before the teams see it.
- Pick one cross-team dependency or shared person that has come up in recent retrospectives. Name the leader who owns removing it (smile, it might be you).
- Delegate one outcome instead of one task. Say what is needed and why, and let the team decide how.
FAQ
Can an executive cancel a Sprint?
The Scrum Guide says: "A Sprint could be cancelled if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to cancel the Sprint." If you think the direction has changed, take it to the Product Owner.
How does an executive change what the team builds?
The Scrum Guide says: "Those wanting to change the Product Backlog can do so by trying to convince the Product Owner." My take: bring the outcome you need and the reason for it, not a task list.
What should executives do instead?
The Scrum Guide says the Scrum Master helps with "Removing barriers between stakeholders and Scrum Teams." In Scrum Events Running, Delivery Flat, I wrote that a team can name a cross-team dependency in its retrospective, but cannot decide that another group changes its schedule. Only a leader can.