As readers of this blog know, I’ve been using my previous book, Scaling Software Agility: Best Practices for Large Enterprises, as a source reference to help large-scale software enterprises in becoming more agile. In the course of many engagements, a recurring theme keeps popping up, “How do I handle requirements at scale in an agile environment?” It’s a good question that deserves a thorough treatment of the subject and some practical answers. 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.
While thinking about this issue for the last few years, I’ve accumulated a lot of practical approaches to managing requirements for systems, both small and large, in an agile manner. In addition, several 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” issue, it just wouldn’t go away, so I’ve committed to writing it anyway. I’ve tentatively titled the book Agile Requirements: Lean Requirements Practices for Teams, Programs and the Enterprise and, with help from my co-author, Don Widrig, it should be published by Addison-Wesley sometime early next year.
Below is the Table of Contents we are working from now. Much of the book exists in draft from now ( I actually started writing last spring) , so don’t hesitate to contact me if you’re interested in helping me shape this book for final publication. On this resource page, I’m posting some of the interim content for public review. Yo can find those pieces in the table of contents,too.
Agile Requirements: Lean Requirements Practices for Software Teams, Programs and the Enterprise
Forward
Preface
About the Author
Front Matter
· Preface
· How to Read this Book
· Acknowledgements
Part I – Overview: The Big Picture
1. A Brief History of Software Requirements Methods
2. The Big Picture
The Big Picture of Enteprise Agility(whitepaper) (this is derived from Chapter 1, but is published, in stand-alone, whitepaper form).
3. Agile Requirements for the Project Team
4. Agile Requirements for the Program
5. Agile Requirements for the Portfolio
Case Study: Tendril Residential Energy Ecosystem
Part II – Agile Requirements for the Team
6. User Stories
User Story Primer (this is derived from Chapter 6, but is published, in stand-alone, whitepaper form).
7. Stakeholders, User Personas and User Experiences
8. Estimating and Velocity
9. Iterating
10. Acceptance Tests
11. Role of the Product Owner
Ch 11 Role of the Product Owner (Rev 12)
[...] Agile Requirements (the book) [...]
On page 11-4, footnote 3, you cite Pragmatic Marketing as Pragmatic Marketing Institute. The name is Pragmatic Marketing, Inc and website is http://www.pragmaticmarketing.com. If you’d like, you are welcome to reference http://www.pragmaticmarketing.com/pdf/Living_in_an_Agile_World.pdf which contains a view of the product manager vs product owner roles.
Your book is looking good! Keep it up!