Agile

Software Teams can Jump

14 Comments

For many years I’ve been coaching software teams in various things such as Example Driven Methods (xDD), including BDD and TDD; pair-programming; programming; testing; retrospectives; Scrum, kanban and various other ways of getting the most out of a development team. One thing that I notice is that while the teams are being coached, they do amazing things. They are more happy, more productive, fast to improve as if there are no limits to what they can achieve.
Michael Jordan, Blue Dunk, Lisle, IL, 1987
Then, at some point they decide that it’s time to go it alone. I always say to my clients to keep at least one day in their budget for me to go away and come back some time later. Usually within a month or two to see how things are going. Inevitably when I return, the team is doing reasonably well, but not as well as if I’d stayed involved, even if I was just popping in once every couple of weeks.

Some say that this is what the Scrum master is there for, however, I’ve noticed that this is something that the Scrum master doesn’t get to do much of as they are are often dealing with external pressures “to get things done”…

On many teams, once I move on, there is a coaching void. Despite my pleas and efforts to encourage them to at least establish a coach from someone in-house, the team is often left to just get on with it.

This isn’t a new idea. For example, Extreme Programming highlights “the coach” as a key role in the team.

In sports, teams have coaches. Have you ever heard of a professional sports team without a coach? Can you imagine a professional sports team hiring a coach for a while and then saying – “we think we’re ready to compete on our own now so thanks for your help but you’re not needed anymore”. No, I don’t think so. This is unheard of in competitive sports, yet all too common in competitive business.

Even my 12 year old son’s basketball team, the Islington Panthers, has a coach. He trains them 2-3 times per week and he (or an acting coach from the seniors) attends all of their games. In some training sessions he gets a member of the under 21s team to coach the under 13s training session – so there is always a coach even if they’re just borrowed from another of the club’s teams. Without him, do you think any of the club’s teams would make the national play-offs as they regularly do? Very unlikely.

So, competitive sports teams always have a coach. Temporary coaching in a professional sports team is almost unheard of… Sure, they could get by but would they be taken seriously? Would they be competitive? Would they save money by not having a coach or would this be an obvious false economy? What are their chances of generating sponsorship revenue if they are not winning games? What are their chances of winning games without a coach?

The same applies in software teams. For example, I worked with a client recently and helped a team of 6 people double their output in one day. They’d have to hire another 7-10 people in order to achieve that but instead, one good coach was enough.

So, if you have a professional software team without a coach, consider, are you really helping your business save money by going it alone? Or, like the professional sports team, is having a professional development team without a coach another example of a false economy.

 

  • Very insightful. There should be a more straightforward and accessible way to “become” coach, IMHO – for those of us that feel they have what it takes to do so, and would love the challenge.

  • Thanks for the feedback Stefano.I’m not sure that it’s very complicated to “become” a coach… But like anything else, to become good at it takes learning, practice, experience, reflection and more learning. You’re probably doing some coaching already… you might not realise it yet.

    I fell into coaching by accident. I happened to have a lot of experience in Agile when it started to become popular and coaches were hard to find so I was asked to coach a team of beginners. At first I wasn’t very good at coaching but I learned from experience and from a great mentor – Rachel Davies.Whether I’m any good now, I’ll let others decide.

    I’ve been particular to maintain my technical skills development and my appreciation of the daily challenges teams face by working as a team member on real projects for at least a quarter of the year… Not to mention background projects like JNarrate and CukeSalad. I’ve also developed my coaching skills through practice, reflection, feedback, reading and workshops. This combination allows me to move comfortably between more directive coaching to more non-directive coaching – see this post:http://agilecoach.typepad.com/agile-coaching/2010/10/agile-coaching-zone.html

    Today there are great resources that weren’t there when I got started. There’s Rachel Davies and Liz Sedley’s superb book on Agile Coaching – http://pragprog.com/titles/sdcoach/agile-coaching(Which I’m honoured to have made a small contribution to)Rachel helps to organise the Agile Coaches Gathering where anyone who registers is welcome http://www.agilecoachesgathering.org/

    Rachel also has an excellent blog http://agilecoach.typepad.com/ A google search on “Agile Coaching” returns a whole host of resources, including Lyssa Adkin’s book on Agile Coaching… 

    There’s so much to read and absorb now that you can avoid having to learn many of the lessons the hard way as I did.

    Best of luck on your journey.

  • Have you ever heard of a self-organising professional sports team? Have you ever heard of a successful professional sports coach who doesn’t impose rigorous hierarchical structures, often supported by draconian ‘club rules’ and fines?

    And to ask another question: how many software coaches do you know who are the first in line to be fired if their team fails to deliver against short-term goals?

    Your analogy and the conclusions you draw from it are fundamentally flawed. Professional sports teams play very simple physical games and benefit from constant drilling, simplistic instruction and very little intellectual consideration. That sound like many software teams you know?

    It sounds like you’ve done some good work as a coach – that’s great to hear. But your conclusion that a professional software team without a coach is inefficient or in some way flawed is extremely wide of the mark.

  • Hi Paul,

    Thanks for your feedback 🙂 Somehow my words have allowed you to misunderstand my point and read far beyond my actual words… So I’ll try to address the misunderstanding…

    “Have you ever heard of a self-organising professional sports team? Have you ever heard of a successful professional sports coach who doesn’t impose rigorous hierarchical structures, often supported by draconian ‘club rules’ and fines?…”

    The message I tried to convey was that successful pro sports-teams /have/ coaches… and the most successful software teams I’ve worked with /have/ coaches. 

    That’s as far as the metaphor goes… I’m not saying anywhere in this post that software-teams or their coaches should behave in the same way, or use the same coaching techniques, or be organised in the same way. I hope I’ve addressed that misunderstanding.

    “But your conclusion that a professional software team without a coach is inefficient or in some way flawed is extremely wide of the mark.”

    I can kind-of see how you might infer that this was the conclusion but I’m not making that assertion at all.

    The key take-away from my post should not be a conclusion… but a question… “By not having a coach, are we saving money or is it a false economy?” For some it will be a saving, for others it will be a false economy… In my experience, it’s more often the latter.

    For the record, a professional software team without a coach is not [inherently] inefficient nor are they [inherently] flawed. However, in 16 years in the software industry and 11years of ‘Agile’ projects (as a team member or a coach or both), my experience has been that  even the best teams without a good coach can be even better with a good coach.Sometimes that coach comes from the outside… other times they are found within… And on the most elite teams I’ve been on, everyone does a little coaching – depending on each person’s area of expertise… and even then an outside coach visiting periodically brings a valued fresh perspective.

    I hope you better understand the message I was trying to convey.

    Best regards

    Antony

    🙂

  • Thank you for the clarification – I now understand better the message you are trying to convey 🙂

    Perhaps I could offer an alternative message? I’ve worked in and with extreme programming teams since 1997 and not one of them had someone identified as ‘the coach’ or ‘a coach’. There was a lot of learning and improvement driven from within the team, but that’s the standard emergent behaviour of self-organising teams: there is not ‘a coach’ just a team working and continually improving. There was also a lot of learning and improvement coming from outside the team, as the result of reading about or hearing from other teams, sharing experience and so on. But never was some individual hired or identified as ‘a coach’.

    Could those teams have benefited from doing so? I honestly don’t believe so.

    You see I believe there’s a contradiction in your message: in the “elite teams” where “everyone does a little coaching” there *is no coach*. There is a self organising team with emerging behaviour and a focus on continual improvement. Bringing in an external coach may bring a valued fresh perspective, or may just prove disruptive and distracting. Either way, a focus on self-organisation and self-determination has, in my experience, far more influence on the efficiency, ability to learn, rate of improvement and general social wellbeing of a team than the presence or absence of a coach.

    Best,

    Paul

  • Thanks for your comments Paul. They are really valuable…

    I accept that it is possible that there would have been no value in any coaching for any of your teams… but from what you tell me, there was lots of coaching… from inside and outside of them…

    With your extensive experience in XP, I suspect that you have frequently adopted the role of “coach” without even realising it. It was just something that you did without labelling it… And for you there was no need for a label. It was just what you did to help others around you learn… 

    For others, the labels help them to slice up the areas in which they can develop their skills (à la Ambler’s “generalising specialist”)… For me, coaching was one of those areas – along side programming, architecture, testing…etc.

    I can see where you are coming from regarding the title of “coach”… I’ve worked with successful teams where there was no one with the title of “Tester”. People would switch seamlessly between programmer, architect, business-analyst and tester all in the blink of a red-green-refactor cycle. I see the same happen where people seamlessly switch into the role of “coach” – even though there is no one on the team with that as a title.

    My blog post wasn’t really about anyone having the title of “coach” it was about the value of “coaching” in my experience.

    The pro-sports team analogy was a way of showing how “normal” it is for us to see coaching as something that is invaluable. So much so that a pro-sports team wouldn’t be without someone “coaching”. Again, it wasn’t about having someone with the title of “coach” but was about the perceived value of coaching.

    So, do you still believe that coaching did not happen on your teams or was your objection only about the title?

    I hope your objection was just about the title… Otherwise we have one person with extensive experience of only non-coached teams apparently saying there is no value in something he has never experienced… While another person with extensive experience of both coached *and* non-coached teams is saying he has seen value in the same and it is something he has experienced 🙂

    I suspect we are actually in violent agreement on the principles but just bouncing off the terminology of “roles” vs. “titles”.

    Best regards,

    Antony
    🙂

  • You know its funny, you’re the second professional coach I’ve had this
    discussion with who has accused me of violently agreeing with them.
    Either I’m not very good at putting my point across or you guys are so
    attuned to conflict resolution that you find it hard to spot when
    someone is genuinely disagreeing with you 🙂

    But lets start with what we agree on: in all good teams people learn
    from each other all the time. On the teams I worked in sometimes I
    brought something new that helped others, sometimes it was others
    helping me. If you want to call that team learning activity ‘coaching’
    then fine. Personally I prefer ’emergent behaviour’ because it is less
    directed (and given your partnership in PairWithUs I’m sure you
    understand the difference between coaching someone towards an outcome
    and discovering the outcome together) but lets not argue about nuances
    of terminology.

    Then there is having ‘a coach’ – something I generally object to (and
    your article is about having ‘a coach’). This is more than just titles,
    although in a sense it *is* about the title; its about role and its
    about responsibility. The wonderful thing about XP and the old-school
    agile approaches was their emphasis on a ‘whole team’ delivering
    software. In an XP team, as I’m sure you know, the whole team works
    together with a common goal – deliver valuable software to the customer –
    and you succeed as a team or you fail as a team. Then along came scrum
    with its concept of Scrum Master (a certified qualification no less)
    and, latterly, a whole slew of people who describe themselves primarily
    as coaches … people whose role it is to ‘facilitate’ the process, to
    ‘support’ the team, to ‘coach’ the individuals. People whose goals are
    not aligned to the rest of the team who are working to deliver software.

    But of course most coaches will say “Our goals ARE aligned. We help the
    team to improve and by improving they get better at delivering
    software.”.

    “We … and they”. All of a sudden the whole team isn’t so whole.

    Or they say “But I’m just part of the team”. Fine, so be part of the
    team. Be responsible for delivering software and contribute to the
    emergent behaviour by doing so. But don’t come with the title, or the
    role, or the responsibility or even the attitude of being ‘a coach’.

    Just because the teams I work in or with don’t have coaches doesn’t mean
    I have no experience of coached teams. I used to run a business that
    specialised in rescuing failing projects, usually brought in by the CEO
    or CIO equivalent when a team wasn’t delivering to their business goals. In the
    early days these were always waterfall style projects but from ~2005
    onwards we saw plenty of failing agile projects with coaches and masters. I’m
    not saying that all, or perhaps even any, of these projects failed
    because of the coaches but I have seen how badly applied coaching can be
    disruptive and thoroughly unhelpful.

    So my view is simple: software teams should delight in the fact that,
    unlike pro sports teams, they can excel without a coach. It’s not about
    saving money but about allowing the team to self-organise and behaviour
    to emerge… something that sports teams cannot do … which makes the
    software team all the stronger. Anyone who relies on a software team for
    their competitive advantage should really think hard about having
    someone working with the team whose goals are not aligned. If a team
    *really* feels they need some outside coaching to improve in a specific
    area they can’t, for some reason, cope with internally then make it a
    temporary and specific engagement with very clear deliverables.

    I hope where we disagree is clearer now 😉

    BTW, I do seem to have somewhat hogged your blog comments, my apologies for that.

    Cheers,

    Paul

  • Hi Paul,No problem about this discussion taking up the comments. I think this is a valuable debate and I think anyone reading the comments will be doing so because they want to… And they will only want to continue reading if they are gaining value from the discussion 🙂

    Ok, I accept that we have a difference of opinion. I acknowledge the validity of your opinion in the context of your experience. I hope you can acknowledge the validity of my opinion in the context of my experience.

    There is some agreement between our experiences and there is some disagreement between our experiences. I.e. our experiences have some things in common and some differences.

    The agreement between experiences includes the fact that teams can excel without someone labelled or named as a coach. The disagreement between our experiences appears to be that I have experienced teams excelling even more with good coaching (whether anyone happens to carry that label or not) than without and you appear to not have had that experience. 

    It seems that because you’ve not had that experience you reject the idea that it is possible… If that is the case then I will say that you and I fundamentally disagree as I have seen it happen and therefore know that it is possible. 

    If you accept that it is possible but reject the idea that it is likely and assert that most of the time good coaching on a team will make no difference to the pace at which most teams can grow it’s excellence then, I can neither agree nor disagree… I’ll only say that this is not consistent with my experience.

    I’d like to highlight that the nature of the work involved in saving failing projects is more likely to bring you closer to people doing a bad job of coaching than a good job. Combine that experience with the fact that you’ve not experienced any positive effects of someone knowingly coaching on a team and it might be worth asking yourself whether you are prejudiced against coaching and thus biased against anything I might say in favour of the idea. And, if that is the case, it might be that you are closed minded to learning anything from anything I have to say on the subject… and if that is the case further discussion is probably of little value to you.

    As someone who values shared discovery and learning, as I do, I hope you are open minded to the fact that just because you haven’t experienced something – doesn’t mean it isn’t possible.

    Because of my positive experience with people knowingly coaching, treating it as a legitimate skill-area (just like programming or testing or design), I admit that I may be biased towards the idea of good coaching adding value to a team… But because of that experience I reject the assertion that it *cannot* have a positive effect on the a teams growth and excellence and this is perhaps the basis of of our disagreement. You seem to be asserting that it makes no difference.

    And I think that maybe our understanding of roles is different… When I talk of roles, I think of it more in the dynamic sense… 

    “Roles on a mature XP team aren’t fixed and rigid. The goal is to have everyone contribute the best he has to offer to the team’s success.” XP Explained, 2nd Edition, Beck, Andres

    In this sense, people switch into and out of roles dynamically and seamlessly. This is the situation you appear to be accustomed to and, perhaps, you are at the point where labels have become meaningless to you because you are able to perform all the roles on an XP team and apparently work with others who are as experienced as you and never have anyone on any of your teams for whom the labels are useful…

    “At first, fixed roles can help in learning new habits, like having technical people make technical decisions and business people make business decisions. After new, mutually respectful relationships are established among the team members, fixed roles interfere with the goal of having everyone do his best. Programmers can write a story if they are in the best position to write the story. Project managers can suggest architectural improvements if they are in the best position to suggest architectural improvements.” (continuation of Beck, Andres quote above)

    And it sounds like the latter part of this quote describes where you, and the teams you tend to work with, happen to be… the context you spend most of your time in.

    I spend my time in a variety of contexts. I spend time in a) teams just like that and b) in teams where people need fixed roles… and c) in teams transitioning from the latter to the former. In all of those situations, I’ve seen good coaching, appropriate to the maturity of the team add value. 
    See “Adapting your Coaching Style” by Rachel Davies http://agilecoach.typepad.com/agile-coaching/2010/10/agile-coaching-zone.html

    Also, in all cases, I’ve seen value in recognising and labelling the various skill areas that bring value to the team doing its best in both sustainably delivering products that matter and continuously improving how they do that.

    Programming, design, testing, coaching and so on are such labels. This is where the labels are useful – not as titles but as skill-areas that each person may wish to focus their personal development to improve the team’s capability.

    My article was indeed about teams having someone coaching. It was not my intention to imply that you need someone who is labelled as a coach.

    There is a significant flaw in one of your arguments against coaching… Your suggestion that “along came scrum with its concept of Scrum Master (a certified qualification no less) and, latterly, a whole slew of people who describe themselves primarily as coaches … people whose role it is to ‘facilitate’ the process, to ‘support’ the team, to ‘coach’ the individuals. People whose goals are not aligned to the rest of the team who are working to deliver software.”

    It sounds like you are saying that all was right with the world while we were doing XP and then when Scrum became more popular, it ruined everything by introducing coaches… Yet, in XP Explained 1st edition, Kent Beck lists several roles: programmer, customer, tester, tracker, *coach*, consultant and big boss. So, if you want to blame any approach for the existence of coaches, perhaps it’s better to blame XP than Scrum.

    You also say ‘But of course most coaches will say “Our goals ARE aligned. We help the 
    team to improve and by improving they get better at delivering software.”‘ 
    Firstly, this is what you might hear from a team where there are fixed, labelled roles… and by contrast you might also hear a programmer say “Our goals are aligned. We help to implement the code that makes the customer’s vision a reality”.

    Secondly, whether the role is labelled or not, the goals of someone doing a good job of coaching is always aligned with their fellow team members (assuming that those goals are about sustainably delivering the products their customers need/want and continuously improving the quality of that service).

    Thirdly, when a team recognises a weakness and calls in someone external to help, I would use the 1st Edition XP label of “Consultant” for that service, not the label of “Coach”. And I would say that I have seen teams realise that they need that help sooner with the help of someone “coaching” than when the team has no-one coaching them.

    Fourth, in my experience, the satellite view reveals things that the ‘troops on the ground’ will often not see. The person coaching from this perspective can sometimes just be a colleague from another team… or someone on exchange or visiting from another organisation doing similar things… or from a new team-member who has joined or rotated into the team… or from a person like me who is retained explicitly as a “coach”.

    And, finally let’s focus on teams, delivering stuff and the things that help them do that well, with ever-improving efficiency and effectiveness.I have experienced the positive effects of things that I label as “good coaching” on teams, sometimes performed by a person labelled as a coach, sometimes from people without a label. You cannot disagree with that experience because you are not me and have not had my experience. You can say that you have not had that experience or that you have had a different experience.

    I have experienced the value of recognising the skills areas that add value to a team so that we can use labels for those skills areas to target the skills development of the team. Again, you cannot disagree with that experience… You can however, have had a different experience where being able to recognise and articulate with a label that you solved a problem using something, say meta-programming, is of no value to help direct your learning or the learning of your team mates. To me, coaching is just another such label.

    But I accept that you might disagree with my assertion that ongoing coaching can deliver value to a team… and in that regard… I am more than willing to agree to disagree… I cannot agree with a statement that essentially says that something I’ve seen and directly experienced didn’t happen.

    Best regards,

    Antony

  • P.S. “I’d have written a shorter letter, only I didn’t have the time” – Various
    🙂 

  • P.P.S. Paul, I hope my last significant comment addressed the key points of our disagreement and refined our understanding of that disagreement further…  It’s occurred to me that you are not really the target audience for this article. “Experts” (à la the Dreyfus Model of Skills Acquisition) generally find maxims and rules frustrating because an expert knows they don’t always apply. 

    So, I guess the intended audience was the teams that drop any form of coaching way before they are ready because a manager somewhere wants to save money… not because the team elects to go it alone.So, the expert version would contain the sorts of things in my most recent comment to you… Essentially saying that I’ve found ongoing coaching valuable and I’ve seen value in recognising coaching as an area to develop skills in within the team… and that finding someone with those skills to come in periodically and tell you what they see from the satellite view can help you spot things that the team might not see.

  • Hi Antony,

    a comprehensive and insightful response which I’d love to respond to in detail. But I’m going to resist … partly because I don’t have time to write a long letter, let alone a short one right now but mostly because I think detailed point-and-counter-point discussions are best done face-to-face. Maybe we’ll meet one day and can have that discussion.

    Instead I’m going to step back and try and explain the context in which I make my comments so you can see where I’m coming from. I’ve read your article four or five times now and it really is about having ‘a coach’ (specifically you in most cases). A labelled individual with an identified role:

    “If you have a professional software team without *a coach*, consider …”

    “Competitive sports teams always have *a coach*. Temporary coaching in a professional sports team is almost unheard of”

    “On many teams, once *I* move on, there is a coaching void.”

    “I always say to my clients to keep at least one day in their budget for *me* to go away and come back some time later”

    You’re absolutely right when you say you are asking questions rather than offering conclusions, albeit with a bias based on your experience that having ‘a coach’ is a good thing, and what I’m doing is positing a different set of questions with a bias based on my experience.

    Why?

    Two things make me feel uneasy about the growing ‘cult of coaching’. The first is that I’ve seen many teams thrive without ‘a coach’. Yes, Kent had coach down as a role in his first edition – I don’t blame him, he’s American, they see the whole of life as a sports metaphor – but none of us who started out in the early days took that too seriously. We couldn’t really because there were no coaches to call on; we all had to make our own discoveries and mistakes. Different teams talked to each other and learned from each other but I can’t remember a single one appointing a coach from inside or outside. And those teams all did great things partly, I believe, because their behaviour and learning emerged as a result of self-organisation and experimentation. 

    [As an aside: some of the best-known coaches emerged from those teams and I wonder whether they are so well-known and talented because they have just been around for longer or because they got so much from learning it all for themselves?]

    As soon as you appoint ‘a coach’, no matter how experienced and talented, how well-meaning and adaptable, some of that self-organisation and emergent behaviour goes out the window. Its human nature: even in a team of experienced peers, identify someone as ‘the coach’ and the team look to them for guidance. Remove that person and they feel they have lost that guidance (a “coaching void”). In other words you can take a team that would tend towards self-emergent behaviour, and be very strong for it and, by providing guidance, deny them that opportunity.

    And this is assuming the coach is a benign and benevolent presence (and something I want to say is none of this is an attack on you or any individual … I’m sure you’re a great person who adds a lot of value to any team you work with). If the coach is a bit naive, doesn’t understand the business domain well enough, hasn’t got the right techniques for this team, is having a bad week, whatever, then their guidance may take the team to a place it really doesn’t want to be. Either way, a question the team or the manager or the business owner should ask themselves, alongside the ones you pose, is “can my team self organise and can behaviour emerge or do they need a guide?” if the answer is they need a guide a further questions need to be asked: “are they the right team; is the coach the right coach?”.

    The second thing that makes me uneasy is an extension of the first. The more people – usually professional coaches – who say “you really need a coach”, the more this becomes accepted wisdom. Its an age-old pattern: want to do something different, get in an external guru. 

    Now maybe you don’t mean it quite like that. Maybe you see all ‘good’ coaches as experienced facilitators who don’t even provide something as directed as ‘guidance’. But that’s irrelevant because managers and business owners will always look to external gurus when they need to make a change and large consultancies are built on the back of providing those gurus. How long do you think it will be before IBM has a team of 3000 certified coaches? How will people distinguish between the good coaches and those peddling Agile Method/1? If the government decides they need to do 100 agile projects why would they come to the likes of you and Rachel and Liz (great people all) when they can go to KPMG and take advantage of their agreed rates and loss-leading prices?

    You see I think the sad thing in all this is that *the* truly great thing about XP and agile was that it started off being about teams discovering for themselves a new way of doing things that took complete advantage of the soft nature of software and the unique way in which people delivering software could organise themselves and work. I’m afraid that what I see with the establishment of Coach as a job title and Mastership certification is the erosion of that celebration of the uniqueness of software and software teams to something that is much more standardised, commoditised and off-the shelf. So my hope is more people ask themselves the question: “do we really need a coach or can we just do it for ourselves like so many others have?”

    Hmm, a longer letter than I’d hoped … as always. Will leave the final word to you.

    Cheers,

    Paul

  • Sorry … couldn’t resist … an hour after I posted this link popped into my twitter stream: 

    http://www.infoq.com/news/2011/05/agile-coach

    From the first entry written by someone described as an Agile Coach:

    “Do you work hard to make them agile since this is what they’re paying you to do even though they really don’t want to change?”

    “Make them agile”, “what they’re paying you to do”, “they really don’t want to change”. Not much self-organisation and emergent behaviour going on here!

  • Very interesting the concept of a coach in a work environment. I guess you’ve been hired as a coach for a software dev team. How does a coach integrate into the team? and its a little different than a sports team because I would imagine you are not the boss whereas in sports the coach is the boss. So how do you define your role versus the boss/manager?

  • Yes, I’ve spent over half my time in the last 5 or so years working as a coach (the rest as a practitioner – keeping my skills current and relevant). The idea is very common on Agile development teams. I first read about the idea in the early 2000s in  Kent Beck’s book “Extreme Programming Explained”. I experienced it on a couple of teams I worked on and found it invaluable.

    How does it differ from a pro-sports coach? Well, I suppose I see myself a bit like a cross between a sports-coach and a life-coach. I gain my personal satisfaction by seeing peoples’ work-lives improved through the gratification they get from excelling and extending the ways they excel.

    The worst coaches I’ve worked with act like the boss. The best coaches I’ve worked with create a trusting atmosphere for the teams to draw on the coach’s knowledge, experience and insight. The most awesome coaches I know can take a team on a journey of discovery about their untapped potential and help them continuously exploit more and more of it. These especially awesome coaches adapt their style depending on the team[1] and are skilled and versatile enough to work with any member of the team showing them how to do new things as well as learn new things alongside the team.

    If you are interested in learning more there are several books on the subject of “Agile Coaching” [2]. I’m also more than happy to have a chat. Get in touch[3] and we can set up a skype call.

    [1] http://agilecoach.typepad.com/agile-coaching/2010/10/agile-coaching-zone.html

    [2] http://www.amazon.co.uk/s/?field-keywords=agile+coaching

    [3]