
Unifying User Stories, Use Cases, Story Maps: The Power of Verbs (The Simplifying Series)
Description
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
Use cases, user stories, and story maps have been circling like comets, competing for the same energy of the same people at the same time. There is something obviously similar about all three but just exactly what isn't obvious.
In this ground-breaking book, Dr. Alistair Cockburn, noted expert on all three techniques, co-author of the Agile Manifesto, and author of the definitive work Writing Effective Use Cases, puts them all together, showing how they both complete and complement each other. Cockburn starts by attending to the seven key concepts without which none of them can be written well, and with mastery of which you can move freely between them. From there he breaks down user stories, then use cases, then story maps one by one, in clear and practical terms. Finally, he shows how to move between them, making them more effective in combination.
The book contains exercises and drills, making it suitable for self study and classroom teaching.
More details
Content
- Intro
- Preliminaries
- 1: Key concepts for all of them
- 1. Verbs imply durations.
- 2. Decompose verbs into shorter-duration verbs.
- 3. Manage precision
- 4. Decompose everything, not just the verbs.
- 5. Write from the user's perspective.
- 6. Write just the needs, not the encyclopedia.
- 7. Sacrifice perfection for readability.
- The Practical: How to do it.
- 2: About user stories
- 8. User stories are not requirements documents. They are tokens for work.
- 9. User stories can be about anything.
- 10. A user story should fit into a single iteration.
- 3: About use cases
- 11. A use case describes how a user achieves a goal with failures.
- 12. Use cases contain multiple scenarios.
- 13. Use cases nest within each other.
- 14. Use cases capture all - but only! - the behavioral requirements.
- 15. Use cases spec all sides of the system.
- 16. Use cases should be developed incrementally.
- 4: Relating user stories and use cases
- 17. Use cases and user stories have almost nothing in common.
- 18. User stories decompose forever, use cases don't.
- 19. User stories are as hard to write well as use cases are.
- 20. An "epic" is a user story without a development deadline. A use case makes a fine epic.
- 5: About story maps
- 21. Story maps are a 2D chart of storylines and work tokens.
- 22. The top rows show a coherent, useful release to the users.
- 23. Each column contains prioritized user stories per user.
- 24. Optional: Keep your core business knowledge in use cases, decompose those into your story map.
- 6: Playing them together
- 25. Move between story maps and use cases easily.
- The running example.
- 26. Choice 1: Story map first, check with use cases, continue with the story map or stories.
- 27. Choice 2: Keep the business in the use cases, create a story map to develop.
- 28. Choice 3: Just use cases, micro-incrementally.
- 29. Use cases to user stories to BDD tests.
- Reminder & Summary
- Fin
- About the Author
System requirements
File format: ePUB
Copy protection: Adobe-DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Install the free reader Adobe Digital Editions prior to download (see eBook Help).
- Tablet/smartphone (Android; iOS): Install the free app Adobe Digital Editions or the app PocketBook before downloading (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (not Kindle).
The file format ePub works well for novels and non-fiction books – i.e., „flowing” text without complex layout. On an e-reader or smartphone, line and page breaks automatically adjust to fit the small displays.
This eBook uses Adobe-DRM, a „hard” copy protection. If the necessary requirements are not met, unfortunately you will not be able to open the eBook. You will therefore need to prepare your reading hardware before downloading.
Please note: We strongly recommend that you authorise using your personal Adobe ID after installation of any reading software.
For more information, see our ebook Help page.