What do you think?
Rate this book
Scrum Mastery: De Buen a Gran, Líder Servicial
The basics of being a ScrumMaster are fairly straightforward: Facilitate the Scrum process and remove impediments. But being a great ScrumMaster, one who truly embodies the principles of servant-leadership and helps move a team to the high performance levels possible with Scrum, is much harder and much more elusive. In his over ten years of coaching numerous Scrum teams, the highly-respected and experienced Scrum coach Geoff Watts has identified patterns that separate a good ScrumMaster from a great one. In this book, he not only illustrates these patterns through stories of his own experiences and those of the many Scrum teams he has encountered but offers practical guidance for you on your own path to greatness.
In this book you will learn:
The skills and characteristics of great ScrumMasters
How to generate, maintain and increase engagement from the team
How to increase the effectiveness of the Scrum meetings, such as retrospectives and daily scrums.
How to foster a more creative and collaborative team
How to increase the performance of the team
How to know when you are a successful ScrumMaster\
Scrum Mastery is for practicing ScrumMasters who want to develop themselves into a great servant-leader capable of taking their teams beyond simple process compliance.
Comments on the book
Mike Cohn, in his foreword for the book, said:
"Most books rehash well-trod territory and I don’t finish them any wiser. I am positive I will be referring back to this book for many years"
Roman Pichler, author of Agile Product Management with Scrum: Creating Products That Customers Love said:
"I am thoroughly impressed with how comprehensive and well-written the book is. It will be indispensable for many people"
Jean Tabaka, Agile Fellow, Rally Software:
"Geoff brings us a personal and inspired peak into what truly moves us from good to great: great in how we serve; great in how we lead; great in how we create mastery in our teams and organizations; and, great in how we recognize the impediments to our own growth to greatness. Scrum mastery is a skill that can be honed and Geoff gives us rich tools to sharpen our craft."
In this book you will learn:
The skills and characteristics of great ScrumMasters
How to generate, maintain and increase engagement from the team
How to increase the effectiveness of the Scrum meetings, such as retrospectives and daily scrums.
How to foster a more creative and collaborative team
How to increase the performance of the team
How to know when you are a successful ScrumMaster\
Scrum Mastery is for practicing ScrumMasters who want to develop themselves into a great servant-leader capable of taking their teams beyond simple process compliance.
Comments on the book
Mike Cohn, in his foreword for the book, said:
"Most books rehash well-trod territory and I don’t finish them any wiser. I am positive I will be referring back to this book for many years"
Roman Pichler, author of Agile Product Management with Scrum: Creating Products That Customers Love said:
"I am thoroughly impressed with how comprehensive and well-written the book is. It will be indispensable for many people"
Jean Tabaka, Agile Fellow, Rally Software:
"Geoff brings us a personal and inspired peak into what truly moves us from good to great: great in how we serve; great in how we lead; great in how we create mastery in our teams and organizations; and, great in how we recognize the impediments to our own growth to greatness. Scrum mastery is a skill that can be honed and Geoff gives us rich tools to sharpen our craft."
Paperback
First published June 4, 2013
258 people are currently reading
2084 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 30 of 101 reviews
January 19, 2018
Although this book has some suggestions that I consider to be silly and distracting--like adding a game to the daily scrum updates--it is on the whole a terrific book full of practical, inspiring, and extremely challenging ideas. For example:
> A good ScrumMaster will say what needs to be said. A great ScrumMaster knows the power of silence.
My only other objection would be that the information is a mishmash of random thoughts that are forced into the acronym RETRAINED instead of coherently organized. But I would much rather a mishmash of random interesting thoughts than a boring framework.
> A good ScrumMaster will say what needs to be said. A great ScrumMaster knows the power of silence.
My only other objection would be that the information is a mishmash of random thoughts that are forced into the acronym RETRAINED instead of coherently organized. But I would much rather a mishmash of random interesting thoughts than a boring framework.
March 4, 2020
If you’re interested in what a Scrum Master does, this book as some informative chapters in the Appendices. If you want an in depth breakdown of what makes a great Scrum Master, this is the book for you. There are some excellent pointers and tips on leadership and team building that could be applied outside of Scrum/Agile. However, the Agile methodology and Scrum framework facilitate this style of leadership and provide opportunities that might have to be forced otherwise.
January 9, 2025
Who gives a shit about Scrum any more? This was a pointless detour. I am officially a scrum master though, I have the certificate and everything.
August 30, 2015
Foreword cause me to think, there would be some great advice for scrum teams and entirely new topics. In fact, only few things where new and even then, they were explained with long stories and without deep dive into the subject.
Content is really basic. It covers some people managing technics without any new knowledge in that area. It's just scrum perspective on those tools.
For plus are chapters about planning and tracking progress and using visuals. I also liked summaries and quotes before and inside chapter which makes reading more enjoyable.
Content is really basic. It covers some people managing technics without any new knowledge in that area. It's just scrum perspective on those tools.
For plus are chapters about planning and tracking progress and using visuals. I also liked summaries and quotes before and inside chapter which makes reading more enjoyable.
March 16, 2019
This book was on my to-read list for a few years. Since I've drifted a bit from the Scrum Master role in my professional career a few years ago, I didn't had the urge to read it right away... Few weeks ago I finally started reading and yeah. This is great book exactly as I suspected. A must read for all Scrum Masters, no matter how experienced, and a must read for anyone who seeks to understand that role. After gifing it some though I also strongly encourage every people manager that have anything to do with Scrum to read it. Very good book!
June 6, 2018
This book has excellent highlights on what it takes to be a great Scrum Master and I was happy to find a lot of them matched my own observations of what makes SMs effective. Perhaps because I was already familiar with many of the points raised, I found the book somewhat lacking in practical advice.
Despite my somewhat average rating, the book is a good read and I think many will find it useful to discover and start thinking about some of the more subtle aspects of the SM role.
Despite my somewhat average rating, the book is a good read and I think many will find it useful to discover and start thinking about some of the more subtle aspects of the SM role.
January 17, 2021
In my opinion, ScrumMaster is the role that a lot of people underestimate. I believe it is all because they haven't met a great ScrumMaster yet.
I wish every ScrumMaster read the book. It could help get to know how the "great one" would handle difficult situations. Moreover, the author shows how to carry on scrum ceremonies creatively.
The book focuses on a few traits of a great ScrumMaster and explains them by example. Few things are outdated. But still, it is a must-read for everyone interested in the topic.
I wish every ScrumMaster read the book. It could help get to know how the "great one" would handle difficult situations. Moreover, the author shows how to carry on scrum ceremonies creatively.
The book focuses on a few traits of a great ScrumMaster and explains them by example. Few things are outdated. But still, it is a must-read for everyone interested in the topic.
April 1, 2024
it was nice to find a book that spoke to issues found beyond the basic functions of a scrum master. my manager and i have gone thru a bunch of product role related books and a lot feel like they rehash the same info so this was refreshingly different. the biggest issue is that a lot of it centers around like, playing games with your team during meetings and things like that which is kinda silly. i get it, and i would love to find a group of people to work with who are open to those sorts of things, but it's just a job and i fully understand the desire to simply be professional, do the work required, and move on with your life, so a lot of the advice just isn't realistic. i mean, they're reluctant to even do virtual happy hours because they want to just be doing their work lol. i get it tho. there are still good things in this book that you can take away and get excited about, and a nice reminder that it's more beneficial to alter the processes to fit your team instead of being super strict about it and never changing as the team goes through changes.
December 3, 2019
A great book on Scrum Mastery and coaching teams - narrated well in a down to earth accessible way and brought alive with good i
examples and anecdotes. An essential read for all Scrum Masters, teams, any supporting roles, and all aspiring agile coaches.
examples and anecdotes. An essential read for all Scrum Masters, teams, any supporting roles, and all aspiring agile coaches.
July 30, 2020
Very interestig book, gives numerous examples of how a great scrum master should be.
Covers a lot of ground, many different aspects, and the examples are great.
Setting goals, how to inspire the team, how to keep things interesting, removing impediments, are all examples of what was tackled in the book.
Small mini chapters, as well as the case studies, make it a very light read.
Covers a lot of ground, many different aspects, and the examples are great.
Setting goals, how to inspire the team, how to keep things interesting, removing impediments, are all examples of what was tackled in the book.
Small mini chapters, as well as the case studies, make it a very light read.
November 1, 2024
Habe mich vergriffen. Wollte eigentlich ein anderes Buch von meinem Papa mit nach Finnland nehmen und habe aus Versehen dieses eingepackt. Hat nicht wirklich Relevanz für mich, ich habe es aber trotzdem fertig gelesen. ich habe versucht trotzdem ein paar Punkte aus diesem Buch mitzunehmen. Waren 2-3 interessante Punkte dabei.
Ich muss aber sagen, dafür dass es ein Buch für "fortgeschrittene Scrummaster" ist, waren die Empfehlungen alle ziemlich "logisch" und nicht special.
Ich muss aber sagen, dafür dass es ein Buch für "fortgeschrittene Scrummaster" ist, waren die Empfehlungen alle ziemlich "logisch" und nicht special.
December 2, 2019
Must read for every Scrum Master.
January 24, 2020
I regret buying this one. There’s a couple things wrong with the book.
In the beginning, the book introduces the acronym "RETRAINED" that stands for "resourceful", "enabling", (and spoilers), and then retrofits the content into it. Such approach reads like a collection of articles from the internet that have almost no relation to each other.
There are “live cases” to reinforce the ideas in chapters. The cases are not realistic and apparently aren't supposed to be. Each of them boils down to “the team didn’t work, then a scrum master guy did this one trick, and — voilá! — the team now suddenly functions perfectly!” Except this is a very simplistic representation that misses exactly the most important part — feedback loops.
Enormous amount of typos (dashes varying in width) and broken syntax (words put in wrong order in sentences). Lots of padding — literally. Print characters aren't black in the paper book — they are somewhat dark grey, and in combination with a tone too white paper it's hard to read.
In the beginning, the book introduces the acronym "RETRAINED" that stands for "resourceful", "enabling", (and spoilers), and then retrofits the content into it. Such approach reads like a collection of articles from the internet that have almost no relation to each other.
There are “live cases” to reinforce the ideas in chapters. The cases are not realistic and apparently aren't supposed to be. Each of them boils down to “the team didn’t work, then a scrum master guy did this one trick, and — voilá! — the team now suddenly functions perfectly!” Except this is a very simplistic representation that misses exactly the most important part — feedback loops.
Enormous amount of typos (dashes varying in width) and broken syntax (words put in wrong order in sentences). Lots of padding — literally. Print characters aren't black in the paper book — they are somewhat dark grey, and in combination with a tone too white paper it's hard to read.
October 21, 2015
A must read for every leader of some sort. The title has Scrum in it, but it is really about building great teams and changing the organisational context.
What makes the book a 10/10 stars you ask?
* Lots of experience reports as stories from real team situations
* Lots of tips what to try
* Lots of things what hinder team collaboration and growing
* The "Good to Great" motto is awesome!
* Easy to read and very short breathed
* Shows beyond the basics of facilitation and teaching the process to teams
* Shifts focus from practices and complying to process to -> principles
BTW: This book helped me pass the PSM2 assessment, which is VERY hard (prosa answers).
What makes the book a 10/10 stars you ask?
* Lots of experience reports as stories from real team situations
* Lots of tips what to try
* Lots of things what hinder team collaboration and growing
* The "Good to Great" motto is awesome!
* Easy to read and very short breathed
* Shows beyond the basics of facilitation and teaching the process to teams
* Shifts focus from practices and complying to process to -> principles
BTW: This book helped me pass the PSM2 assessment, which is VERY hard (prosa answers).
July 22, 2016
The book consists of real life stories and use cases for the daily use of scrum. I found many of them useful and practical. There are lots of ideas on how to handle difficult situations. The implementation of those ideas is fairly easy and straightforward. Although some of the stories were slightly boring I would recommend this book for begginers, who would like to dive deeper into the world of scrum master's responsibilities.
December 26, 2019
A great book for those newer to scrum or guiding teams, a good book that recaps and reminds you about important topics for those with more experience.
A well written book, the structure makes it easy to refer back to specific chapters when looking for guidance around a specific problem. The highlighting between good and great is a nice format, suggesting that you're not wrong by following the "good" path, but you could help a team (and yourself) even more by following the "great" path.
A well written book, the structure makes it easy to refer back to specific chapters when looking for guidance around a specific problem. The highlighting between good and great is a nice format, suggesting that you're not wrong by following the "good" path, but you could help a team (and yourself) even more by following the "great" path.
May 23, 2019
Great little book. Short, easy to read chapters with some great real-life examples and ideas. Besides some tips and tricks, I also found it useful to evaluate myself against each of the characteristics described. This has helped identify areas I'm doing well at as well as those I either need more practice at or have not even been aware of!
November 8, 2013
Its a much better book than many scrum related books I've read so far. I like the human centered approach, the stories and the mention of tools that are not that obvious to the regular scrum master.
April 27, 2015
Great advice for Scrum Masters, written in a friendly way, with lots of practical tips and real stories. Must read for any good Scrum Master that wants to become a great Scrum Master ;-)
October 31, 2019
This book is a great read if you have experience working as a scrum master for at least a year and want to improve. Novices will not get as much out of this book initially.
December 27, 2019
Fun. Lot of interesting stories, but most of things is basic. Quick read for me.
September 2, 2018
There are some really interesting stories in this book but each chapter starts with a great two line summary which really do sum up a huge amount.
A good ScrumMaster grasps the responsibilities of the role. A great ScrumMaster grasps the skills and mindset of the role.
A good ScrumMaster will be indispensable to a team. A great ScrumMaster will become both dispensable and wanted.
A good ScrumMaster helps a Scrum team survive in an organisation's culture. A great ScrumMaster helps change the culture so Scrum teams can thrive.
A good ScrumMaster will hold team members to account if needed. A great ScrumMaster will hold the team to account for not holding their teammates to account.
A good ScrumMaster is wary of influencing the team. A great ScrumMaster can act normally and know the team will still make their own decisions.
A good ScrumMaster will ensure the team have access to a product owner. A great ScrumMaster will ensure the team have access to the product owner.
A good ScrumMaster helps the team develop and grow. A great ScrumMaster helps the team develop their own growth pathway.
A good ScrumMaster removes disruptive influences from the daily scrum so it is used for the team's benefit. A great ScrumMaster will create an environment where others (particularly the product owner) can attend and not affect the behaviour of the team.
A good ScrumMaster will help a team change their sprint length to find their optimum. A great ScrumMaster has faith in self-organisation and knows the value of rhythm.
A good ScrumMaster will say what needs to be Said. A great ScrumMaster knows the power of silence.
A good ScrumMaster creates an environment where raising impediments can occur.
A great ScrumMaster creates an environment where creativity can occur.
A good ScrumMaster ensures team members share their status efficiently with one another in the daily scrum. A great ScrumMaster ensures the daily scrum is an energising event that teams look forward to.
A good ScrumMaster helps the team identify improvements. A great ScrumMaster inspires the team to be adaptive.
A good ScrumMaster holds a balanced retrospective. A great ScrumMaster holds a focused retrospective.
A good ScrumMaster encourages teams to share skills. A great ScrumMaster encourages teams to share responsibilities.
A good ScrumMaster helps a team meet their definition of done at the end of the sprint. A great ScrumMaster helps a team extend their definition of done.
A good ScrumMaster facilitates the sprint review to look back and review the product built in the previous sprint. a great ScrumMaster facilitates the sprint review to look forward and shape the product in future sprints.
A good ScrumMaster helps ensure the high-value product backlog items are selected in a sprint planning. A great ScrumMaster helps raft an inspiring, engaging and synergistic sprint goal.
A good ScrumMaster updates the sprint burn-down to free the team from overhead. A great ScrumMaster helps the team find a fun way to manage themselves visually.
A good ScrumMaster notices areas for improvement in the team. A great ScrumMaster recognises and highlights strengths for the team to build on.
A good ScrumMaster helps every member of the team grow. A great ScrumMaster fosters the team's growth.
A good ScrumMaster facilitates cooperation between people. A great ScrumMaster facilitates collaboration.
A good ScrumMaster helps teams use "yes, but" effectively. A great ScrumMaster helps teams find more space for "yes and".
A good ScrumMaster will push for permission to remove impediments to team productivity. A great ScrumMaster will be prepared to ask for forgiveness.
A good ScrumMaster protects the team from distractions. A great ScrumMaster finds the root cause of those distractions and eliminates them.
A good ScrumMaster will help maintain team harmony. A great ScrumMaster will guide a team through disharmony to reach a new level of teamwork.
A good ScrumMaster will use Scrum to help bring out the best in everyone. A great ScrumMaster will use Scrum to create a "new best" for everyone.
A good ScrumMaster asks to understand. A great ScrumMaster asks so the team can understand.
A good ScrumMaster will listen carefully to what is said. A great ScrumMaster will also listen carefully to what is not said.
A good ScrumMaster will guide the team through the inevitable stages of development. A great ScrumMaster holds the mirror up to the team and the wider organisation so they can reflect and grow.
A good ScrumMaster coaches the team to success. A great ScrumMaster also allows room for failure.
A good ScrumMaster helps the team find ways to optimise their process. A great ScrumMaster guides the team past the need for process (and a ScrumMaster).
A good ScrumMaster grasps the responsibilities of the role. A great ScrumMaster grasps the skills and mindset of the role.
A good ScrumMaster will be indispensable to a team. A great ScrumMaster will become both dispensable and wanted.
A good ScrumMaster helps a Scrum team survive in an organisation's culture. A great ScrumMaster helps change the culture so Scrum teams can thrive.
A good ScrumMaster will hold team members to account if needed. A great ScrumMaster will hold the team to account for not holding their teammates to account.
A good ScrumMaster is wary of influencing the team. A great ScrumMaster can act normally and know the team will still make their own decisions.
A good ScrumMaster will ensure the team have access to a product owner. A great ScrumMaster will ensure the team have access to the product owner.
A good ScrumMaster helps the team develop and grow. A great ScrumMaster helps the team develop their own growth pathway.
A good ScrumMaster removes disruptive influences from the daily scrum so it is used for the team's benefit. A great ScrumMaster will create an environment where others (particularly the product owner) can attend and not affect the behaviour of the team.
A good ScrumMaster will help a team change their sprint length to find their optimum. A great ScrumMaster has faith in self-organisation and knows the value of rhythm.
A good ScrumMaster will say what needs to be Said. A great ScrumMaster knows the power of silence.
A good ScrumMaster creates an environment where raising impediments can occur.
A great ScrumMaster creates an environment where creativity can occur.
A good ScrumMaster ensures team members share their status efficiently with one another in the daily scrum. A great ScrumMaster ensures the daily scrum is an energising event that teams look forward to.
A good ScrumMaster helps the team identify improvements. A great ScrumMaster inspires the team to be adaptive.
A good ScrumMaster holds a balanced retrospective. A great ScrumMaster holds a focused retrospective.
A good ScrumMaster encourages teams to share skills. A great ScrumMaster encourages teams to share responsibilities.
A good ScrumMaster helps a team meet their definition of done at the end of the sprint. A great ScrumMaster helps a team extend their definition of done.
A good ScrumMaster facilitates the sprint review to look back and review the product built in the previous sprint. a great ScrumMaster facilitates the sprint review to look forward and shape the product in future sprints.
A good ScrumMaster helps ensure the high-value product backlog items are selected in a sprint planning. A great ScrumMaster helps raft an inspiring, engaging and synergistic sprint goal.
A good ScrumMaster updates the sprint burn-down to free the team from overhead. A great ScrumMaster helps the team find a fun way to manage themselves visually.
A good ScrumMaster notices areas for improvement in the team. A great ScrumMaster recognises and highlights strengths for the team to build on.
A good ScrumMaster helps every member of the team grow. A great ScrumMaster fosters the team's growth.
A good ScrumMaster facilitates cooperation between people. A great ScrumMaster facilitates collaboration.
A good ScrumMaster helps teams use "yes, but" effectively. A great ScrumMaster helps teams find more space for "yes and".
A good ScrumMaster will push for permission to remove impediments to team productivity. A great ScrumMaster will be prepared to ask for forgiveness.
A good ScrumMaster protects the team from distractions. A great ScrumMaster finds the root cause of those distractions and eliminates them.
A good ScrumMaster will help maintain team harmony. A great ScrumMaster will guide a team through disharmony to reach a new level of teamwork.
A good ScrumMaster will use Scrum to help bring out the best in everyone. A great ScrumMaster will use Scrum to create a "new best" for everyone.
A good ScrumMaster asks to understand. A great ScrumMaster asks so the team can understand.
A good ScrumMaster will listen carefully to what is said. A great ScrumMaster will also listen carefully to what is not said.
A good ScrumMaster will guide the team through the inevitable stages of development. A great ScrumMaster holds the mirror up to the team and the wider organisation so they can reflect and grow.
A good ScrumMaster coaches the team to success. A great ScrumMaster also allows room for failure.
A good ScrumMaster helps the team find ways to optimise their process. A great ScrumMaster guides the team past the need for process (and a ScrumMaster).
August 10, 2019
An inspectional read, and a profound one at that. If I ever consider transitioning into a Scrum master role and wish to elevate my status from 'good' to 'great', this shall be the first text I reach for. Such a profound and pragmatic view on teams and team building.
The book is structured around an acronym to encapsulate the ideal characteristics of a great Scrum master: re-trained.
Each item has a section and each section has 2-4 chapters, each stating a common team behaviour or useful method of leadership. For example, what can you do if developers run out of work in a sprint? How can you best eliminate distractions from the team? How should dissident members of the team be dealt with? Each chapter also includes a useful anecdote, taken from real life scenarios, to illustrate the point of the chapter. It's really a great format and have found many of its truths mirrored in my own team's development.
In a final section at the end, the author also presents a second acronym to cover areas of growth for Scrum masters: belief.
These are not as strongly emphasised, given just a paragraph each, but these are much more general principles which I think are valuable outside of the Scrum master role, so are not so well explored.
Overall worth a quick read if you're ever curious about how the mind of your Scrum master works and the considerations she makes daily. Especially worth it when she is a great one.
The book is structured around an acronym to encapsulate the ideal characteristics of a great Scrum master: re-trained.
R - Respect
E - Encouraging
-
T - Tactful
R - Resourceful
A - Alternative
I - Inspiring
N - Nurturing
E - Empathetic
D - Disruptive
Each item has a section and each section has 2-4 chapters, each stating a common team behaviour or useful method of leadership. For example, what can you do if developers run out of work in a sprint? How can you best eliminate distractions from the team? How should dissident members of the team be dealt with? Each chapter also includes a useful anecdote, taken from real life scenarios, to illustrate the point of the chapter. It's really a great format and have found many of its truths mirrored in my own team's development.
In a final section at the end, the author also presents a second acronym to cover areas of growth for Scrum masters: belief.
B - Believe
E - Enquire
L - Listen
I - Illuminate
E - Encourage
F - Facilitate
These are not as strongly emphasised, given just a paragraph each, but these are much more general principles which I think are valuable outside of the Scrum master role, so are not so well explored.
Overall worth a quick read if you're ever curious about how the mind of your Scrum master works and the considerations she makes daily. Especially worth it when she is a great one.
November 23, 2022
This was a book I read for work. Although I am not in the technology field, I use a type of Scrum with the leaders that I coach. This book is mostly focused on a full-time Scrum Master. This person is a crucial member of a team as they work on fulfilling their goals in weekly Sprints.
The Main purpose of a Scrum Master is to support the team and help remove impediment. However in working with people and personalities, the Scrum Master has to incorporate many "people skills".
Here is the gist, a great Scrum Master has the following traits:
Respect
Enable
Tactful
Resourceful
Alternative
Inspiring
Nurturing
Empathetic
Disruptive
Faith in people
The book is full of examples of different teams and how various Scrum Masters handle issues using the traits above.
I would not suggest reading this book unless it fits what you do for a living or if you are n executive or educational coach. I learned some new ideas and that is why I read it. :)
The Main purpose of a Scrum Master is to support the team and help remove impediment. However in working with people and personalities, the Scrum Master has to incorporate many "people skills".
Here is the gist, a great Scrum Master has the following traits:
Respect
Enable
Tactful
Resourceful
Alternative
Inspiring
Nurturing
Empathetic
Disruptive
Faith in people
The book is full of examples of different teams and how various Scrum Masters handle issues using the traits above.
I would not suggest reading this book unless it fits what you do for a living or if you are n executive or educational coach. I learned some new ideas and that is why I read it. :)
December 30, 2022
So now I’m not sure what to do. The end of this book says that there needs to be a dedicated scrum master who is not part of the team. The significance is that a) I don’t have the ability to not particpate on the projects, and it was not what I was hired to do, but B) there are compelling psychological reasons and network reasons to not be a member of the team while also directing the team.
Perhaps I can get the program manager to be a part of this scheme? I don’t know. I’m conflicted at the very end.
I learned a lot from this text. Namely I saw connections between user story mapping and stories being objective for scrum.
I think the agile process is the next thing to interrogate. Once again I’m wading backwards into a larger process. Lol. (3D Materials instead of 3D modeling)
Ok. So the next question is how to I incorporate what I have learned into what I am motivated to do, and what I have been asked to do.
🤷♀️
Perhaps I can get the program manager to be a part of this scheme? I don’t know. I’m conflicted at the very end.
I learned a lot from this text. Namely I saw connections between user story mapping and stories being objective for scrum.
I think the agile process is the next thing to interrogate. Once again I’m wading backwards into a larger process. Lol. (3D Materials instead of 3D modeling)
Ok. So the next question is how to I incorporate what I have learned into what I am motivated to do, and what I have been asked to do.
🤷♀️
August 15, 2025
Tenía pendiente este libro desde que hice el PSM II (lo tiene como lectura recomendada) y a nivel de contenido creo que es un buen libro, presenta de forma estructurada las cualidades que debería tener un líder servicial y va planteando situaciones de ejemplo con propuestas de como afrontarlas. Para mí gusto demasiados minijuegos entre las propuestas, cosa que nunca me ha funcionado demasiado bien, pero puede ser cosa mía y considero que por lo demás da buenos consejos.
Ahora bien, la traducción al español es bastante mediocre, en general poco revisada, poco natural y de vez en cuando frases directamente sin sentido, algunas para más inri utilizadas en grande como introducción a capítulos, por ejemplo "¿crecen como personan los que se servidos?". No llega al punto de otros libros que directamente he tenido que abandonar su lectura pero a poco que te defiendas con el inglés te recomiendo leer el original, yo me arrepiento de haberlo leído en castellano.
Ahora bien, la traducción al español es bastante mediocre, en general poco revisada, poco natural y de vez en cuando frases directamente sin sentido, algunas para más inri utilizadas en grande como introducción a capítulos, por ejemplo "¿crecen como personan los que se servidos?". No llega al punto de otros libros que directamente he tenido que abandonar su lectura pero a poco que te defiendas con el inglés te recomiendo leer el original, yo me arrepiento de haberlo leído en castellano.
December 8, 2018
While I liked the book, I don't think its content is revolutionary in any way. To my taste, it focuses too much on the soft-skills needed for what Geoff Watts calls great scrum masters. You will find some tips on how to coach the team in certain aspects such as active listening or conflict management for example.
Before I read the book I knew I needed to work on my facilitation, coaching, mentoring, self-reflection or teaching skills. But that's what this book has to offer, areas for people to develop themselves to be better scrum masters. How you do that, it is your own journey. That's the conclusion.
I think this would be a good read to any rookie scrum master, for the experienced ones you won't find anything here you haven't heard before.
Before I read the book I knew I needed to work on my facilitation, coaching, mentoring, self-reflection or teaching skills. But that's what this book has to offer, areas for people to develop themselves to be better scrum masters. How you do that, it is your own journey. That's the conclusion.
I think this would be a good read to any rookie scrum master, for the experienced ones you won't find anything here you haven't heard before.
March 14, 2019
At the beginning, it seems that the book explains obvious thoughts or facts, but while you're reading it, these concepts hook you. I recommend to write down some notes because it's full of tips or new ideas you may apply in some moments. In fact, I've started to do a couple of tips during the retrospectives and the daily meetings.
However, you need to be open-minded to get all the concepts and think about all the things you're doing. Sometimes you're doing something unintentionally and it might be dangerous for the team.
An excellent book to think about your possibilities. I'm positive I'll read it again in some months to assess my progress.
However, you need to be open-minded to get all the concepts and think about all the things you're doing. Sometimes you're doing something unintentionally and it might be dangerous for the team.
An excellent book to think about your possibilities. I'm positive I'll read it again in some months to assess my progress.
February 1, 2021
4.5/5
The book is so good that everyone who works with SCRUM should read it (PO, dev, SM - nevermind). Servant leadership at its finest! I love that the book is not tight-coupled with the scrum guide and is full of examples. One drawback - the SM work with PO is a little bit neglected in the book and the chapter about Eliminating Distractions about part-time team members isn't something I can agree with. All in all this book is of great value and is a must have!
The book is so good that everyone who works with SCRUM should read it (PO, dev, SM - nevermind). Servant leadership at its finest! I love that the book is not tight-coupled with the scrum guide and is full of examples. One drawback - the SM work with PO is a little bit neglected in the book and the chapter about Eliminating Distractions about part-time team members isn't something I can agree with. All in all this book is of great value and is a must have!
April 3, 2022
Watts discusses in this book how to make the jump from a good Scrum Master driving execution from their scrum team through command and control heroic tactics to a truly great servant leader Scrum Master who empowers the scrum team by assisting them to be all that they can be by focusing on their growth and success. “It is amazing what you can accomplish if you do not care who gets the credit.” – Watts. #Agile #ScrumMaster #ServantLeadership
Displaying 1 - 30 of 101 reviews