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 projectsAuthor 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 daysCoauthor 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.

For courses on Agile Software Development, Extreme Software Development or Advanced Software Engineering covering one of those topics.

The Agile software process allows companies to implement extreme programming quickly and immediately and to begin producing software incrementally in as little as 30 days. Scrum is the fastest, easiest to implement, and most widely accepted Agile process. This book shows readers how to use Scrum to quickly and seamlessly implement extreme programming while producing software. Readers will come to understand a new approach to systems development projects that cuts through the complexity and ambiguity of complex, emergent requirements and unstable technology to iteratively and quickly produce quality software.

The rules and practices for Scrum--a simple process for managing complex projects--are few, straightforward, and easy to learn. But Scrum's simplicity itself--its lack of prescription--can be disarming, and new practitioners often find themselves reverting to old project management habits and tools and yielding lesser results. In this illuminating series of case studies, Scrum co-creator and evangelist Ken Schwaber identifies the real-world lessons--the successes and failures--culled from his years of experience coaching companies in agile project management. Through them, you'll understand how to use Scrum to solve complex problems and drive better results--delivering more valuable software faster. Gain the foundation in Scrum theory--and practice--you need to: Rein in even the most complex, unwieldy projects Effectively manage unknown or changing product requirements Simplify the chain of command with self-managing development teams Receive clearer specifications--and feedback--from customers Greatly reduce project planning time and required tools Build--and release--products in 30-day cycles so clients get deliverables earlier Avoid missteps by regularly inspecting, reporting on, and fine-tuning projects Support multiple teams working on a large-scale project from many geographic locations Maximize return on investment