Eine bessere Version des Scrum Flow DiagrammsA better Version of the Scrum Flow diagram

Da ich morgen einen Workshop zum Thema Scrum und JiraAgile halte, habe ich nach bekannten Bildern des Scrum-Flow gesucht, um einen „Roten Faden“ duch den Workshop (Tabs: Plan, Work und Report) zu ziehen. Leider empfinde ich die existierenden Versionen des Scrum Flow Diagramms als unzureichend, da sie die Arbeit der Product Owner bestenfalls als „Sortierer“ von Listen darstellt.

Ich begann mit dem klassichen Flow um nach der dritten Iteration eine Skizze eines besseren Flow’s zu erhalten.


Das Ergebnis war anders als ich es mir zu Beginn vorgestellt hatte, aber die Darstellung der Arbeit des Product Owner (und seines PO-Staff) fand ich eben so gut, wie die Möglichkeit einige Artefakte und Zeremonien darzustellen. Weiter Aufgaben eines Product Owner (z.B. Abstimmung der Stories im skalierten Umfeld) können einfach hinzugefügt werden.
Die Zeichnung geht auch wunderbar mit Marty Cagan’s Dual-Track-Scrum einher.


Wenn Ihr Ideen habt, wie ich diese Zeichnung weiter verbessern kann, oder wenn Ihr mehr darüber erfahren wollt, wie man Jira mit Scrum vereint, dann kommentiert diesen Beitrag oder schreibt mir persönlich.

The click here to open the english version of this post.

Ihr könnt dieses Bild frei für Trainings oder Workshops benutzen, solange ich als Urheber genannt werde ;-)As I’ll be holding a workshop about the best way to use JiraAgile with Scrum, I planned to show the „standard“ Scrum Flow Chart to explain the three JiraAgile-Tabs (Plan, Work and Report). What I found missing in all of the existing Diagrams is the visualizations of the Product Owners‚ work. One could believe their sole purpose is sorting lists.

I started with a sketch of the regular flow and continued to iterate until I came to the bigger painting.

my version of the Scrum Flow Chart

The Result was a different kind of diagram than I had in mind at the start, taking the PO (and his staff) into account, while explaining some of the Ceremonies and Artifacts of a Sprint along the way. You could easily adapt it for a scaled Environment.
This „piece of art“ also corresponds quite nicely with Marty Cagans‘ Dual-Track-Scrum.

My final version of the Scrum Flow Chart

If you have any Ideas on how to improve this Scrum Flow Diagram, or want to know more about the art of using Jira with Scrum leave a comment below or contact me directly.

You can use this drawing freely for your trainings of workshops as long as you acknowledge me as the author ;-)

Über Markus Wissekal

Markus Wissekal ist seit 15 Jahren in der IT-Branche tätig. Im Jahr 2008 entwickelte er eine tiefe Begeisterung für agile Prinzipien und Methoden wie Scrum, Kanban und vielen Lean-Ansätzen. Ab 1.8.2015 ist Markus als Akkreditierter Kanban Trainer, agiler Coach und LegoSeriousPlay Facilitator verfügbar. Wenn Sie Interesse an einem Training in der DACH Region haben, oder Interesse daran wie Kanban, Scrum oder Lean in Ihrem Unternehmen funktionieren können, dann hinterlassen Sie mir doch eine Nachricht.

8 Gedanken zu „Eine bessere Version des Scrum Flow DiagrammsA better Version of the Scrum Flow diagram

  1. This is a GREAT diagram!! The PO role is as large and critical as the entire team’s role and this shows the equality of the PO’s role to the Team’s. Both are extremely critical to the overall success of the product and scrum team.

    My only one question: the ‚grooming‘ arrows collide, but then go nowhere. Is there somewhere they should visually go?

    A comment for consideration: My teams have always adopted a best practice per see of having the PO attend the daily scrums and all other ceremonies (except the sprint team planning, although they need to be accessible for this for questions if not in attendance). If this is wider common practice, should this be depicted as well.

    All in all, it’s great as it is for the reasons mentioned initially and more!

  2. Thank you Marianne!

    We do the same thing: involve the PO as much as possible – after all he/she is an important part of the scrum-team.

    About the grooming arrows: You’re right, it looks like they collide in the middle an almost evaporate. One of the sketches had them span from the team-circle to the PO-circle, which is way more acurate but didn’t catch the eye as much (IMO).

    I think there is still space for improvement / things missing:
    * the ScrumMasters Role in all of that
    * product increments aren’t visualized as well as I would have wanted them to be,
    * collaborated time (Team, PO, SM, Stakeholders,…)
    * and some more … ;-)

    I’m glad you liked the diagram, thanks for your lovely comment!

  3. Markus, very good visualization!

    Some detail that might make it even better:
    „Prio“ / „Prioritization“ => „ordering“? If we just „prioritized“ things, the backlog would have sections „A“, „B“ and „C“, each containing items of equal priority, right? ;-)

    Thank you for sharing!

  4. Rolf, you’re absolutely right. The arrow next to the ordered list is supposed to show that, but doesn’t seem to be enough. I’m planning on doing a digital (.ps or .ai) Version of the diagram which will have „ordered“ List in it. :-) Thanks for commenting

  5. Great one, Markus,

    I would add a scrum master that listens,understands, talks, re-frames, protects, …. and resolves issues.

    So another loop of actions somewhere (3rd one), „gearing up“ two existing ones :)


  6. Markus, great way to visualize the process, maybe a suggestion to take it in sync with Scrum 3.0. Terms like grooming is now refinement. But never the less great diagram, i am surely gone use it in my presentations if you are okay with that?

  7. Hi Remi!

    Sure, go ahead and use it :-) I’d love to know the context you’re going to use the diagram in.

    I considered the terms „Development Team“ and „Refinement-Meeting“ instead of Team and Grooming. But I like the sound of the „old“ Terms much better. ;-)

    Merry Christmas

Kommentare sind geschlossen.