What is Scrum?

If anyone thinks Scrum is now known to everyone involved in software development or project management, think again.  ‘What is Scrum’ is still one of the most searched terms on the web (in relation to agile development that is).

According to the Scrum Alliance, “Scrum is an agile framework for completing complex projects. Scrum originally was formalized for software development projects, but works well for any complex, innovative scope of work. The possibilities are endless. The Scrum framework is deceptively simple.”

For me, that still doesn’t describe what Scrum is.  “An agile framework for completing complex projects” – that could be anything!

Here is my attempt to define it more clearly:

Scrum is a simple and repeatable way of managing work.  It can be used for projects, or for ongoing activities.  It was originally designed for software development work, although is not specific to software development so can be used to manage any work.  

Scrum  is based on the principles and values of the agile manifesto, which proposes a different style for managing software development work, encouraging an emphasis on people over processes, working software over documentation, collaboration over contract negotiation, and responding to change over following a plan.

The term agile has also become synonymous with an incremental and iterative approach to software development.

Over the years, I have seen various diagrams that try to depict Scrum.  In my opinion, they are not great because they often look over complicated to me, or they leave too much to the imagination.

In an effort to address this, I have had a go at creating a clearer summary diagram for myself:

Scrummary :)

All of the activities referred to in the above diagram are covered in my series How to Implement Scrum in 10 Easy Steps.  They are also covered in my eBook – Agile Made Easy! – which covers how to implement Scrum and also 10 Key Principles of Agile.

Hope this has been helpful…


3 Responses to “What is Scrum?”

  1. Victor Hernandez says:

    Scrum – simple and elegant; the flow diagram that you put forth is straight and to the point, and I do feel that it removes any possible confusion.

    I enjoyed this, Kelly – thanks!

    Victor (@vhernandez)

  2. Hi,

    thx for good introduction on the flow.

    One small issue that is often spoken about the last months, the product backlog should not be prioritized but ordered.

    A huge difference as it is explained in this article: http://www.scrumalliance.org/articles/367-its-ordered–not-prioritized

  3. Kelly Waters says:

    Hi Kenneth. Thanks for taking the time to comment here. There’s a problem with the link btw, the correct link is here:


    I read this article and I have to say this chap is far too clever for me! The article makes something very simple seem very complicated!

    Personally I think it’s a semantic point. I agree that the backlog should be ordered, rather than putting things into groups of priority 1, 2, 3, for example. But I also think the word ‘prioritised’ can also mean to put it in priority order and that’s perfectly valid too.

    I also think that the idea of building a house roof-first because the roof is the highest priority isn’t a good example. My personal interpretation of priority would not allow that. It would be an earlier priority to build some walls to put the roof on, and an early priority to lay some foundations so the walls stay up. They are higher priorities, not because they carry more business value in themselves, but because they are important things that the roof is dependent on.

    Anyway, that’s my take. But certainly we’re agreed on one thing. The product backlog should be a list of the things you want or need to do to the product, in the order you want or need to do them.


Leave a Reply

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