How much should we sharpen the saw?

This content is syndicated from Agile & Business by Joe Little. To view the original post in full, click here.

You probably know the classic story of the man sawing the tree. You walk up to him.

You: "How's it going?"
Sawer: "Wow. It's really hard. This is one big tree, and I have been working at it for hours now."
You: "Sounds tough. Why is it going so slowly?"
Sawer: "Well, this is hard wood. [He is still sawing.] (Puff.) And my saw has become dull. (Puff)"
You: "Why don't you take the time to sharpen it?"
Sawer: "Can't. (Puff.) (Puff.) I am in a rush."

And the point is that the sawer is not thinking well. He could easily have saved time by sharpening the saw.

But, they always feel that sharpening is taking too much away from doing 'real work'.

And the truth is that sometimes "they" are right about this.

So, how much team time should we allocate to 'sharpening the saw'? In Scrum, say.

Some of you will notice that I have a picture of Coach K above. Coach K, for those who don't know, is the ScrumMaster of the Duke Blue Devils basketball team. A real team. His team won the NCAA Championship last Spring (in what they call March Madness). And his team is #1 in US college basketball today, as I write this. And is undefeated. He is a very, very, very good coach.

So, if we use him, his team, his other coaches, his managers, his trainer, etc, etc, as an example, what is a reasonable allocation to "impediment removal" for one team? If you really want to win.

My answer in practical Scrum terms: one full-time person (ScrumMaster) on impediment removal per full-time team of 7 people is quite reasonable. Probably an under-allocation, but quite reasonable.

And I take the view that none of us has won the NCAA Championship yet (or our equivalent), so until we do, we have plenty of impediments to remove. (And by the way, our team members virtually always do not join the team with the same raw ability in our sport with which Coach K's recruits join his team.)

And I notice that Duke does not fire Coach K after they win the NCAA. And New England does not fire Coach Belichick after they win the Super Bowl. Just repeating at that high level is almost impossible. But again, I personally have never seen a Scrum team that could argue that it was the best team (or even thought that it might be), so this worry that we have 'topped out' seems like an issue not worth talking about for a long time.

Now, if the SM is not very good or if the organization or some other factor means that the SM's efforts will not increase team velocity, then maybe 1 to 7 is too high an allocation. But it is often the first job of the SM to learn how to remove impediments effectively, and to teach the organization (the managers) how worthwhile that can be. Those are the first two impediments, sometimes.

Doesn't this allocation seem reasonable now?

Leave a Reply

Your email address will not be published. Required fields are marked *

one × 1 =

There are 101 ways to do anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”



To explore how we can help you, please get in touch