Software in 30 days how agile managers beat the odds

Software in 30 Days. How Agile Managers Beat the Odds, Delight Their Customers, And Leave Competitors In the Dust

Скачать книгу

О книге «Software in 30 Days. How Agile Managers Beat the Odds, Delight Their Customers, And Leave Competitors In the Dust»

A radical approach to getting IT projects done faster and cheaper than anyone thinks possible Software in 30 Days summarizes the Agile and Scrum software development method, which allows creation of game-changing software, in just 30 days. Projects that use it are three times more successful than those that don’t. Software in 30 Days is for the business manager, the entrepreneur, the product development manager, or IT manager who wants to develop software better and faster than they now believe possible. Learn how this unorthodox process works, how to get started, and how to succeed. Control risk, manage projects, and have your people succeed with simple but profound shifts in the thinking. The authors explain powerful concepts such as the art of the possible, bottom-up intelligence, and why it’s good to fail early—all with no risk greater than thirty days. The productivity gain vs traditional «waterfall» methods has been over 100% on many projects Author Ken Schwaber is a co-founder of the Agile software movement, and co-creator, with Jeff Sutherland, of the «Scrum» technique for building software in 30 days Coauthor Jeff Sutherland was cosigner of the Agile Manifesto, which marked the start of the Agile movement Software in 30 Days is a must-read for all managers and business owners who use software in their organizations or in their products and want to stop the cycle of slow, expensive software development. Programmers will want to buy copies for their managers and their customers so they will know how to collaborate to get the best work possible.

На нашем сайте можно скачать книгу «Software in 30 Days. How Agile Managers Beat the Odds, Delight Their Customers, And Leave Competitors In the Dust» в формате pdf или читать онлайн. Здесь так же можно перед прочтением обратиться к отзывам читателей, уже знакомых с книгой, и узнать их мнение. В интернет-магазине нашего партнера вы можете купить и прочитать книгу в бумажном варианте.

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.

Book Details

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

Price

Target Audience

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.

Software in 30 Days. How Agile Managers Beat the Odds, Delight Their Customers, And Leave Competitors In the Dust

Посоветуйте книгу друзьям! Друзьям – скидка 10%, вам – рубли

Эта и ещё 2 книги за 399 ₽

A radical approach to getting IT projects done faster and cheaper than anyone thinks possible Software in 30 Days summarizes the Agile and Scrum software development method, which allows creation of game-changing software, in just 30 days. Projects that use it are three times more successful than those that don’t. Software in 30 Days is for the business manager, the entrepreneur, the product development manager, or IT manager who wants to develop software better and faster than they now believe possible. Learn how this unorthodox process works, how to get started, and how to succeed. Control risk, manage projects, and have your people succeed with simple but profound shifts in the thinking. The authors explain powerful concepts such as the art of the possible, bottom-up intelligence, and why it’s good to fail early—all with no risk greater than thirty days. The productivity gain vs traditional «waterfall» methods has been over 100% on many projects Author Ken Schwaber is a co-founder of the Agile software movement, and co-creator, with Jeff Sutherland, of the «Scrum» technique for building software in 30 days Coauthor Jeff Sutherland was cosigner of the Agile Manifesto, which marked the start of the Agile movement Software in 30 Days is a must-read for all managers and business owners who use software in their organizations or in their products and want to stop the cycle of slow, expensive software development. Programmers will want to buy copies for their managers and their customers so they will know how to collaborate to get the best work possible.

Software in 30 Days: How Agile Managers Beat the Odds, Delight Their Customers, And Leave Competitors In the Dust

Read it now on the O’Reilly learning platform with a 10-day free trial.

O’Reilly members get unlimited access to live online training experiences, plus books, videos, and digital content from O’Reilly and nearly 200 trusted publishing partners.

Book description

A radical approach to getting IT projects done faster and cheaper than anyone thinks possible

Software in 30 Days summarizes the Agile and Scrum software development method, which allows creation of game-changing software, in just 30 days. Projects that use it are three times more successful than those that don’t. Software in 30 Days is for the business manager, the entrepreneur, the product development manager, or IT manager who wants to develop software better and faster than they now believe possible. Learn how this unorthodox process works, how to get started, and how to succeed. Control risk, manage projects, and have your people succeed with simple but profound shifts in the thinking.

The authors explain powerful concepts such as the art of the possible, bottom-up intelligence, and why it’s good to fail early—all with no risk greater than thirty days.

The productivity gain vs traditional «waterfall» methods has been over 100% on many projects

Author Ken Schwaber is a co-founder of the Agile software movement, and co-creator, with Jeff Sutherland, of the «Scrum» technique for building software in 30 days

Coauthor Jeff Sutherland was cosigner of the Agile Manifesto, which marked the start of the Agile movement

Software in 30 Days is a must-read for all managers and business owners who use software in their organizations or in their products and want to stop the cycle of slow, expensive software development. Programmers will want to buy copies for their managers and their customers so they will know how to collaborate to get the best work possible.

Software in 30 Days: How Agile Managers Beat the Odds, Delight Their Customers, And Leave Competitors In the Dust by

Get full access to Software in 30 Days: How Agile Managers Beat the Odds, Delight Their Customers, And Leave Competitors In the Dust and 60K+ other titles, with free 10-day trial of O’Reilly.

There’s also live online events, interactive content, certification prep materials, and more.

Appendix 2: The Scrum Guide

The Definitive Guide to Scrum: The Rules of the Game

Developed and sustained by Ken Schwaber and Jeff Sutherland

Table of Contents

Article I. Purpose of the Scrum Guide

Scrum is a framework for developing and sustaining complex products. This Guide contains the definition of Scrum. This definition consists of Scrum’s roles, events, artifacts, and the rules that bind them together. Ken Schwaber and Jeff Sutherland developed Scrum; the Scrum Guide is written and provided by them. Together, they stand behind the Scrum Guide.

Article II. Scrum Overview

Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. Scrum is:

Lightweight

Get Software in 30 Days: How Agile Managers Beat the Odds, Delight Their Customers, And Leave Competitors In the Dust now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.