A Mike Cohn Signature Book
Succeeding with Agile: Software Development Using Scrum (Addison-Wesley Signature Series
This is the definitive, realistic, actionable guide to starting fast with Scrum and agile–and then succeeding over the long haul. Leading agile consultant and practitioner Mike Cohn presents detailed recommendations, powerful tips, and real-world case studies drawn from his unparalleled experience helping hundreds of software organizations make Scrum and agile work.
"Succeeding with Agile" is for pragmatic software professionals who want real answers to the most difficult challenges they face in implementing Scrum. Cohn covers every facet of the transition: getting started, helping individuals transition to new roles, structuring teams, scaling up, working with a distributed team, and finally, implementing effective metrics and continuous improvement.
Throughout, Cohn presents “Things to Try Now” sections based on his most successful advice. Complementary “Objection” sections reproduce typical conversations with those resisting change and offer practical guidance for addressing their concerns. Coverage includes:
- Practical ways to get started immediately–and “get good” fast
- Overcoming individual resistance to the changes Scrum requires
- Staffing Scrum projects and building effective teams
- Establishing “improvement communities” of people who are passionate about driving change
- Choosing which agile technical practices to use or experiment with
- Leading self-organizing teams
- Making the most of Scrum sprints, planning, and quality techniques
- Scaling Scrum to distributed, multiteam projects
- Using Scrum on projects with complex sequential processes or challenging compliance and governance requirements
- Understanding Scrum’s impact on HR, facilities, and project management
Whether you've completed a few sprints or multiple agile projects and whatever your role–manager, developer, coach, ScrumMaster, product owner, analyst, team lead, or project lead–this book will help you succeed with your very next project. Then, it will help you go much further: It will help you transform your entire development organization.
512 pages, Paperback
First published January 1, 2009
About the author
Mike Cohn
17 books171 followersRatings & Reviews
Friends & Following
Community Reviews
You can read the book cover to cover but depending on your background and situation you can also cherry pick the chapters you need. Each chapter is packed with handy tips ('things to try now'), typical 'objections' (and counter arguments) and clear diagrams.
What I also like about the book as that it has a kind of iterative feel to it. Reading a chapter makes you grasp the general concept and stimulates you to immediately start implementing the concept with it's hands-on tips. As you become more familiar and experienced with the concepts you can refer back to the book to deepen or update your knowledge and practices.
The 5 stars are rather emotional based since as we are currently adapting scrum as our method of work in our tiny company, this book was exactly what we needed.
It is very recommended for a project manager rather than a developer or a team leader!
Merged review:
The book is focusing on only one thing "How to adapt Agile development (successfully)"! It is business oriented book, so don't expect so much for a cut through plan for agile development process to jump working right now!
It is very recommended for a project manager rather than a developer or a team leader!
If you are looking to introduce Scrum in your organisation or to improve the way it is implemented, you should read this book and keep it close at hand. If you do not already have a working knowledge of Scrum, some Certified ScrumMaster or Certified Product Owner training, say, you should get that first, and then read this book.
Often when reviewing books I condense my key findings, but this is hard in this case. The book is just too expansive, but in a good way. It is to Scrum what Code Complete by Steve McConnell is to programming. Neither are introductory texts, but they are excellent companions for anyone having advanced past that stage.
The first part of the book is about how to introduce Scrum. if you are not about to do this, I think you'll find it a little boring, and despite what Cohn writes in the introduction, it probably can be safely skipped. The next three parts form concentric circles starting with the individual, followed by the team and then the entire organisation. I found the topics covered here to be very illuminating and well-explained, though I still have unresolved questions on topics such as what should before launching a project (business case, initial product log, feasibility) and how to effectively manage an organisation using a lot of Scrum. The book is centred on Scrum the process with a clear bias to software engineering, but it only touches on the software engineering practices that are necessary to succeeding with agile.
Cohn's style is more journalistic than academic. He uses a mix of anecdote, theory and hard data from research and even quotes from agile practitioners. This makes the book very readable. It is also very practical with concrete tips on practices you can try today and ways to handle common objections to Scrum and agile (of which there are many).
As my career progresses, I’m certain that I’ll refer back to this book. However, at my current stage it isn’t #1 on my list of recommendations for a new dev. 🤷🏻♂️
Finally, unless you are directly in a leadership position, you can completely skip the Parts IV and V, chapters 17–22. I should have, and knew I should have, it’s just that I have too much of a completionism streak in me. Admittedly though, that’s why I stalled so long on finishing this book this book—I even read a whole other agile book in between.
Значна частина книги присвячена тому, як виставити на посміховисько, ізолювати, подавити, а то й просто виперти з проекту скептиків. Думаю, радянські комсорги, профорги й інша партота знайшли б багато цікавого для себе в цій книзі.
Втім, people хаває, а ворога потрібно знати в обличчя. Сама книга написано непогано, не надто сухо, але й без зайвої води.
This is a valuable book from a more leadership perspective. The book goes through the main points on how to implement Agile and demystify Agile as easy-all-mighty mindset. The author tables the steps to follow to implement Agile framework (mainly Scrum) and the hard challenges along the way.
You can read the book cover to cover easily but I would not call it an introductory text, it is for leaders who want to understand Agile inserted in an organization and how to implement it.
This book was published in 2009 (nearly ten years ago) and was one of the most authoritative works on how to adopt scrum at the time. I wanted to read it to see the context of one of the first mentions of the testing pyramid. These approaches (scrum and testing pyramid) have become the bedrock of current Dev(Sec)Ops development techniques. I rate it 3 out of 5 now because even though modern-day techniques have evolved, it is still worth reading for its fundamentals.
Если есть вопросы по внедрению - очень рекомендую, если нет, то стоит обратить внимание на другие его творения.
I would have liked a more comprehensive list of resources to dig deeper, specially in the second part of the book regarding team work, one of the main challenges in scrum.
Summing up, this is a excellent starting point to implement scrum.
This is one of the most conplete book that I have read to esycate a great scrum master or agile coach. I think it's a must seek book for all the professional that whats to evolve and get succeeding with agile.
That is not the case in this book, Cohn describes the agile software development process and he provides extensive examples of the use of the Scrum methodology and the difficulties commonly encountered. It is easy to understand the hesitation that development teams will have when considering the adoption of Scrum. The development of large software projects is the most complex task that humans have ever undertaken; even a single wrong character out of millions can break a program. The appearance of the relaxation of controls of the process can appear counterintuitive, as it seems that would allow for additional errors to slip through the weakened defenses.
Cohn goes to great lengths to demonstrate how Scrum will strengthen those defenses by reducing the likelihood that errors will survive for very long. Splitting the process into short spurts means that all minds can be on deck and their focus will be on a small set of parameters. This is a way to make minds smarter without actually having to be smarter. Cohn also joins the collective clamor against the extensive use of overtime as a way to compress the time to completion. Evidence going back decades is completely convincing that when it is brainwork, overtime can only increase productivity for a short time. Intellectual fatigue rapidly sets in and after approximately three weeks, the productivity level begins to drop down to less that what is achieved in a standard forty-hour week.
Charts, graphs and tables are used to support the arguments made for the adoption and intelligent use of Scrum. Convincing a team to adopt Scrum is essentially using facts and demonstrated rewards to overcome emotional barriers and the natural unwillingness to execute change. This cannot be done in any way other than by starting with the reality of current problems, giving multiple demonstrations that it can work and then detailed explanations of how to overcome common obstacles that are encountered. Cohn does all of this very well; this book is an excellent point to begin the study and adoption of Scrum.
Published in the online Journal of Object Technology, reprinted with permission.
Advice for the harder stuff - how to introduce and spread Scrum, how to get people to let go of doing by design at the start of the project, how to deliver software that works by the end of each sprint, what managers do, and more.
The solutions presented are generally clear and do not claim to be silver bullets. The author provided a good balance between formal and informal solutions that fit our goals well. Definitely a useful read for everyone involved in transition from traditional development to more agile methods, even those on the periphery of actual development having to support the team(s).
It also shows that this book is targeted at people who are looking to migrate a company's practices over to scrum or are in the process of a transition and gives a lot of advice and techniques that the author has used to perform such transitions in the past.
I've put this back to my 'to-read' pile so I can pick it up again once I've gotten a better basic comprehension of scrum principles and practices
This book is most applicable to organisations that are just starting out with Scrum (although a basic understanding of the artifacts / roles / etc. is assumed), or are having problems adapting it. There are lots of examples for organisations of any size (including entire chapters on adapting Scrum to massive projects, dealing with non-colocated teams, etc.), although the primary focus seems to be on midsized colocated companies (e.g. having 5-6 teams of no more than 8 people).
Understanding the mechanics of an agile process is just not enough. The quest of transitioning a company to agile is hard, full of mysteries, and also never ending :-).
This book is a distillation of everything Mike Cohn has learned over the years working with many many companies that are trying to become more agile.
