A Guide to the Scrum Body of Knowledge (SBOK Guide) provides guidelines for the successful implementation of Scrum the most popular Agile product development and project delivery methodology. Scrum, as defined in the SBOKTM Guide, is a framework which is applicable to portfolios, programs, or projects of any size or complexity; and may be applied effectively in any industry to create a product, service, or other result.
The SBOK Guide was developed as a standard guide for organizations and professionals who want to implement Scrum, as well as those already doing so who want to make needed improvements to their processes. It is intended for use as a reference and knowledge guide by both experienced Scrum and other product or service development practitioners, as well as by persons with no prior experience or knowledge of Scrum or any other project delivery methodology.
The SBOK Guide draws from the combined knowledge and insight gained from thousands of projects across a variety of organizations and industries. In addition, contributions have been made by experts who have taught Scrum and project delivery courses to more than 400,000 professionals in 150 countries. Its development has truly been a collaborative effort from a large number of experts in a variety of disciplines. The book has eighteen co-authors and subject matter experts and the twenty-eight reviewers who greatly contributed to the creation of the SBOKTM Guide.
Wide adoption of the SBOK Guide framework should help standardize how Scrum is applied to projects across organizations globally, as well as significantly help to improve their Return on Investment. Additionally, it should promote greater thought and deliberation regarding the application of Scrum to many types of projects, which will in turn contribute towards expanding and enriching the body of knowledge and consequently future updates to this guide.
Although the SBOK Guide is a comprehensive guide and framework for delivering projects using Scrum, its contents are organized for easy reference, regardless of the reader s prior knowledge on the subject.
The first chapter (Introduction) of the SBOK Guide is available in Scrumstudy.com, along-with a free "Introduction to Scrum" course.
Es un 3 por algunos conceptos y contenido interesante. Puede usarse muy bien como material bibliográfico y hay que darle el crédito por eso, además el material de estudio de SCRUMStudy - en general - es muy bueno y es útil para aprender.
Sin embargo existe un tremendo “PERO”, que se debe comprender antes de continuar con esta certificación y es que muchos conceptos son diferentes o nuevos con respecto a la Guía de Scrum original, escrita por los creadores, aplicada por muchos expertos y ampliamente practicada en todo el planeta.
No niego que al principio me pareció una idea genial poder estudiar Scrum como si fuera el PMP, un libro estructurado y muy familiar, pero luego lo sentí pretencioso, redundante, y definitivamente distinto a Scrum en muchos conceptos y prácticas.
Yo tuve la oportunidad de certificarme como SMC con ScrumStudy y también como PSM de la mano de Scrum.org, y como profesional, me siento en la obligación de advertir que no son lo mismo y que pueden generarse muchas confusiones en el camino. Son cosas serias, que en el mundo laboral pueden definir un currículum y el éxito de una aplicación laboral.
En lo personal, y con mi experiencia, yo prefiero el contenido tradicional de Scrum.org, porque es el más aceptado y conocido por el mundo. Y yo siento que dominar eso me conviene más.
Claro que sería genial que todos las entidades certificadoras se pusieran de acuerdo y existiese unas sola certificación de Scrum Máster (CSM, PSM, SMC, etcétera), pero no creo que eso vaya a pasar.
Así que al momento de certificarte es importante saber “¿Cuál es la certificación que te conviene? Y ¿cómo te vas a preparar?”.
I was fighting this book for months because it's so frustratingly unreadable. No wonder it's available for free. I'd even suggest paying anyone for completing it because it's such a pain to read.
To be fair I actually managed to learn something from that book but it's only because I've been working in Scrum for several years. It'd be difficult to get anything useful from it without prior exposure to that methodology.
The book is poorly written and carelessly edited. Too much terminology, too few examples. It's so repetitive it could've been 4x shorter without losing any value. There were multiple cases where a paragraph was duplicated so I wonder if there was any editing at all.
Anyway, it was a painful read and I wouldn't recommend it to anyone.
There are other books which details the framework better, faster. Its not bad but its not great also. I gave it a 2 for the effort, the quality of the content its less. The structure of the book resembles with PMP, neh have to say that medium articles about SCRUM brings more value vs time to read this book, even if its free.
Es una guía muy impotante que todo miembro de algún equipo que esté trabajando por un logro en común. Brinda las bases necesarias para la gestión de equipos de trabajo de forma ágil
Scrum is built on 5 values and 3 pillars. Transparency is one of these pillars and respect is one of the values. I'm going to try and be respectful, but transparent at the same time.
But before I do so, I need to point out that I'm a trainer in the field of Agile and that I am associated with a company that could be considered a competitor in the field of scrum. That said, I'll try to keep my review fully based on the facts.
So fully transparent. I did not like this book. I respect the effort that was clearly put into it, but I'm afraid that a lot of people from a more traditional software development type organisation will read this and take away that this is what agility looks like.
Scrum is a framework, it's simple in it's basis and is based on the principles of inspection and adaption. Due to this nature, there is no one right way to "do scrum". As long as you keep to the basic rules, you'll be doing scrum, but you might not actually be getting much value out of it if you don't take the opportunity to actually apply what you're learning from the short sprints you're doing.
In the same view, there is not just one way to combine multiple teams, or to work with multiple product owners or multiple scrum masters. There is no default "process" one can invoke, except for the few events that are described in the Scrum guide. And even for these events, the format is kept open, the goals are described. It's up to the team to figure out what works best for them and their organisation.
This is where the scrum guide might fall short. It leaves open so much, that it might feel daunting to figure it all out. It's with reason that it's said that scrum is simple to understand and very hard to master. And maybe this is where the ScrumBOK has some merit. As a possible starting point. As one way one could try to start doing scrum (after fixing a few issues with its definition of the simple scrum events and roles). It would not be my choice, but it may be yours.
There are so many other great books, blogs and presentations available that I would hope that you spend your money on those first. Or at least that you investigate other options as well to see what works for you and how you can apply the values of scrum in such a way that you really improve both as individual and as an organisation.
I would not buy this book. Luckily it is provided as a free PDF and I can honestly say that I read it from front to back.
It provided a detailed framework of scrum methodology. I liked the step by step approach explained in the book. It is very helpful as a reference source, especially if you are implementing scrum or working in a scrum team.
If you need to learn about SCRUM and you already have a grasp of agile delivery, then the information you need is in here. However, it is poorly laid out. To be fair, it was probably written primarily as study notes for people ho took the course and want to get certified.