Agile Software Requirements

Agile Software Requirements
Author :
Publisher : Addison-Wesley Professional
Total Pages : 977
Release :
ISBN-10 : 9780321685407
ISBN-13 : 0321685407
Rating : 4/5 (07 Downloads)

Book Synopsis Agile Software Requirements by : Dean Leffingwell

Download or read book Agile Software Requirements written by Dean Leffingwell and published by Addison-Wesley Professional. This book was released on 2010-12-27 with total page 977 pages. Available in PDF, EPUB and Kindle. Book excerpt: “We need better approaches to understanding and managing software requirements, and Dean provides them in this book. He draws ideas from three very useful intellectual pools: classical management practices, Agile methods, and lean product development. By combining the strengths of these three approaches, he has produced something that works better than any one in isolation.” –From the Foreword by Don Reinertsen, President of Reinertsen & Associates; author of Managing the Design Factory; and leading expert on rapid product development Effective requirements discovery and analysis is a critical best practice for serious application development. Until now, however, requirements and Agile methods have rarely coexisted peacefully. For many enterprises considering Agile approaches, the absence of effective and scalable Agile requirements processes has been a showstopper for Agile adoption. In Agile Software Requirements, Dean Leffingwell shows exactly how to create effective requirements in Agile environments. Part I presents the “big picture” of Agile requirements in the enterprise, and describes an overall process model for Agile requirements at the project team, program, and portfolio levels Part II describes a simple and lightweight, yet comprehensive model that Agile project teams can use to manage requirements Part III shows how to develop Agile requirements for complex systems that require the cooperation of multiple teams Part IV guides enterprises in developing Agile requirements for ever-larger “systems of systems,” application suites, and product portfolios This book will help you leverage the benefits of Agile without sacrificing the value of effective requirements discovery and analysis. You’ll find proven solutions you can apply right now–whether you’re a software developer or tester, executive, project/program manager, architect, or team leader.


Agile Software Requirements Related Books

Agile Software Requirements
Language: en
Pages: 977
Authors: Dean Leffingwell
Categories: Computers
Type: BOOK - Published: 2010-12-27 - Publisher: Addison-Wesley Professional

DOWNLOAD EBOOK

“We need better approaches to understanding and managing software requirements, and Dean provides them in this book. He draws ideas from three very useful int
The Art of Agile Development
Language: en
Pages: 436
Authors: James Shore
Categories: Computers
Type: BOOK - Published: 2008 - Publisher: "O'Reilly Media, Inc."

DOWNLOAD EBOOK

For those considering Extreme Programming, this book provides no-nonsense advice on agile planning, development, delivery, and management taken from the authors
Agile Software Development in the Large
Language: en
Pages: 249
Authors: Jutta Eckstein
Categories: Agile software development
Type: BOOK - Published: 2013 - Publisher: Pearson Education

DOWNLOAD EBOOK

Who Says Large Teams Can't Handle Agile Software Development? Agile or "lightweight" processes have revolutionized the software development industry. They're fa
Large-Scale Scrum
Language: en
Pages: 374
Authors: Craig Larman
Categories: Business & Economics
Type: BOOK - Published: 2016-09-30 - Publisher: Addison-Wesley Professional

DOWNLOAD EBOOK

The Go-To Resource for Large-Scale Organizations to Be Agile Rather than asking, “How can we do agile at scale in our big complex organization?” a different
Agile Software Development
Language: en
Pages: 193
Authors: Thomas Stober
Categories: Computers
Type: BOOK - Published: 2009-10-03 - Publisher: Springer Science & Business Media

DOWNLOAD EBOOK

Software Development is moving towards a more agile and more flexible approach. It turns out that the traditional "waterfall" model is not supportive in an envi