ScrumMaster Can Be A Blocker

scrum master is a blocker I was intrigued by this article from InfoQ about the role of ScrumMaster as a blocker.

Personally, I hate office politics.

I think they’re are complete waste of time. They zap my energy and leave me feeling frustrated and angry.

I guess there’s an argument here that playing political games protects the team from people that don’t buy into the team’s approach.

I can kind of see their point. But encouraging such a political approach seems to be a bad idea to me. If you can’t debate the pros and cons of an approach – and win or lose the argument on an open and professional basis – I don’t think this is the answer.


3 Responses to “ScrumMaster Can Be A Blocker”

  1. Anonymous says:

    Scott Ambler seems to get about; he’s recently spoken at a Games Developer Conference, talking about how Agile might work in a game-development environment. Who knew that working with Agile could move us all towards the dream of making video games?

  2. ben ross says:

    The terms agile methodology, scrumm and blockers and all the associated bulls*** is a complete waste of time and brain space. Nobody is truly agile, everyone is secretly waterfall and does everything the same way they always have. What a complete load of managerial crap’ola.

    I was reading an article a few weeks ago which measured the effectiveness of Agile and the new philosophy or way of working compared to a traditional workflow. To surmise, the agile projects that were delivered took just as long as the waterfall approach, however the functional teams in the agile space were much more stressed which resulted in arguments and disagreements. This in turn cause a high level of attrition and churn within the groups.

    A successful project can be measured in the outcome traditionally, however in reality, it’s the journey getting there that deems if this was a successful project. Most, if not all agile projects are failures in this respect.

    In my time managing and working on numerous projects, I have not seen one Agile team deliver anything better than a waterfall one…. period.

    In conclusion, this is no more than a concoction of terminology, theory and noise for managers who don’t know how to manage workload or talk to their staff. Any attempt to create a practical application of agile methodologies soon results in the ‘secret’ waterfall approach because agile was not working for them, but they talk the talk to convince themselves and others otherwise.

  3. Kelly Waters says:

    Hi Ben,

    Sounds like you’ve had a lot of bad experience of agile. Your comments certainly don’t echo my experience at all. In fact I have seen agile reduce the stress a team is under quite significantly, particularly when moving from complete chaos with everyone shouting to get stuff done to a process that is more orderly and structured. Having said that, agile does feel quite chaotic when coming from a much more formal waterfall approach.

    The other benefit I have seen (one of many) is the advantage of releasing the software incrementally and much more frequently. I respect the fact that this isn’t possible for all types of projects – some just can’t be released until it has ‘all’ been done. But I have seen many projects deliver incremental benefits along the way, while the team carries on delivering remaining features, and that has carried quite an upside from a business perspective.

    If the fundamental practical difference between waterfall and agile is writing the whole spec up-front and doing all the user testing at the end, versus delivering one small feature at a time and testing it as you go along, I would never do waterfall again.

    I agree with you about the terminology. Coming up with lots of jargon and making agile seem like another language was a mistake and was presumably just for the commercialisation of it as a methodology. But agile can work, I’ve seen it many times.


Leave a Reply

What is 6 + 3 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

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

What People Say

“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.”


“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.”


“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 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!”


“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 was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“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. ”


“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.”


“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 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.”