Software in 30 Days: How Agile Managers Beat the Odds – A Book Review
Software in 30 Days: How Agile Managers Beat the Odds, Delight Their Customers, and Leave Competitors in the Dust is about Agile and Scrum software development. It discusses the problem of why current software organizations are slow in developing software. It reviews current and faulty processes, and presents a better alternative. The book explains in detail how organizations can produce usable and valuable software quickly and flexibly through Scrum.
Software in 30 Days first paperback edition measures about 7.3 in. wide, 0.6 in. thick, and 9.2 in. tall. It ships about 1 pound. It has 216 pages divided in 10 chapters. It is available in paperback and Kindle formats. Publication was in May 2012 by Wiley publishing in English. ISBN-10: 1118206665; ISBN-13: 978-1118206669
Software in 30 Days is for business owners, product development managers, IT managers, and other business managers who use software in their organization or company. The book is written for leaders who do not build software themselves, but use software in their organization.
What Customers Say
Alan L. (Amazon) stated that he recommends Software in 30 Days for technology professionals in all levels. The targeted audience are executives and management but can still provide technology professionals the larger picture not usually seen in more technical Scrum guides. The authors were able to explain and provide examples of the value of following Agile philosophy with the Scrum framework.
Jesse H. (Goodreads) rated it 4 out 5 stars. He stated that he read the book after getting his Professional Scrum Master certification. He described the chapters as relatively short but with great real-life examples. It also provided good explanation of the different roles, ceremonies and values used in Scrum. It achieves the goal of making the reader understand well what Scrum will change in the organization, but not so much how to do Scrum itself.
Eugene P. (Amazon) stated that Software in 30 Days did not meet his personal expectations. He believed that it is really written for business owners. As a Scrum team member, it was not the right book. He felt that he was reading an advertisement, persuading him to use Scrum.
Content, Approach, Style
Content: Software in 30 Days is divided in 2 sections. The first section discusses the crisis in software development, how the waterfall development process is not suitable, and the alternative of using a better process through Scrum. The second section provides more details about Scrum implementations, in a project level up to the enterprise level. It also discussed more details about burn-down chart, 30-day sprints, productivity measurements and more. The book also contains 3 appendices about terminology, the Scrum guide, and a plan for achieving enterprise agility.
Approach/Tone: The authors, who are the co-founders of Scrum, use an encouraging tone in promoting to the readers the viable alternative of using Scrum. They back up their suggestions with real-life examples that provides proof and evidence of the value and reliability of the suggested framework.
Style: The book uses paragraphs of readable length. It is organized in such a way that the reader is presented with the current situation and problem, and then followed by the suggested solution and its details. Some technical terminologies are used but an appendix for these terms for easier understanding is also available at the end. Figures, lists and case studies are included to support or emphasize the ideas conveyed.
Why Buy the Book
Business owners and managers who rely on software for their organization to become profitable should consider reading this book. Agile and Scrum have transformed some organizations for the better, making them more productive and competitive. It has also changed how development teams approach building usable and valuable software, either for internal or external customers, in a more efficient manner. If one’s organization need to address slow, costly and inefficient software development, then this book may offer real solutions.
Ken Schwaber is the President of Scrum.org, a provider of Scrum training, assessment and certification for Scrum Masters and Scrum Developers. Ken has over 30 years of experience in the software industry. He is one of the signatories of the Agile Manifesto in 2001. He created Scrum with Jeff Sutherland. Ken subsequently founded the Agile Alliance and the Scrum Alliance. In 2009, he founded Scrum.org with the mission to improve the profession of software delivery. He also has written other books about Scrum.
Jeff Sutherland is the CEO of Scrum, Inc., a Scrum training and consultancy company in Boston, MA, USA. Jeff received his B.S. degree in Engineering, Mathematics, and Economics at West Point. He is a fighter pilot in the US Air Force for 11 years. After the Air Force, he received his MS degree in Statistics, Mathematics, and Computer Science at Stanford University. Jeff received his PhD in Biometrics, Radiology and Preventive Medicine at the University of Colorado. Over the years, he has been the VP of Engineering, CTO or CEO of 11 software companies. Jeff was among those who signed the Agile Manifesto and co-created Scrum with Schwaber. He founded Scrum Inc in 2006. He has written and co-written several books, including Scrum: The Art of Doing Twice the Work in Half the Time.