- Published 4/17/2015
- 1st Edition
With this ebook, the ALM Rangers share their best practices in managing solution requirements and shipping solutions in an agile environment, an environment where transparency, simplicity, and trust prevail. The ebook is for Agile development teams and their Scrum Masters who want to explore and learn from the authors’ “dogfooding” experiences and their continuous adaptation of software requirements management. Product Owners and other stakeholders will also find value in this ebook by learning how they can support their Agile development teams and by gaining an understanding of the constraints of open-source community projects.
Table of Contents
Foreword 7
Preface 8
Introduction 9
Who should read this book 9
Assumptions 9
This book might not be for you if . . . 9
Organization of this book 9
System requirements 10
Downloads: Toolbox samples 10
We need your candid feedback 11
Conventions and features in this book 11
Errata, updates, & book support 11
Free ebooks from Microsoft Press 12
We want to hear from you 12
Stay in touch 12
About us 13
Authors 13
Brian Blackman 13
Gordon Beeming 13
Michael Fourie 13
Willy-Peter Schaub 13
Coauthors and editors 14
Bijan Javidi 14
Jeff Beehler 14
Patricia Wagner 14
Acknowledgments 14
Chapter 1: Triage of ideas 15
Flights of ideas 15
Roles, responsibilities, and ownership 15
Idea management 16
Capturing ideas 16
Triaging ideas to meet priorities, strategies, and return on investment (ROI) 19
Identify passionate owners 23
Planning the kickoff to enable innovative teams 25
Motivation 25
Vision 26
Categorize solution 26
Objectives 27
Features 28
Roadmap 29
What about the orphaned ideas? 30
Scaling flights . . . how many are too many? 31
Visibility from start to finish 33
Dogfooding case study: Venturing into the cloud 37
Background information 38
Requirements and ownership triage 38
Key learnings 40
Chapter 2: Getting ready 41
Training-research-plan (TRP) 41
It all starts with the kickoff! 42
Planning the meeting 42
Hosting the meeting 43
Organizing the team 43
Objectives 44
Team structure 44
Portfolio “ideas” level 45
Solution “flights” level 45
Team “feature” level 45
Team infrastructure 45
Training . . . learning new things from the SMEs 50
Research . . . investigate and model requirements 51
Planning 51
Estimating and prioritization fundamentals 52
Release planning: Offline preparations 57
Release planning: virtualFace-to-virtualFace (vFace-to-vFace) 61
Schedule the infamous worldwide scrums 63
Summary of our process and requirement rudiments 63
Glimpse of tomorrow . . . tracking with an informative board 65
Dogfooding case study: Where is the fire?
