Storyotypes

Get To Done

We use Storyotypes to capture re-useful information common to many Stories. Storyotypes are used to capture common Standards of Care.

Storyotypes are used as a checklist for repeatable work. For example, we know that at the end of every Sprint we are going to have a Team Retrospective. Though each Retrospective may have a different activity or focus, the overall steps are always going to be the same.

We can create a checklist for us to follow for the Retrospective:

    1. Team Facilitator (Scrum Master) helps the team warm up via reflective dialog or an activity.
    2. Team Facilitator recalls the last Kaizen the team agreed to.
    3. Each person uses silent writing to answer 3 classic questions. 1) What went well? 2) What could be better? 3) What could we agree to improve?
    4. Each team member participates by sharing what they wrote in his/her own voice.
    5. The team discusses the proposed improvements, chooses one, and then commits to a Kaizen (team agreement to improve) for the next sprint.

The above steps will be our go to checklist for the Retrospective. Instead of needing to remember these 5 steps every Sprint, we can take this checklist and create a Stroyotype. Using a checklist for repeatable work will ensure no step is missed when getting the Story to Done.

In the video, we will show you how to create a new Storyotype and how to edit and assign existing Storyotypes.

Share this Post