In Learning

The VFQ team are constantly seeking to challenge, improve, and collate information into the best education programme in the world. This has led us down the path of tackling titans like Dan Pink, seeking down books long out of print and talking to lots of people to find different examples from around the world. We are looking forward to showing people some of the product in August at our launch in Texas, Agile 2012.

Today, it’s the turn of the Scrum Diagram (sometimes called the Snowman) to be challenged.

The current and most popular diagram is one that we felt did not really serve the purpose of explaining Scrum as well as we hoped. In the first instance, it looks very linear (more akin to waterfall), and secondly, it misses things like events of Scrum. It’s like a pair of old slippers, we are very comfortable with it, but it just has too many holes.

Scrum - popular diagram

We believe the Scrum Alliance is aware of this, since the picture they display on their website today is from Mitch Lacey.

Scrum Framework

We wanted to see if we could further improve the diagram, and below is our result. We have been through a few iterations and intend to do some more. Once we are happy, and if we have enough positive feedback, we will release a pdf poster version of it, and a high resolution image.

VFQ Scrum Diagram

Sign up to receive our newsletter and new posts

Recent Posts
Showing 3 comments
  • Jv Ravichandran

    Looks good…two points of note – one, a bulb, traditionally, represents an “idea” not a vision; two, the daily scrum meeting timebox should have “Work Progress” and not just “Work”, which is static and backtracking!

  • Russell

    I am very excited you are challenging the status quo. We never ever want to become complacent when it comes to evolving better ways to communicate the essence of what it means to develop IT solutions iteratively and incrementally.
    I am concerned though the way you depict the Scrum Backlog is conveying the wrong idea. The Sprint Backlog is at the very least input and output to the “sprint cycle” as is the Product Backlog.

  • David Wilkinson

    Interesting ideas, although it needs to be understood what the representations are to convey. It’s a simple depiction of workflow without any detail (and we all must be aware that is where the Devil resides). It’s very easy to pick holes in all the proposed /submitted visualisations, all omit any process of realisation of requirements and some (considered) essential steps in “true” Scrum practises. But, where do you stop?.  I believe it is the level of abstraction that is required by the individual. To depict an end to end model in full detail, although beneficial would be overly complex for a layman. The “Snowman” works just fine to give a high level view, granted there is always room for improvement, beliefs should be challenged and improvements made. With the hoards of users in the Agile community to agree and formalise a visual Snowman II – Return of the Scrum, may prove difficult but very welcoming and will promote healthy discussion and a better understanding for all. A very interesting opportunity and a well raised topic for conversation.

Leave a Comment