What do you think?
Rate this book
Софт за 30 дней. Как Scrum делает невозможное возможным
Создатели методики Scrum рассказывают, как реализовывать IT-проекты дешевле и быстрее, чем это кажется возможным.
Проекты, в которых используются подходы Agile и Scrum, успешнее других. Эти методики позволяют создавать программное обеспечение за 30 дней или даже быстрее, а продуктивность работы с ними значительно (во многих случаях более чем на 100%) возрастает по сравнению с традиционным каскадным подходом.
Прочитав эту книгу, вы познакомитесь с методикой Scrum и узнаете, как этот нестандартный подход работает и как начать применять его в своем бизнесе, чтобы сделать процесс разработки эффективным, быстрым и гибким.
В приложения к книге вошла «Библия скрама», как ее неофициально называют — The Scrum Guide. Это официальное руководство по скраму, созданное основателями этой методики Швабером и Сазерлендом. В нем описаны все термины, роли и процессы.
От авторов
Мы обращаемся к каждому лидеру в организации, который хочет создавать лучшие программные продукты с лучшими характеристиками и предсказуемостью. Индустрия программного обеспечения изменяется и радикально улучшается. Неопределенность, риск и потери, к которым вы привыкли, больше не неизбежны. Мы имеем за плечами данные 20-ти лет работы с организациями, которые уже перешли на новый уровень. Мы хотим, чтобы и вы сделали этот шаг.
Мы хотим, чтобы вы были способны предсказуемо создавать полезное, качественное программное обеспечение с управляемыми рисками.
Мы обращаемся к вам по двум причинам.
Во-первых, в течение сорока лет вы страдали от плохого обслуживания в индустрии программного обеспечения, ненамеренно, но неизбежно. Мы хотим вернуть ваше доверие.
Во-вторых, программное обеспечение — это уже не только специализированный инструментарий для профессионалов. Программы теперь везде, выполняют все более и более важные операции в нашем обществе. Мы хотим, чтобы вы были способны создать программное обеспечение, на которое мы все можем надежно полагаться.
Мы надеемся, что сможем достичь этих целей нашей книгой.
Для кого эта книга
Эта книга поможет руководителям и менеджерам компаний, которые хотят покончить с дорогим и медленным циклом разработки ПО.
Проекты, в которых используются подходы Agile и Scrum, успешнее других. Эти методики позволяют создавать программное обеспечение за 30 дней или даже быстрее, а продуктивность работы с ними значительно (во многих случаях более чем на 100%) возрастает по сравнению с традиционным каскадным подходом.
Прочитав эту книгу, вы познакомитесь с методикой Scrum и узнаете, как этот нестандартный подход работает и как начать применять его в своем бизнесе, чтобы сделать процесс разработки эффективным, быстрым и гибким.
В приложения к книге вошла «Библия скрама», как ее неофициально называют — The Scrum Guide. Это официальное руководство по скраму, созданное основателями этой методики Швабером и Сазерлендом. В нем описаны все термины, роли и процессы.
От авторов
Мы обращаемся к каждому лидеру в организации, который хочет создавать лучшие программные продукты с лучшими характеристиками и предсказуемостью. Индустрия программного обеспечения изменяется и радикально улучшается. Неопределенность, риск и потери, к которым вы привыкли, больше не неизбежны. Мы имеем за плечами данные 20-ти лет работы с организациями, которые уже перешли на новый уровень. Мы хотим, чтобы и вы сделали этот шаг.
Мы хотим, чтобы вы были способны предсказуемо создавать полезное, качественное программное обеспечение с управляемыми рисками.
Мы обращаемся к вам по двум причинам.
Во-первых, в течение сорока лет вы страдали от плохого обслуживания в индустрии программного обеспечения, ненамеренно, но неизбежно. Мы хотим вернуть ваше доверие.
Во-вторых, программное обеспечение — это уже не только специализированный инструментарий для профессионалов. Программы теперь везде, выполняют все более и более важные операции в нашем обществе. Мы хотим, чтобы вы были способны создать программное обеспечение, на которое мы все можем надежно полагаться.
Мы надеемся, что сможем достичь этих целей нашей книгой.
Для кого эта книга
Эта книга поможет руководителям и менеджерам компаний, которые хотят покончить с дорогим и медленным циклом разработки ПО.
256 pages, Hardcover
First published March 21, 2012
66 people are currently reading
628 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 36 reviews
February 3, 2013
Badly written Scrum marketing brochure.
October 17, 2015
I read this book *after* getting my Professional Scrum Master I certification and found the content interesting mostly for the examples provided. The book seems to rely on the power of repetition, the simple process and the cadence a lot. The chapters are relatively short, most use a real life example to show how the scrum process changes not only the projects, but also the organisation around it to deliver more value in less or equal amounts of time.
The second half of the book is made up of a number of appendices. These provide very useful management abstracts of the roles, the ceremonies and the values which Scrum is built upon.
I didn't find contents very useful to learn how to do Scrum. It is a great way to understand what Scrum will change to your organisation, how you can embed it in the enterprise and what it will and will not deliver. Which seems logical since the prime audience for the book is the Management of a company or Project organisation.
The second half of the book is made up of a number of appendices. These provide very useful management abstracts of the roles, the ceremonies and the values which Scrum is built upon.
I didn't find contents very useful to learn how to do Scrum. It is a great way to understand what Scrum will change to your organisation, how you can embed it in the enterprise and what it will and will not deliver. Which seems logical since the prime audience for the book is the Management of a company or Project organisation.
December 24, 2019
I read the book because it is on the reading list for PSM I but It left me quite unsatisfied. Maybe this book is a good start for managers or CxOs new to scrum or agile. As a scrum practitioner I did not get much out of it. There is a lot of story telling, which is generally a good thing, but the stories did not really add much insights and felt quite repetitive.
January 24, 2016
This book provides a good overview of Scrum targeted to CXOs and senior managers considering adopting, or transitioning to Agile. The essential matters and challenges are laid bare, in a clear and straight-forward manner, telling it like it is. I found the references to real-world projects, and latest project history data very useful in reinforcing the message that there is indeed value in moving to Scrum.
Having said that, Schwaber & Sutherland hide nothing and make it clear that Scrum might seem easy to adopt at the surface, but is a painstaking process of transformation to get right, and that organisations should approach Scrum in a careful, methodical approach.
I was comforted by the descriptions of scaling agile to enterprise-wide projects, and the challenges with distributed teams, since it adds credence to my own experience and writings on Agile:
http://khanmjk-outlet.blogspot.com/20...
Too often than not, people get hooked to Agile/Scrum for the wrong reasons, lacking the appreciation of the sound engineering practices that are mandatory. People often misinterpret Scrum/Agile as a development transformation, instead has a cross-organisation, cross-team and multi-disciplinary impact.
Often overlooked is the subject of Quality. "Software in 30 days" is about delivering complete functionality, fully tested and integrated, of shippable quality. If you're not doing that, you're not doing Scrum. The book cites useful references as a constant lookup/refresher. A note on quality from the reference "...Customers often pressure development organisations to deliver features faster than is feasible. Some organisations accommodate this by reducing the quality of the product, dropping re-factoring, cutting test efforts and other solid engineering practices...not supportable with Scrum practices.....succumb to this pressure eventually build design dead systems...."
If I were to criticize one aspect of the book is the lack of appreciation for globally distributed teams, built not from permanent employees in the organisation, but offshore contractors. I think this deserves more work because I'm not yet sold on the idea of self organising teams if the bulk of the work is offshore - that comes with a whole world of challenges.
Nevertheless, I recommend this book to all, not only senior managers - I would also stress if this is your first time into Scrum/Agile, then read it once giving it a first pass, then read again thinking hard about the message and possible impact on your work, and give it a third read but this time producing your own plan of action / backlog as a result.
Then pick up Ken's other book "Agile Project Management with Scrum" to get your hands dirty...
Having said that, Schwaber & Sutherland hide nothing and make it clear that Scrum might seem easy to adopt at the surface, but is a painstaking process of transformation to get right, and that organisations should approach Scrum in a careful, methodical approach.
I was comforted by the descriptions of scaling agile to enterprise-wide projects, and the challenges with distributed teams, since it adds credence to my own experience and writings on Agile:
http://khanmjk-outlet.blogspot.com/20...
Too often than not, people get hooked to Agile/Scrum for the wrong reasons, lacking the appreciation of the sound engineering practices that are mandatory. People often misinterpret Scrum/Agile as a development transformation, instead has a cross-organisation, cross-team and multi-disciplinary impact.
Often overlooked is the subject of Quality. "Software in 30 days" is about delivering complete functionality, fully tested and integrated, of shippable quality. If you're not doing that, you're not doing Scrum. The book cites useful references as a constant lookup/refresher. A note on quality from the reference "...Customers often pressure development organisations to deliver features faster than is feasible. Some organisations accommodate this by reducing the quality of the product, dropping re-factoring, cutting test efforts and other solid engineering practices...not supportable with Scrum practices.....succumb to this pressure eventually build design dead systems...."
If I were to criticize one aspect of the book is the lack of appreciation for globally distributed teams, built not from permanent employees in the organisation, but offshore contractors. I think this deserves more work because I'm not yet sold on the idea of self organising teams if the bulk of the work is offshore - that comes with a whole world of challenges.
Nevertheless, I recommend this book to all, not only senior managers - I would also stress if this is your first time into Scrum/Agile, then read it once giving it a first pass, then read again thinking hard about the message and possible impact on your work, and give it a third read but this time producing your own plan of action / backlog as a result.
Then pick up Ken's other book "Agile Project Management with Scrum" to get your hands dirty...
October 6, 2012
Clearly lays out the case for an Agile (specifically Scrum) approach to product development. If you're not doing Agile or Scrum this is as good an introduction as you could hope for from the co-creators of Scrum.
August 15, 2012
Very management focused, but not bad.
September 6, 2015
Bit theoretical. Not an interesting read so can't continue from start to finish. But I will refer pages at random.
March 4, 2020
Fortlaufende Rechtfertigung warum Scrum gut ist. Ansonsten nix Beeindruckendes.
December 6, 2017
Authors said upfront that this book is for CXO or top executives. If you already have strong background in Scrum/Agile, you might use some of the stories/examples (and to some extends, more arguments) from this book to "sell" to "others" (either subordinates, or other departments, sales, marketing, etc.) if there are resistances to change.
If you don't, you might not learn much "how" from this book, but at least some of the "what"; for the "how", it's much better if you read other agile "bibles" and/or have external trainers/coaches.
It's weird that https://www.scrum.org/resources/sugge... recommends this book for the topic of "Maximizing Value", because I couldn't learn much from it, while it's said that "The Lean Startup" is doing much better job.
If you don't, you might not learn much "how" from this book, but at least some of the "what"; for the "how", it's much better if you read other agile "bibles" and/or have external trainers/coaches.
It's weird that https://www.scrum.org/resources/sugge... recommends this book for the topic of "Maximizing Value", because I couldn't learn much from it, while it's said that "The Lean Startup" is doing much better job.
July 5, 2023
A short masterpiece about SCRUM that can be used in any kind of program development.
I would definitely recommend as a starter to newby and to update SCRUM routines for middle, for grown up teams I would say there is not much new, but good to update that for the teams - just use this book.
There are schemes, research questions and recommendation on sprint activities. How the measure, what lenght should I choose, what members should be involved.
A book for 1 day to read, but can be used daily, 15 minutes, such as it should be in SCRUM!)
I would definitely recommend as a starter to newby and to update SCRUM routines for middle, for grown up teams I would say there is not much new, but good to update that for the teams - just use this book.
There are schemes, research questions and recommendation on sprint activities. How the measure, what lenght should I choose, what members should be involved.
A book for 1 day to read, but can be used daily, 15 minutes, such as it should be in SCRUM!)
December 31, 2017
Great read and to the point
Questions about who's a scrum master and what's their job. And similar questions for other scrum roles. This book clarifies such questions with anecdotes and real examples of how efficient managers execute scrum in different development and organizational transformation. You can see the experience of the authors poured very thoughtfully in this book. It's a great read and a must for every srum and agile software development enthusiast.
Questions about who's a scrum master and what's their job. And similar questions for other scrum roles. This book clarifies such questions with anecdotes and real examples of how efficient managers execute scrum in different development and organizational transformation. You can see the experience of the authors poured very thoughtfully in this book. It's a great read and a must for every srum and agile software development enthusiast.
April 12, 2018
A good overview of scrum and what it takes to successfully utilize it. It covers important general principles and common challenges. It did have a more managerial focus with its content on adopting and scaling scrum in big organizations. I would be interested in reading more about specific case studies and how scrum activities were conducted there, the way artifacts were created/managed, etc.
August 3, 2018
A very interesting book. Though it's written for managers, it also delivers a profounder understanding of Scrum, and what one needs to keep in mind when using and scaling it.
it was a very good read and extremely recommendable for anyone interested to abandon the old ways of software development management and welcome the joys of common sense and sensible methodology.
it was a very good read and extremely recommendable for anyone interested to abandon the old ways of software development management and welcome the joys of common sense and sensible methodology.
December 27, 2018
Is a good book if you want to learn a little bit more about the Scrum framework. I would recommend this book when you have some basic knowledge about Scrum, gives you a better clue about what to do, and how does it work.
June 7, 2019
"If one can establish a complete vision, define all of the requirements of the vision, and then devise the detailed plan to turn the requirements into the vision, then a predictive process will work." Don't get me wrong, I liked the book, it just gets to a point where it repeats itself too many times.
March 22, 2024
Very informative and clear on what Scrum is and is not
I liked the clarity and simplicity of the book
The content is just simple to digest although implementing is something else.
every informative book
I liked the clarity and simplicity of the book
The content is just simple to digest although implementing is something else.
every informative book
June 15, 2017
Awesome read with some really good philosophy on Scrum by the creator himself. Great examples and some really good insight.
January 8, 2018
Неплохая книга про гибкие методологии и фреймворк Scrum, но очень много воды. Структура книги показалась странной, однако про масштабирование Scrum мысли интересные.
December 4, 2018
Good overview of how Agile can help you as a manager trying to accomplish a software project.
December 28, 2018
Странная книга. 3 раздела об одном и том же, но разной длины. Очень много отвлеченных историй без хорошей практики. После прочтения мало что остается в голове. Советую читать только третью часть.
December 11, 2019
Pro re nata, which means "take when needed".
Developer productivity arises from not being interrupted.
Empiricism does not create certanity; it makes one aware of the possibilities.
Developer productivity arises from not being interrupted.
Empiricism does not create certanity; it makes one aware of the possibilities.
August 19, 2020
A good intro, but soft of basic.
March 22, 2017
A good book to sell 'Scrum' to high level executives, has several success stories that emphasize the importance of agile. Before reading it, make sure you go with the right expectations, otherwise you'll be disappointed.
February 6, 2017
tl;dr Version: YMMV (Your Mileage May Vary)
The authors state that the goal of the book is to provide an overview of agile methodology, but it only talks about Scrum. It's geared towards executives or decision makers who want more information & learn about its benefits. So, it's not particularly prescriptive or in-depth. I found it a little on the light side, but the information is well laid out with a fair number of case studies, so it doesn't get tedious.
You can read a more detailed review on my blog.
The authors state that the goal of the book is to provide an overview of agile methodology, but it only talks about Scrum. It's geared towards executives or decision makers who want more information & learn about its benefits. So, it's not particularly prescriptive or in-depth. I found it a little on the light side, but the information is well laid out with a fair number of case studies, so it doesn't get tedious.
You can read a more detailed review on my blog.
March 11, 2014
A good book to start with scrum for Managers, Ceo's and the likes. But I have to admit that it is a great selling booking. Selling Scrum. But if you really want to go in-depth into the workings of Scrum you better find a trainer or coach to help you along. I recommend this book to the managers I work with. At least you should have read this book before you can argue with me that Scrum is not something that will work in your company.
December 14, 2013
if you have only a day to grasp the main concept of scrum, the this book is for you. both author talk about the main concept of scrum and how it can help to fasten a software development time. As it's said on the prolog this book it's intended for managers level and above, so if you expect for a deeper discusson on scrum then this is not for you.
October 11, 2015
The book was fine. I didn't realize that it was meant for CEO's/senior managers. It was meant for people who are skeptical of Scrum and a sales pitch on why to use it. There were lots of case studies. I was bored because it was too high level and I'm already doing Scrum. The appendixes seem useful - glossary of words, the Scrum guide PDF and a script for a sprint.
June 2, 2013
This book is good as a support for conversations with CXO that want to start playing with Scrum or those who are already using Scrum(but…).
It's an overview of Scrum on a management point of view.
May sounds a bit like a commercial sometimes.
It's an overview of Scrum on a management point of view.
May sounds a bit like a commercial sometimes.
December 7, 2013
Read this book in preparation for Scrum Master certification. A good read for anyone looking for foundations of Lean product development and getting started on delivering software products using scrum.
April 16, 2014
The book contains some good ideas or points about how to implement Scrum in an organization. However, the content is entirely theoretical and repetitive, rather in some cases with advertising character, to which the Scrum Guide has been added to swell the number of pages.
Displaying 1 - 30 of 36 reviews