A Little Book about Requirements and User Stories
This book is 100% complete
Completed on 2017-04-04
About the Book
User Stories and more - well, a bit about requirements and backlogs actually.
- How to Write Small Stories That Still Have Value
- They Can Help You Write Better User Stories
- Are systems systems role?
- Stories, Epics, and Tasks: Organizing Agile Requirements
- Defining Acceptance Criteria for Agile Requirements
- Acceptance criteria, Specifications and tests
- Definition of Done
- Non-functional requirements and what we can learn from them
- Managing dependencies between stories
- Assigning value
- Forward planning
- Backlog management
- About the author
1. Conversation and benefit
- A Placeholder for a Conversation
- Each Story Has Business Benefit
2. Small and beneficial
- A Balancing Act
- How Small Is “Small”?
- So, What’s the Right Size?
- Practice Makes Progress
3. Assessing the Business Value of Agile User Stories
- Calculating Business Value
- Assessing Cost Savings
- Time as a Business Factor
- The Importance of a Company Strategy
4. As a Who?
- “As a User”? You Can Do Better!
- Roles, Personas, and Stakeholders
- Don’t Write Stories about the Team
- Are systems roles?
- Conversation forgives and resolves
5. Stories, Epics, and Tasks
- Stories up and down
- Go Large with Epics
- Go Small with Tasks
- Three Organizational Levels
- Color Coding and Planning
- Making Use of Your Choices
6. Defining Acceptance Criteria
- Acceptance Criteria and Testers
- The Level of Detail
- The Right Time to Define
- Acceptance Criteria in Action
7. Acceptance Criteria, Specifications, and Tests
- Splitting Stories by Acceptance Criteria
- Specifications and Tests
- Specification by Example
- Test Automation: More Than Fast
8. Definition of Done
- Acceptance Criteria or Definition of Done?
- Task Twist
- Working within Columns
- Reviewing and Updating the Definition
9. Working with Nonfunctional Requirements
- Nonfunctional User Stories
- Specifying the Requirements
- Constraints and Value
- Opportunities to Benefit
- Seeking Out the Real Benefit
- Evaluation: Closing the Loop
11. Estimating Business Value
- Estimating the Business Value
- The Result: Prioritization and Conversation
12. Effects of Time on Value
- Value before Estimates
- Engineer within Constraints
- The Cost of Delay
- Time, Value, and Risk
13. Maximising return on investment
- More to Modeling and Calculating ROI
- Value-Based Prioritization
- Next Stop: Continuous Delivery
- Story by Story
14. Writing stories - where do I begin?
- Solo brainstorm
- Group brainstorm
- Write as you visit
- Big requirements doc
- Work continues
15. Backlog structure
- Two backlogs good
- Three backlogs better
- Stories, PBIs, JBTD, etc. etc.
- Use cases
- Persona stories
17. Last words of advice
- Keep them Short
- Break, don’t bend, the format
- So that
- Context is important
- Not an analysis technique
Appendix: Requirements and Specifications
- An example
- Enter the Iteration
- And tests
- Automated acceptance tests: the new formal methods
- Knowledge and Trust
Quick User Stories FAQ
- What is the right size for a User Story?
- When is the conversation?
- How do I determine business value?
- How do I make my User Stories smaller?
- When do I use a Story and when do I use and Epic?
- How big should my backlog be before we start coding?
- How do I write strong User Stories?
- When is a User Story ready to go to development?
- Acknowledgements and history
The Leanpub 45-day 100% Happiness Guarantee
Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms...