πŸŽ“ So you're a story owner?

Congratulations! You have secured a special right to the majority of the πŸŽ‰ and πŸŽ‚! And with all great power comes great responsibility πŸ•·οΈ!

You are now responsible for pushing the story aaaaaaaaall the way to Shipped. Whatever it takes - getting help, advocating changes to the story definition, nagging people, taking magic leaps of faith and relying on your own innate ability as a human being to solve the problem the best you can. ❀️πŸ’ͺπŸ§ πŸ’‘

To help you in this process, we have a checklist with the most important things to consider when owning a story, here below.

Good luck and remember you're an exceptional part of an amazing team. You've got this. And you're never alone.

πŸŽ—οΈRequirements for each user story

Willa's Definition of Done helps us keep a consistent quality of our deliveries and reduces the risk of leaving things incomplete.

The following requirements should be verified by at least one other team member:


βœ… Production quality!

All "Production Quality" requirements are met before you demo the story πŸ‘‡

βœ… Tested!

The entire story has been tested in (an environment that is equivalent to) the production environment before you demo the story.

βœ… Merged!

The entire story has been merged to master after peer reviews and passing the build pipeline.

βœ… Demo'd (It's getting exciting!)

The story has been demonstrated according to our Demo guidelines πŸ‘‡

βœ… Confirmable (totally a word)

It is possible to confirm if and how the story works through the app, webpage and/or system logs.


βœ… Production Quality!

For something to be considered to have Production Quality, it must be sufficiently ...

πŸ” robust (resilient, available, scalable)