Define a story in SAFe
Create high-level definitions of your requirements in the form of stories in SAFe.
Before you begin
Role required: safe_sprint_planner, safe_art_user, safe_scrum_master, safe_story_editor, safe_team_member, or safe_admin
Procedure
- Create a story using either of the following options.
| Option | Steps |
|---|---|
| From the Story module |
|
| From the SAFe stories related list |
|
- In the form, fill in the fields:
| Field | Description |
|---|---|
| Number | System-generated number for the story. |
| Feature | Feature to which the story belongs. |
| SAFe epic | Epic to which the story belongs. |
| SAFe sprint | Sprint in which the story is scheduled for completion. |
| Points | Number of points indicating the estimated effort required to complete the story. A larger point value indicates that a greater amount of effort is required. |
| State | State of the story. Select one of the following:- Draft: In this state, the story requirements, such as the description and acceptance criteria, are still being drafted. - Ready: In this state, the story is marked as ready to be picked up by the development team. - Work in Progress: In this state, the development team works on the story and records their changes in the work notes field. - Ready for Testing: In this state, the story is marked as ready to be taken up by a tester. - Testing: In this state, the tester works on testing the story based on the requirements provided in the story. - Complete: In this state, the development and testing efforts on a story are complete. - Cancelled: In this state, a story has been cancelled. The default state for a new story is Draft. |
| SAFe team | Team to which the story is assigned. |
| Assigned to | User to which the story is assigned. |
| Enabler | Check box identifying the story as an enabler. Enablers do not add direct business value but help lay a foundation for future work. |
| Short description | Brief description of the story. |
| Description | A more detailed description of the story. |
| Acceptance criteria | The functional criteria or testing results required to move the story to the state of Complete. |
| Work notes | Work notes indicating the progress of the story at various stages in its life cycle. |
- Click Submit.
What to do next
- Use the related links and lists of the story to create tasks for this story, or add dependencies of the current story to other stories. You can also convert this story into a SAFe feature or split this story into two, based on your requirements. For more information, see Related links and lists for a SAFe story.
- You can create a story with the same details as this story using the Insert or Insert and Stay options from the story additional actions (
Image omitted: additional-options.png
Additional options\).
Additional options\).
When you use **Insert and Stay**, the form of the newly created story remains open so that you can modify its details, create more stories with these details, or do both.
On SAFe Board, the new story is positioned right below the original story and the global rank of the new story is set accordingly.
**Note:**
- Set the glide.ui.task.insert and glide.ui.advance properties to **true** to access these actions.
- These actions are not allowed on stories added from the triage board.
- Related links and lists for a SAFe story
Use the related links and related lists in your SAFe story form based on the actions that you need to perform on your story. - Add dependencies to your SAFe stories
Set dependencies to your SAFe story by adding prerequisite and dependent stories to it. Using the SAFe Planning board, you can distinguish these dependencies between stories during your big room planning and replan the stories as required.
Parent Topic:SAFe entities