Scrum Agile Development: Uncommon Sense

Scrum Agile Development Uncommon SenseScrum is an agile development method based on some of the key principles of lean manufacturing, pioneered by Toyota.

Advanced Development Methodologies, Inc is the home of Scrum. On their web site, I recently noticed their strapline: ‘It’s about Common Sense’.

When you think about it, it is.

In fact, it’s so ludicrously simple, it’s almost funny.

Think about it.

Think about the basic framework, only without the jargon:

  • Make a list of the things you need to do (Product Backlog)
  • Get someone (Product Owner) to decide what’s most important and put the list in priority order
  • Set a fixed deadline in the foreseeable future (Sprint)
  • Estimate how much you’ll be able to complete by the deadline (Sprint Planning/Sprint Backlog)
  • Work through the list in priority order, completing each thing before moving on to the next
  • Check your list every day to see how you’re doing (Daily Scrum)
  • Even if you haven’t completed everything on the list, release the software when the time is up, in order to realise some benefits
  • Review how it went to see if there’s anything you would do differently in future (Sprint Review)
  • Repeat (iterate)

So if it’s so simple – if it’s such Common Sense - why do so many software development teams tend not to work this way?

Why instead do so many development teams tend to work on long projects. Seeking to understand and define the entire scope up-front. Seeking to resist change. Seeking to develop everything before getting it tested. Seeking to complete *everything* before releasing *anything*.

Perhaps the makers of Scrum should have tagged it ‘Uncommon Sense’.

Personally I think that would be closer to the truth.


See also:
10 Key Principles of Agile Development

6 Responses to “Scrum Agile Development: Uncommon Sense”

  1. Vladimir Levin says:

    That’s a great summary. I think the tendency to try to think of things up front has to do with fear of risk. There is a perceived reduction in risk if you assess things up front. However, in practice, it tends to be a waste of time. I do think the RUP idea of identifying and maintaining a list of the highest project risks is a not a bad idea – but it has to be handled in a way that doesn’t involve ridiculous amounts of time spent on meetings and artifacts that don’t have intrinsic value.

  2. Mihai Campean says:

    Indeed a great summary of Scrum, even better than any of their highly regarded evangelists could have come up with :).
    I also believe Vladimir is correct when he says that thinking things up front and resisting change tend to give development teams a feeling of comfort and low risk.
    My personal opinion regarding software development methodologies is that you should use whatever suits your team and project best, even if it means combining more of the commonly known methodologies like Agile, RUP or Waterfall or doing something entirely new if that helps things along. I also wrote a short post on my blog regarding this so, if you like you can check it out:

  3. HarryC says:

    My take on Why not?: There’s nowhere to hide.

    You have to accept that many bad ideas and poor workers are hidden within software products: Misanthropic people, burnouts, requirements that don’t make sense, pet projects, sideline items demanded by management, but of no value.

    With Scrum, it’s so startlingly obvious what’s valuable and what’s not, that there’s nowhere for a bad manager/project manager/architect/developer to hide, and that scares some people to death, enough that they bring down any sort of ‘Agile’ methodology as too radical or “cowboy”.

    I’m not implying that other methodologies are bad. This is just my experience with how Agile has been received where I’ve worked.

  4. Kelly Waters says:

    I agree.

    see my other post “Agile Development: No place for snipers!”


  5. Vladimir Levin says:

    I’ve posted a blog entry refering this one at the following url

  6. Anonymous says:

    Reality is more complex than Scrum lets you believe.

Leave a Reply

What is 4 + 5 ?
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.”