Is there a way to check on the correct application of Scrum?
Most attempts end up in complex questionnaires or big assessments. This is strange as Scrum is a simple process and has distinct definitions of roles, artefacts and meetings. And I also distinguish core principles.
When presenting Scrum as the core process of my My.Fragility framework I always show my Scrum Diamond, a graphical representation of the 3 essential elements for each of the 4 Scrum ceremonies:
It makes an assessment of Scrum simple: check whether the process and the above ceremonies are in place!
And remember: Scrum prescribes a minimal, but tightly coupled, set of ceremonies. Skipping even only one implies affecting the essence of Scrum. Doing so does not necessarily mean that you are not Agile or don’t perform well, but don’t call it… Scrum.
7 thoughts on “Definition of… Scrum”
Gunther, Thanks, that explains it ! Time to read your book as well -;)
If you do, I hope you like it. Find a bunch of links on where to get it at http://guntherverheyen.com/2014/06/10/scrum-a-pocket-guide-3rd-impression/
I already ordered it. Expected tomorrow. I’ll let you know my thoughts. The references of your scrum collegues are very promising.
Gunther, I want to compliment you on your book. I would describe it as a ‘Lean’ travel companion: If I should represent the journey in your book as a Value Stream Map it’s components represent much value and minimum waste (carefully chosen descriptions and each sentence has a its own meaning/value). Very clear in separating the game and the tactics of scrum. Further a good explanation of the embedding / (gorilla)position of scrum in Agile, the contradiction with the traditional paradigm and the necessity of further upstream adoption. The book invites me to investigate further, in particular the tactics. I have some further thoughts, questions and remarks on the book. Is it alright to put these on your scrum.org mailaccount?
Hans, thank you very much for the nice feedback and the appreciation. You have pointed out some core objectives I had in mind when writing the book; concise, clear, the why of Scrum’s rules. Do reach out at my Scrum.org address.
I would be very pleased if you would be willing to add some of your feedback on my book at Amazon etc.
Hi Gunther, looking at your scrumdiamond I wonder why the sprint retrospective is not in there. From what I read on your website it leaves me no doubt that you value ‘learning from the past’ (being one of the important principles of scrum) very high! So why letting it out?
Best regards, Hans van Lavieren.
Hans, I understand the confusion, but on the diamond “Review” is intended to refer to the activity of reviewing, not the Sprint Review meeting. Reviewing is done on the product, and on the process. The drawing was further improved when re-using it in my book, by eliminating the preceding “Sprint”.