scrum software
  • 800.653.0024

Scrum Overview Diagram

It is challenging to find a good, high-level summary of Scrum that you can share with your team.  One that visually describes the core concepts of the methodology in a way that anybody can understand. After having produced the new Scrum in 10 Minutes video, we decided to take a stab at this using the visuals from the video. What do you think?

Download the Scrum Overview Diagram PDF

We are releasing this Scrum Overview Diagram under the Creative Commons 3.0 license so you can share it or put it on your own blog.

Tagged with: , ,

Categorised as: Development, Team, Tools

  • Shoeb

    nice diagram..it helps.

  • Pingback: Kickass Scrum Diagram (.PDF) | Agile | Syngu

  • Pingback: 9 Interesting Things You May Have Missed This Week » Eddie Awad's Blog

  • Pingback: 9 Interesting Things You May Have Missed This Week | Oracle Administrators Blog - by Aman Sood

  • http://www.ScrumCrazy.com Charles Bradley, CSM, PSM I, Experienced Scrum Coach

    This diagram has some problems.

    Lacking:
    * Sprint Review
    * Sprint Planning
    * Backlog Grooming (now a required component in Scrum)

    Problematic:
    * There is no such thing as a “Release Backlog.” Further, when you talk about the “goal of a release” you state that is feature driven, which is not always true. Sometimes it is date driven, and most practitioners seem to prefer date driven releases. More here on my blog:
    http://www.scrumcrazy.com/Tips+for+Estimating+Release+Dates+and+Release+Scope+in+Scrum
    Frankly, because Release Planning itself is no longer part of Scrum, I’d just prefer you keep it out out of the picture altogether.
    * What is the deal with the comment about the Product Owner being a dictator?
    * SM – “…sets up meetings and monitors everything…” — this is not an accurate portrayal of the SM — I’m ok with the other text about the SM.

    Having said all of that, I really love the diagram’s concept and presentation, but I will never use it because it is just too inaccurate.

    If you’d like help improving it, I’d be happy to help.

  • http://peppyheppy.com Paul Hepworth

    Hamid, thanks for posting this summary of Scrum. I am afraid however that I agree with Charles Bradley in how the 10 minutes really glazes over the parts that make teams hyper productive. Retrospectives, agile planning, story prioritization, and most importantly sprint review/demos.

    It appears that your perspective of SCRUM is a lot close to “traditional” project management than SCRUM is ever intended to be. I can tell that yout experience with scrum has been with larger organizations that have had to adapt traditional project managers into SM and PO, etc.

    For example, your reference to the role of a SM as one who more or less stares at a burn down and tracks progress grossly under-characterizes the role. SM are pigs that protect the team and help the team voice their concerns and questions. They work with the team to pull in resources from the organization and most importantly remove impediments. This role has less to do with project management and more to do with leadership. After all effective teams don’t need to be tracked, they can do it themselves.

    Also, why should bugs be tracked in a special backlog called a defect backlog? Is a bug work? Why is it grouped separately? I do like your comment about how bugs that are part of the sprint need to be fixed in order to be considered done.

    Also, the release backlog is also kind of strange. I don’t know how Rally and other software vendors get into this mess (same with a defect backlog,) I get that large organizations have larger less frequent releases, but effective teams release smaller chunks of working software more often, making the concept of a “planned release” a foreign one. In my teams I have released software as soon as it was accepted, this means we release 20+ times a day if needed.

    Anyway, thanks for posting and good luck with your scrum tracking tool!

    Paul
    peppyheppy

  • Jonn

    Very useful the second time I read it

Switch to our mobile site