A Little Book about Requirements and User Stories
A Little Book about Requirements and User Stories
$4.99
Minimum
$7.50
Suggested
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.

Chapters include:

  • 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

And maybe....

  • Forward planning
  • Backlog management
  • Estimation

Table of Contents

  • 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
  • 10. Stakeholders
    • 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
    • Finally
  • 16. Alternatives
    • Stories, PBIs, JBTD, etc. etc.
    • Use cases
    • Persona stories
    • Finally
  • 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
    • Specifications
    • An example
    • Enter the Iteration
    • And tests
    • Automated acceptance tests: the new formal methods
    • Knowledge and Trust
    • Conclusion
    • References
  • 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
  • History
  • Notes

Bundles that include this book

Agile Reader
A Little Book about Requirements and User Stories
2 Books
$9.98
Regular Price
$7.45
Bundle Price
Xanpan
A Little Book about Requirements and User Stories
Xanpan appendix - Management and team
3 Books
$15.93
Regular Price
$14.90
Bundle Price

About the Author

Allan Kelly
Allan Kelly

Allan Kelly works as an Agile Consultant, he advises and trains teams from many different companies and domains on adopting and deepen Agile practices and development in general. When he is not with clients he writes far too much.  He specialises in working with software product companies and aligning products and processes with company strategy.  He is the author of three books: "Xanpan - team centric Agile Software Development", "Business Patterns for Software Developers" and “Changing Software Development: Learning to be Agile”; the originator of Retrospective Dialogue Sheets and a regular conference speaker. 

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...

Write and Publish on Leanpub

Authors and publishers use Leanpub to publish amazing in-progress and completed ebooks, just like this one. You can use Leanpub to write, publish and sell your book as well! Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks. Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. It really is that easy.

Learn more about writing on Leanpub