A Little Book about Requirements and User Stories (Little Book of User Stories: e-book and audio book)
A Little Book about Requirements and User Stories
Heuristics for requirements in an agile world
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
About the Author
Packages
The Book
PDF
EPUB
WEB
English
Little Book of User Stories: e-book and audio book
E-book and audio book versions of Little Book of Requirements and User Stories
PDF
EPUB
WEB
English
Bundles that include this book
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
The Leanpub 60 Day 100% Happiness Guarantee
Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
Now, this is technically risky for us, since you'll have the book or course files either way. But we're so confident in our products and services, and in our authors and readers, that we're happy to offer a full money back guarantee for everything we sell.
You can only find out how good something is by trying it, and because of our 100% money back guarantee there's literally no risk to do so!
So, there's no reason not to click the Add to Cart button, is there?
See full terms...
Earn $8 on a $10 Purchase, and $16 on a $20 Purchase
We pay 80% royalties on purchases of $7.99 or more, and 80% royalties minus a 50 cent flat fee on purchases between $0.99 and $7.98. You earn $8 on a $10 sale, and $16 on a $20 sale. So, if we sell 5000 non-refunded copies of your book for $20, you'll earn $80,000.
(Yes, some authors have already earned much more than that on Leanpub.)
In fact, authors have earnedover $13 millionwriting, publishing and selling on Leanpub.
Learn more about writing on Leanpub
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.
Learn more about Leanpub's ebook formats and where to read them
