User Stories Applied Template

—

"User Stories Applied: For Agile Software Development" is written by two of the heavy hitters from the agile movement Kent Bent one of the original signatories of the Agile Manifesto in 2001 who has since driven the development and popularisation of Extreme Programming (XP) which still maintains a presence in many of our pogo to software engineering frameworks. Then the primary author is Mike Cohn who we have already reviewed in this series with "Succeeding with Agile: Software Development Using Scrum". This Miro is structured going through the 4 sections of the book. You can expect to learn and cover:

What are user stories and how are they used 🚀📚🤔
Writing User Stories ✍️📝
Gathering Stories 🤝📊
Guide for Good Stories 📖✨
Estimating and Planning 📆📈
What stories are not 🚫📜
Why user stories? ❓🤔
A catalogue of story smells 📋👃

Remember, user stories are not rigid contracts but rather dynamic instruments for ongoing conversations between customers and developers. So Why do we advocate for users stories over requirements documents or use cases?

Emphasis on verbal communication rather than written.
User stories are comprehensible by all audiences
User stories are the right size for planning
User stories work for iterative development

This concludes with an interactive workshop idea showing how user stories can be applied to different ticket types, creating an agreed format within an organization.

Matthew Binder

Technical Delivery Manager@Boohoo Group

I'm an experienced Technical Delivery Manager / Senior IT Project Manager / Scrum Master. I live and breathe IT delivery I'd say it's one of my passions in life. My experience is in Retail and eCommerce across Morrisons, Asda/Walmart and Boohoo Group working on digitally focused customer and stakeholder-facing web, app and microservices /event-driven architectures.