As readers of this blog know, I’ve been using my previous book, Scaling Software Agility: Best Practices for Large Enterprises, as a reference (along with many others) to help software enterprises become more agile. In the course of many engagements, a recurring theme keeps popping up, “How do we handle requirements at scale in an agile environment?” I’ve been addressing some of the answers in various blog posts and whitepapers (see Agile Requirements category and A Lean and Scalable Requirements Model for Agile Enterprises.) Also, I’ve written fairly extensively on the requirements topic in the past, in Managing Software Requirements: First and Second Editions, from Addison-Wesley.
In the last few years, I’ve learned a lot of practical approaches to managing requirements for systems, both small and large, in an agile manner. In addition, other agilists have been thinking about this problem as well and have made substantial contributions to the art. Although I tried to duck the “write another book” issue”, it just wouldn’t go away, so in a moment of temporary insanity, I committed to writing it. The book Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise has just been published by Addison-Wesley.
Here’s the back cover introductory text:
“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.
And here’s an overview of the book, taken from the “Front Matter”.