Project Name
Begin by typing in the name of your project, then press Enter.
Sprints
Sprints are groups of user Stories that fit together well enough to be demonstrated and used. Sprints are defined by timeboxing, and also by what is practical to deliver and use.
Identify Sprint groupings from your stories and add them here.
Sprint
Stories
Story
Type in a user story, in the following format:
'As a [A], I need to [B], so that I can [C]'
where:
[A] is a user role,
[B] is what the user needs to do, and
[C] is why they need to do it.
Feature, function or task
- What features, functions or tasks will be needed to deliver this story in a working form?
- What components must be working?
- What needs to be researched and designed?
Complexity (points)
Estimate the relative complexity of this story, expressed as story points. Trivial things are only a point or two, and the average is about 5 points.
If you find it hard to guess, you may need to break it down further into smaller stories.
1 story point (easy)2 story points3 story points5 story points (average)8 story points13 story points (hard)More than 13 story points
Users
Next, make a list of Users. These are the people who will interact with the solution that you are creating.
Users are identified not by personal name, but by their role in relation to the task they perform.
Add a User role and press Enter.
User
Epics
Epics are the major stages in a project and are divided up into sprints.
An epic is often a product release point or a handover to the customer.
Add an Epic of your project.
If you have a target date in mind, include it in the topic text for clarity.
Epic
Overview
Write down a summary of your project's key points, to act as a reference for discussions.
Add a key point about your project.
Key point
