Most of us have been trained to write user stories.
As < type of user >, I want < some goal > so that < some reason >.
We write these on whiteboards.
We write these on notecards.
We write these in crazy software that promises to help us work more efficiently.
In the end, they end up being used as a checkbox:
Do the tasks I just completed allow this user to complete their goal?
Yes? Done! Check the box, take down the card.
And this is how Frankenstein’s monster was built.
Piece by piece. Stitched together
You want more for your projects, don’t you?
For that we need to look at User Stories as just a piece of the picture and as a development tool.
Use Cases map out each step of the user’s path.
Documenting this path helps the entire team see how various pieces of the project fit together, point out redundancies or when entire parts of a system are missing, and help catch scope creep.
They help developers work more efficiently.
They also turn themselves into test scripts and user documentation at the end.
It is almost too good to be true.
In this session we’ll run through a few ways to document Use Cases to get the most out of them.
As the Presenter, I want to share my love for User Stories and Use Cases with Project Manager and Leads, so that they can go back after DrupalCamp and help their teams prevent Monster Projects.