Overview | Principles| Project | Story | Planning | Retrospective | Reports | SideView | Integration

Story

The story describes the product owner requirement, risk or bug which must be implemented in the project.
In ScrumDesk, every story has:
  • Id, that uniquely identifies the story
  • Subject, short name of the story
  • Description, more requirement details
  • Importance, the level of product owner requirement demand
  • Effort value, relative size of story in story points. Estimated value can be selected only from the best values obviously used in scrum method.
  • Remaining contains number of days necessary to complete the story.
  • Operator, team member responsible for the story implementation
  • State of the story is indicated using color bar in the left top corner. Clicking it you will change story state.
  • Tasks, every story can have multiple tasks or steps needed to be done to complete the story. Every task has its own state (the same meanings as story state) and remaining time required to task’s completion. Tasks can be processed in parallel by more team members. When you use tasks, remaining value of the parent story will be counted from these tasks. In this case, you will not be able to enter story’s remaining value directly.
  • Sprint is an iteration in which stories are included. It represents a time box in which story will be developed.
  • Release gives you information about a date when customer starts use this story in product release version. Release can be shipped after each sprint or it can include stories from more sprints.
  • Tags -  categorize your stories by free text, search and filter them easy using tag clouds

Story in ScrumDesk is displayed as a card. This card is freely resizable. In some cases story can be displayed as a minicard containing only story subject, priority, state and estimated effort.

Story card
Story card
Story mini card
Story minicard

Tasks

Tasks are typically self managed by developers. Every task describes work step. Task is estimated and tracked in days. Developer update just number of remaining workdays. Task has also its state indicated by colored rectangle.

Story tasks

Progress

Story progress is displayed on the card as small burndown chart. Ideal line is showing ideal work progress, real line is calculated from remaining work in a given day.

Story progress tracking

Impediments

During the story development impediments can appear. Impediments can be currently processed or solved. Every impediment is displayed on the burn down charts as a circle indicator with different color - new, processing or solved.

  Impediments on the burn down chart

All impediments are accessible in one place now. Use button in Timeline and Impediments Summary will appears.
Click on colored rectangle to change the status of the impediment.

Start impediments list by click on button I Impediments list is displaying impediment's status, date, which story is related to impediment, subject, author and other impediment's properties

Documents and attachments

ScrumDesk enables to users to attach files to a story. Story can have attached links to a files or files uploaded in the project database. Thumbnail is displayed for the attachment.

Story attachments

Tags

Stories can be tagged by one or more tags separated with ';'. This enables user to categorize stories into more categories. Tags can be entered in the Story detail dialog.

Tags are displayed in SideView panel Search. From this view stories can be easy filter just by click on the tag.

Tags

 

See also:

Project in ScrumDesk TOC Planning product