Step 6. Backlog Stories RSS Reader

In this step product owner and development team are going to plan project sprints.

Who


Product Owner
       

Creating stories

Target for this step is to create backlog stories.

Product Development
 
Product Backlog
 

Stories in scrum are mainly created by product owner. As a first step let's log in as product owner.

Product owner is responsible for requirements specification and prioritization.

Choose your project and switch to Product Backlog. Product backlog is a container where anyone can see all stories displayed as story cards.

ScrumDesk is primary a virtual board. User experience very near to a wall with story cards.

Creating new stories

Stories can be created on board in different ways:

  • by click on New menu item

  • by Insert key on your keyboard

  • by double-click on board

  • using a template from Templates pane displayed by click on arrow below the New menu item

Story

Story in scrum and ScrumDesk is described by a story card containing following attributes:

  • Id, (number 5605),  that uniquely identifies story
  • Subject, short name of story
  • Description, more requirements details
  • Priority, (number 50), the level of product owner requirement demand
  • Effort value, relative size of story in story points. Estimated value can be selected only from predefined list of values obviously used in scrum method.
  • Duration is number of days necessaries to finish the story.
  • Operator, team member responsible for story implementation
  • State of story is indicated using color bar in left top corner. Clicking the bar you will change the story state. For more details about state look at Story states.
  • Theme, name of the theme which group stories

Story card

Step - creating stories

Let's create new story  Adding a channel.

  1. Double click board

  2. New card is created

  3. Enter the subject: Adding a channel

  4. Enter the description:

    As a user I want to add new channel
    - by entering channel URL
    - using a drag and drop from web browser

  5. Enter the importance: 90 This will be highest priority story. Priority number and range is depending on Product owner decision. Development team must understand this values range.
    ScrumDesk uses number priority as it gives Product Owner better granularity.

  6. As a theme enter User Interface or UI.

  7. As you are logged as a product owner, you are not able to change Effort nor Duration properties.

Your card should look like this:

 

Now you can enter other remaining stories. You will enter stories  in a Grid view. Click Grid menu item .

Story Categorization

Don't forget to set Theme and/or color of the card. This way you can categorize stories into more categories.

Tags

You can use story tags available in a story detail window. Stories can be filtered by tags from the SideView.

Tags cloud

Step 5 Planning project sprints TOC