Story Cards


Story cards are the heart of agile development. They are used to collect and organize all of the information needed to complete a story. StarTeam Agile story cards have several features to make it easier to track the progress of a story as well as retain the history of the story for retrospectives. 

StarTeam Agile story card have four tabs:

  • Story- This tab contains the basic story information:
    • Story Title - In Agile Scrum, this usually takes the format of "As a ____ I want to be able to ______ so I can ________." This is the name that will appear for the story in the backlog and on the Teamboard views of the story cards so it needs to make sense to the team that will be using the cards.
    • Type - The options are User Story, Technical To Do and Defect
    • Sponsor - The person who is sponsoring the story. This can be the product manager or a team member who created the story. Typically it is the person that the developers will go to with questions about what needs to be done to complete the story.
    • Points - When a story is created, an estimate of story points can be entered. The points assigned to the story are usually finalized during the sprint planning meeting. 
    • Description - This is where any information that would be useful for completing the task can be entered, including links to documents or web sites. 
    • Risk Value - This is a graphic to indicate the risk/value of the story. This can be changed by clicking in the appropriate box.
    • Tags - Tags are added to stories in the Backlog view. They are displayed for reference on the card. 

  • Tasks - Stories are broken down into tasks using task cards. The task cards are created from this tab and a list of all tasks associated with the story can found on this tab. See Adding Tasks to a Story for information on how to add tasks. 
  • Impact- The following items can impact a story and can be viewed or accessed from this tab:
      • Stories - All of the stories that impact the selected story will be listed in this section. If the story is a child, the parent story and the other children will be listed. If the story is a parent, then only the children will be listed. The same symbols that are used to indicate story type on the Backlog view are used here.
      • Code in StarTeam - This is a list of all code checked in to StarTeam that is linked to the story.
      • Code in Subversion - This is a list of code checked into Subversion that uses the SVN protocol. Currently, only SVN protocol is supported by StarTeam and StarTeam Agile. Code that doesn't use this protocol will be listed under Other.
      • Defects - This is a list of items entered as Change Requests in StarTeam. This list does not include stories that are categorized as Defects within StarTeam Agile. Defect Stories added via StarTeam Agile will be listed in the Stories section.
      • Other- This is a list of anything else that relates to the story including code checked into Subversion that doesn't use the SVN protocol and links to documents or websites included in the story requirements section

  • Mentions - Mentions includes any discussions that may have been created referencing the story. This tab is only visible after a story is added to a sprint. 
  • History - This tab is a history of all the changes made to the story over time. You can compare versions of the story as well as see who modified the story.

Comment List