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 "e;waterfall"e; 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 "e;Scrum"e; 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.

A radical approach to getting IT projects done faster andcheaper than anyone thinks possibleSoftware in 30 Days summarizes the Agile and Scrumsoftware development method, which allows creation of game-changingsoftware, in just 30 days. Projects that use it are three timesmore successful than those that don't. Software in 30 Daysis for the business manager, the entrepreneur, the productdevelopment manager, or IT manager who wants to develop softwarebetter and faster than they now believe possible. Learn how thisunorthodox process works, how to get started, and how to succeed.Control risk, manage projects, and have your people succeed withsimple but profound shifts in the thinking.The authors explain powerful concepts such as the art of thepossible, bottom-up intelligence, and why it's good to failearly--all with no risk greater than thirty days.* The productivity gain vs traditional "waterfall" methods hasbeen over 100% on many projects* Author Ken Schwaber is a co-founder of the Agile softwaremovement, and co-creator, with Jeff Sutherland, of the "Scrum"technique for building software in 30 days* Coauthor Jeff Sutherland was cosigner of the Agile Manifestowhich marked the start of the Agile movementSoftware in 30 Days is a must-read for all managers andbusiness owners who use software in their organizations or in theirproducts and want to stop the cycle of slow, expensive softwaredevelopment. Programmers will want to buy copies for their managersand their customers so they will know how to collaborate to get thebest work possible.

Section I: Why Every Business In The World Can Produce Software In Thirty DaysThis sections reviews how many organization struggle to develop software and how Software in Thirty Day's approach can eliminate the underlying problem.Chapter 1: The Crisis in Software: The Wrong Process Produces The Wrong ResultsFind out why so many software projects fail and why traditional methods are ill-suited to software development.Chapter 2: Scrum: The Right Process Produces the Right ResultsUnderstand the shift in thinking necessary to eliminate software project failure and deliver software in 30 days.Chapter 3: Try It Yourself: The PilotYou are interested. Learn how to run a pilot project that will successfully help you determine what to do next.Chapter 4: What Can I Do?Learn what you, as a manager, can do to make Software in 30 Days successful.Section II: Why Every Business In The World Can Produce Software In Thirty DaysThis section address how you can implement and embed Software in Thirty Days in your organization.Chapter 5: Getting Started with ScrumUnderstand how Scrum works.Chapter 6: Scrum at the Project LevelLearn how to launch Scrum on a single project.Chapter 7: Develop a Scrum CapabilityLearn how to develop a Scrum capability in your organization.Chapter 8: Scrum at the Enterprise LevelConsider spreading Scrum throughout the enterprise.Appendices1: TerminologyLook up terminology used in this book2: Scrum GuideRead the canonical guide to Scrum3: A Playbook for Achieving Enterprise AgilityA Scrum enterprise adoption playbook in use since 1995.