The Agile Manager's Role: Be the Slack
The Agile Manager's Role: Be the Slack
You can’t be creative when you are overworked or overburdened. Stress kills innovation, as does business. Your mind needs to feel free and unallocated.
Join the DZone community and get the full member experience.Join For Free
[Latest Guide] Ship faster because you know more, not because you are rushing. Get actionable insights from 7 million commits and 85,000+ software engineers, to increase your team's velocity. Brought to you in partnership with GitPrime.
In his book Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency, Tom DeMarco makes the point that you can’t be creative when you are overworked or overburdened. Stress kills innovation as does business. Little slack leads to little time to look around leads to little improvement. To be creative, your mind needs to feel free and unallocated, uncluttered even.
Thankfully, we have a solution.
We have more than one, in fact. Let me first tell you about the solution that this article is not about. You can introduce slack into your organization with regular slack time. There are numerous well-known examples of companies that do things like Fed-Ex days, time set aside for self-directed work, not allocated to Prioritized Product Backlog Items. Dan Pink once endorsed this approach. In line with this, I like what Dan has to say about what motivates knowledge workers.
However, there’s another solution to the lack of slack that we should entertain first. In fact, you are less likely to use FedEx days if you aren’t first doing the following. To introduce this, I must first point out something that Scrum says about managers. Scrum doesn’t say a whole lot about managers, but it does say at least this: mangers must stop assigning tasks. It's too bad that many managers get their power and sense of self-worth from this activity. Deciding how to get the work done in Scrum is left up to the self-organizing cross-functional team. The people who can best decide how the work should be done are those closest to the work.
Just to be clear, Agile managers should not:
- Make assignments.
- Hand out work.
- Direct people or tell them what to do.
- Make the hiring decision solo.
- SW architecture (in my opinion, this is debatable).
- Do work.
- Be an individual contributor.
- Be a hero.
Well, gosh, then what should a manager do? Well, I’ll tell ya. Manage more people. Step in when the team needs help (but not too quickly). Manage risks. Also, you are still an agent of the company, handling legal stuff, signing off on expenditures, etc.
However, you could also do something else.
Be the Slack
Move up to a higher level of value to the organization. Be the slack that has been wrung out of the team. Here are some specific suggestions:
- Keep an eye on the system, looking for improvements.
- Use A3 Problem Solving (A3 Thinking).
- Understand the capacity of the team.
- Protect the slack; protect capacity that is reserved for classes of work that require a short lead time.
- Ensure cross-training is happening — nnot by making assignments, but making the team handle it.
- Understand the dynamics of the organization.
- Understand how value is created.
- Protect the team from interference.
- Make the organization effective; learn to look at it as a system.
- Support the team.
- Clear roadblocks.
- Provide good facilities; fight the facilities police. (Better: Teach facilities how value is created and how better facilities help create value.)
- Provide ample computing infrastructure and sufficient build machines and test machines (people are far more expensive than VMs).
- Use Derby’s 14 essential questions for managers or the book on this topic that she is working on.
- Read Deming and Goldratt.
- Watch interpersonal interaction; watch when one team member withdraws in a brainstorm, for example.
- Help the team hone their craft.
- Encourage the team to learn TDD and BDD by making room for them to learn. Remove the schedule pressure while they learn.
- Think through policies, procedures, and reward and review systems and improve them. Consider what messages they send.
- Understand what motivates knowledge workers (see the previous reference to Pink). Let creating that kind of environment be an imperative.
I contend that we should focus on continuous improvement of process, of people’s skills, and of knowledge, with a strong focus on empowerment and self-organization. Work on open, honest feedback. You’ll have better results if you do all that and just completely scrap the individual annual review. I love quoting Drucker here: “The average person takes six months recovering from a performance review.”
Let me bring it back together by saying you can’t do a good job with this other higher value stuff if you are down in the weeds assigning tasks to people. Delegate more. In fact, delegate everything. Free yourself to be the ultimate in valuable slack.
Published at DZone with permission of Andrew Fuqua , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.