But Scrum

This content is syndicated from VersionOne by VersionOne. To view the original post in full, click here.

Most of us have heard of the term 'Scrum but' - it refers to agile teams that are trying Scrum processes but are having some challenges.  For example, a group that is exhibiting 'Scrum but' might say something like 'We are practicing Scrum, but our sprints are anywhere between 6 and 8 weeks;' 'We are practicing Scrum, but we don't always deliver working code at the end of the iteration.'

Yes, these are bad situations.  But let's look at the flipside - let's look at 'But Scrum.'but scrum

'But Scrum' is when a person/team/organization flips off their 'thinking bit' and just burps up whatever Scrum tells them to do.  Want some examples?

  • But Scrum says we estimate
    I have personally been around agile teams that don't estimate all of their items in their backlog.  Why?  Multitudes of reasons. A couple of examples:
    1. Teams break down their work far enough (day range) where the variance in the estimates would be minuscule.
    2. A team works really well together and can accurately predict how much they can get done, without worrying about points

  • But Scrum says we need self-organizing teams
    Yep, self-organizing teams would be awesome.  There is a magic dashboard of work on the wall and people will just naturally float over and create uber teams to crush out work.  Most large organizations are still structured in classical, matrixed manner.  Telling their IT departments to 'self-organize' is irresponsible.  Most people multi-task. Is it a problem? Sure. Is it a reality? You betcha. Specialization is an output from our national hiring structure - just look at any job boards for confirmation.  Good luck changing that inertia.

  • But Scrum says we need a Scrum Master
    By no means do I have hard numbers to back this up, but look at it this way: If Scrum masters were making agile software development and delivery so much better, then given the rate of CSMs being handed out, we should have some bad bamma jamma software coming out from the majority of organizations.  But we don't.  I'm not even going to get into the whole certification battle. Little known fact - Patrick Duffy is a Scrum Master.

  • But Scrum says once we commit, the backlog doesn't change
    Right, because market events and competition only happen in nice, predictable cycles

  • But Scrum says our teams should be 7, +- 2
    There are plenty of Scrum development teams out there working well with a size over 10 as well as split geographically.  A team that works well together is a team that works well together.

Which is worse - 'Scrum but' or 'But Scrum'?  They are both horrible. One is giving excuses why you can't try and change; the other is giving excuses why you can't change what you are trying.  Both are pointless.

The reality is developing a software product is hard.  It requires thought, inspection, change, and risk.  You have to think.

What other 'But Scrum' comments have you heard?  Let's collect them.

Leave a Reply

What is 3 + 2 ?
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.”