Contents


Preface
Acknowledgments
About the author
About the cover illustration

PART 1 Getting Started

Chapter 1 Key benefits
Implementing changes more efficiently
Higher product quality
Less rework
Better work alignment
Remember
Chapter 2 Key process patterns
Deriving scope from goals
Specifying collaboratively
Illustrating using examples
Refining the specification
Automating validation without changing specifications
Validating frequently
Evolving a documentation system
A practical example
Remember
Chapter 3 Living documentation
Why we need authoritative documentation
Tests can be good documentation
Creating documentation from executable specifications
Benefits of the documentation-centric model
Remember
Chapter 4 Initiating the changes
How to begin changing the process
How to begin changing the team culture
How teams integrated collaboration into flows and iterations
Dealing with sign-off and traceability
Warning signs
Remember

PART 2 Key process patterns

Chapter 5 Deriving scope from goals
Building the right scope
Collaborating on scope without high-level control
Further information
Remember
Chapter 6 Specifying collaboratively
Why do we need to collaborate on specifications?
The most popular collaborative models
Preparing for collaboration
Choosing a collaboration model
Remember
Chapter 7 Illustrating using examples
Illustrating using examples: an example
Examples should be precise
Examples should be complete
Examples should be realistic
Examples should be easy to understand
Illustrating nonfunctional requirements
Remember
Chapter 8 Refining the specification
An example of a good specification
An example of a bad specification
What to focus on when refining specifications
Refining in practice
Remember
Chapter 9 Automating validation without changing specifications
Is automation required at all?
Starting with automation
Managing the automation layer
Automating user interfaces
Test data management
Remember
Chapter 10 Validating frequently
Reducing unreliability
Getting feedback faster
Managing failing tests
Remember
Chapter 11 Evolving a documentation system
Living documentation should be easy to understand
Living documentation should be consistent
Living documentation should be organized for easy access
Listen to your living documentation
Remember

PART 3 Case studies

Chapter 12 uSwitch
Starting to change the process
Optimizing the process
The current process
The result
Key lessons
Chapter 13 RainStor
Changing the process
The current process
Key lessons
Chapter 14 Iowa Student Loan
Changing the process
Optimizing the process
Living documentation as competitive advantage
Key lessons
Chapter 15 Sabre Airline Solutions
Changing the process
Improving collaboration
The result
Key lessons
Chapter 16 ePlan Services
Changing the process
Living documentation
Current process
Key lessons
Chapter 17 Songkick
Changing the process
Current process
Key lessons
Chapter 18 Concluding thoughts
Collaboration on requirements builds trust between stakeholders and delivery team members
Collaboration requires preparation
There are many different ways to collaborate
Looking at the end goal as business process documentation is a useful model
Long-term value comes from living documentation


Appendix A Resources
Index