Scrum Guide

by Ken Schwaber

The Scrum Guide documents the Scrum framework and is maintained by Scrum’s creators, Ken Schwaber and Jeff Sutherland.

Genres: Management, Business, Nonfiction, Programming, Technology, Computer Science, Reference

19 pages, ebook

First published February 1, 2010

Reviews

[Ahmed Rashwan]

فعلا انا محتاج اقرا الكتاب ده
شكرا لاخى محمود ياسر اللى رشحه ليا
’’ سكرم هو عملية تكرارية و هو الإطار التدريجي لإدارة المشروع غالبا ما ينظر إليها في مجال تطوير البرمجيات، وهو نوع من هندسة البرمجيات‘‘

[Vladimir]

It's a short but perfect guide. Nothing extra.

[Alex ♈]

Mehrfach gelesen, fast auswendig gelernt 🥴

[✧ moira ✧]

uni stuff.

es bueno para entender la definición de lo que es scrum.
un 3 porque me gustó como se explica, pero no es mi área, independientemente de que esté estudiando esto 🤓☝🏼

[Adam Cogan]

This was a very important book for me and changed the direction of my software company www.ssw.com.au

Subsequently I ended up initiating some videos to be produced and they are played to each new hire who joins SSW. They are true to the book and were built with the requirement (should I say 'Acceptance Criteria') to use the *exact* words in the book

Here are some of the videos:
What is a 'Product Owner'? - Scrum Guide
https://www.youtube.com/watch?v=3eljo...

What is a 'Scrum Master'? - Scrum Guide
https://www.youtube.com/watch?v=QbPkc...

The Development Team - Scrum Guide
https://www.youtube.com/watch?v=vLqCk...

The Sprint Retrospective - Scrum Guide
https://www.youtube.com/watch?v=bHfbe...

What is the 'Daily Scrum'? -- Scrum Guide
https://www.youtube.com/watch?v=zxwEd...

If you want more see:
https://www.youtube.com/user/sswtecht...

or https://www.youtube.com/playlist?list...

Cheers Adam
www.adamcogan.com

[Alireza Aghamohammadi]

مخاطب

اسکرام یک چارچوب چابک برای ایجاد محصول است که امروزه در شرکت‌های نرم‌افزاری بسیار استفاده می‌شود. اگر در شرکت‌های نرم‌افزاری مشغول به کار هستید قطعا باید این راهنمای ۱۷ صفحه‌ای را بخوانید.

محتوا

برای ایجاد محصول اسکرام از یک روش تکراری استفاده می‌کند که در هر تکرار (به نام اسپرینت) بخشی از محصول ساخته می‌شود. سه نقش اصلی در این چارچوب دیده می‌شود: تیم ایجاد، مالک محصول و استاد اسکرام.

تیم ایجاد وظیفه ساخت محصول را در طول فرآیند ایجاد محصول دارد. مالک محصول مسئول اصلی موفقیت پروژه شناخته می‌شود. استاد اسکرام فردی است که مسلط به چارچوب اسکرام است و تیم را در اجرای بهتر آن یاری می‌کند. در انتهای هر اسپرینت باید یک دمویی از قطعه ساخته شده به ذینفعان پروژه نمایش داده شود تا بازخوردی از آن‌ها دریافت شود. بازخوردهای مشتریان و ذینفعان مبنایی برای انجام بهتر اسپرینت‌های بعدی می‌شود.

جمع‌بندی

حجم کم راهنما و جالب بودن روش ایجاد محصول خواندن این راهنما را لذت بخش می‌کند.

[Thomas]

I have read this Guide several times in the past few months (it’s only about 20 pages). Yet, I still feel completely unprepared for my Scrum Master certification exam.
It is a nice, high-level overview of the Scrum Framework. But, is it going to prepare me to be the Scrum Grand-Master at my scrum of scrums? Not really.
I find myself regularly consuming guidance from the Agile Alliance website (www.agilealliance.org). This helps supplement what I was able to glean from the Scrum Guide.
This Guide is free to download on the Scrum.org website, so I guess I should not complain given the price (www.scrum.org/resources/scrum-guide).

[ZeV]

This is a very high-level overview of Scrum, useful for those who are familiar with what a process like the Sprint means but do not really have a solid understanding of the principle. I am very familiar with Sprints as used in software technology development but did not know that there was a formal definition for the term "Increment," for example. People at that stage may find the consolidation of knowledge useful, presented as a concise guide. The downside is that it is very high-level and provides no real-life examples. As such, the guide may not be as useful to beginners and practitioners who may want to make connections with concrete real-life examples.

[Debraj]

I downloaded this book and found not at all helpful for my work. This is just like a Summary. I am highly upset. It seems I wasted my time to download and read. I need a book with more details. Where all the concepts are well defined. Any one in this group please help me to select right book on SCRUM.

[Ryan]

What I see happening in scrum in organisations in South Africa today hardly reflects the "immutable" roles, events, artefacts and rules described in this guide. I also found that I had questions around responsibility that were not answered by the guide.

[Johann Lilly]

Useful methodology, mediocre guide.

[Priyansh Miri]

The crux of this book is as follows:

1. The 3 Theories/Pillars of Scrum:
- Transparency
- Inspection
- Adaptation

2. The 5 Values of Scrum:
- Commitment, Focus, Openness, Respect & Courage

3. Scrum Team members:
- (1) Scrum Master, (1) Product Owner & (n) Developers.

4. Their Roles:

i) Developers

- Creating plans for the sprint, The Sprint Backlog
- Instilling quality by adhering to a Definition of Done
- Adapting thier plans each day towards the Sprint Goals
- Holding eachother accountable as professionals

ii) Product Owner

- Developing & Explicitly communicating the Product Goals
- Creating & Clearly communicating Product Backlog items
- Ordering Product Backlog items
- Ensuring that the product Backlog is Transparent, Visible & Understood.

iii) Scrum Master

- Coaching the team members on self-management & Cross-functionalilty
- Helping the Scrum Team focus on creating high-value increments that meets the Definition of Done.
- Causing the removal of impediments to the Scrum Team's Progress
- Ensuring that all Scrum events take place & are positive, productive & kept within Timebox.

5. Scrum events:
- The Sprint
- Sprint Planning
- Daily Scrums
- Sprint Review
- Sprint Retrospective

6. Scrum Artifacts: (Commitment)
- Product Backlog (Product Goals)
- Sprint Backlog (Sprint Goals)
- Increment (Definition of Done)

[Scott Nelson]

I have practiced Agile for nearly twenty years and specialized in Scrum for at least a quarter of that time. I can confidently say - Scrum is not a Methodology as it was once billed. Scrum in of itself is incapable of producing the "Twice the work, in half the time" promise.

While I love the Scrum Principles and Values (as they are a simplified representation of the Lean and Agile P's & V's), I loath the fifteen plus years of dogmatic insistence that Scrum was a methodology has done considerable harm to the Agile "brand" irrefutable harm and contributed to the fractalization of the Agile community - and led to the creation of an "industry" that is anything but Agile.

A very helpful *framework* (aka tool) for implementing Agile mindsets, processes, and practices - but NOT a methodology.

[Joshua R. Taylor]

Short, sweet, all scrum team members should skim this at least once. My biggest takeaway was probably the scrum values, scrum theory and the endnote which reads...

Scrum’s roles, events, artifacts, and rules are immutable and although implementing only parts of Scrum is possible, the result is not Scrum. Scrum exists only in its entirety and functions well as a container for other techniques, methodologies, and practices.

... , contradicting all 'scrum' implementations I've seen which have only implemented a convenient subset of the guide.

[Nasir]

The Scrum Guide Handbook is an essential resource for anyone involved in Agile project management. It provides clear, concise, and practical insights into Scrum, making it easy to understand the framework and implement it effectively. Whether you're a beginner or an experienced Scrum practitioner, the guide offers valuable guidance on roles, events, and artifacts, ensuring a smooth and efficient workflow. It’s a must-have reference for teams aiming to improve collaboration, productivity, and delivery.

[Maciej Jarosz]

This one is about 2020 edition

The “new” Scrum Guide is a mess of sorts with ambiguity, unmapped keywords, keywords with hazy meanings, contradictory statements (like what’s the logical work breakdown structure here, who’s ultimately responsible for what?), and the overall feeling of chaos and confusion. Maybe if it would have been called a “spiritual/philosophical guide” then it would be ok, maybe. Empirism is not about “go figure!” or it-depend-ism, but hey, there is an entire market full of Scrum interpretations, so that’s that.

Too high-level of abstraction to be of any real use.

[TruongSinh Tran-Nguyen]

Short (less than 20 pages), easy to understand. It contains mostly values and principles, so that whenever you are in a middle of a situation, you can always deduce what to do based on those values and principles. Scrum is indeed easy to understand but difficult to master and properly practice.

Remember to read scrum.org blog posts for explanations for some of the updates compare to previous versions.

[Alexandru Crăciun]

De ce doar 2 stele? Este un simplu schelet in care ceremoniile si valorile Scrum sunt prezentate minimal.

Aceasta lucrare este un simplu aperitiv pentru ce inseamna cunostintele si practicile Scrum si nu este suficienta in continut si valoare pentru a permite implementarea acestei metodologii doar pe baza informatiilor prezentate.

Desi este prezentat doar ca un "ghid", prin urmare, nu ma asteptam la aprofundari complexe ale conceptelor Scrum, a fost sub asteptarile mele.

[Raquel (Silver Valkyrie Reads)]

In a way, it seems odd to rate this one. It IS Scrum. If you see the value in the system, this should be on your reading list, or at the very least your reference pile.

Yes, it's a dense read (especially if you were completely new to the concepts), and yes, you'll need other sources for the tips and tricks to apply it in different situations. But there's also a certain elegance in summing up all the principles of practicing Scrum in less than 15 pages.

[Elina Belova]

A very dry theory paper on how Scrum framework is organized in IT product development. Since I worked as a Project Manager at an IT agency, I find this reading truly useful. I could relate the theory to my own practical experience. I'm not sure, if it would be so understandable if I didn't have prior work experience in the field.

[Metin Akın]

Maybe it would be good idea to read after having a online course* about what is the scrum.
Abstract roles, artifacts, events might be difficult to understand for those who are not familiar with (software) development companies.

I recommend you the following course which helped me a lot to cover the concepts in this booklet:
https://www.pluralsight.com/courses/s...

[Evan Wondrasek]

At 20-something pages, it's short and sweet, and is a good reminder that ultimately, scrum is a very minimal framework. I read the updated version as of July 2016. This is worth rereading every year as a refresher.

[Reikan]

Not a very detailed guide. But it has everything when it comes to understanding scrum. Each and every line of the scrum guide is important if you are planning to attempt PSM exam. If you are planning to implement scrum in your project then this is the go to guide.

[Ralph N]

Concise guide to scrum. Leaves out concrete examples on how to actually implement it, but that might not be necessary. This would be akin to learning how to skydive by reading a book on skydiving -- useful, but you still gotta do it.

[Omar]

- Good guide for scrum definitions and related features, practices and roles.

- But still could not be commanded easily as stated in it. May be by more practice more understanding of scrum would be gained.

[Artem Chukanov]

Brief explanation of what Scrum is. Very short and condensed. Good to reread to refresh main values of Scrum methodology. But don't think that this short brochure can explain everything about the Scrum. Read something thicker than this.

[Bunny]

not giving this stars because it was an academic read i had to complete for college. sorry to these men, i'm sure they're fantastic at their jobs but once i get my degree i'm never picking this up again. thanks ken and jeff!

[Abis Ali]

Short and sweet. This guide explains scrum in the most simple manner. It explains the inner workings of Scrum, without going into detail. I would recommend this book to anyone who wants to get into the Scum Framework.

[Ankit Agrawal]

Tons of information in just 17 pages, Bible of Scrum

[John Nduli]

This is a short book detailing the work flow on scrum. It doesn't have a lot of examples or details (as expected from a 19 page book ), but still delivers the important details of a scrum workflow.