Story Properties

To help you better define, organize, and prioritize your user stories, you can use the many attributes that TeamPulse provides.  The editing options available on this screen depend on your permissions in the project.

 

enlarge screenshot

 

 

Tags: Tags allow you to label your stories with common terms. Tags are unique to a project and are shared among all the stories, bugs, risks, and issues. Creating a tag is as easy as typing a name and hitting enter. Existing tags can be selected using the drop down or by typing and using the auto-complete ability. Tags can be removed by clicking the small 'x' beside the tag name. If a removed tag is not referenced by any other item within the project, the tag will also be removed from the list of available tags.  

 

Description: You can enter the details of your story in the description field. A powerful feature of story description is Quick Linking. Quick Linking allows you to quickly add a reference to a Story or Persona within your story description text.  If the Story or Persona does not exist, Quick Linking will create a stub for you automatically.  Quick Linking really helps to make it easy to have full traceability between your requirements.

 

Area: Areas can be very helpful for managing stories. You can create an area and assign similar stories to it. This ability to group stories is very useful when planning and scheduling your stories.

You can assign, or reassign a story by selecting the respective area from the drop down menu.

 


Iteration: The iteration assignment shows you to what iteration the story is added. If the story is not assigned, or you want to reassign it, you can do so by using this option.

 

Assigned To: This is the member of the team responsible for the story.


StatusStatus is where your story is on the way to getting done. When you created your project you selected a project template, this template defines the different statuses your story can have. For example, the default TeamPulse project template has the following states your story can be in: Not Done, Deferred, Deleted, In Progress, Ready for Test, and Done.

 


Estimate:  Represents the size of the User Story.  Some teams may use Story Points to represent size.  Other teams may represent the size of a story in the number of days or weeks estimated to implement.  We have made no assumptions regarding the unit of work for this field.

 

Priority:  This is a numeric indicator that you can use to help prioritize the Story in relation to other Stories

 

Priority Classification:  This attribute is a much broader way of defining priority using MoSCoW

  • (M)ust Have
  • (S)hould Have
  • (C)ould Have
  • (W)on’t Have

 

Value Classification:  This attribute helps to identify the type of value the feature provides to your organization.  We’ve started you off with a few values that we use:

  • Differentiator:  A unique feature
  • Spoiler:  A feature that your competitors have, but your software implements better
  • Cost Saver: Work we must do to reduce the cost of development, support, maintenance, or to increase profit or margins
  • Table Stakes:  A feature you must implement in order to ship

 

Complexity:  A relative attribute that allows you to express how complex you believe the story is.  Very complex stories may be flagged for greater design work compared to very simple stories.

 

Maturity:  Maturity represents how mature the story is with regards to its specification.  If you have only just captured the story title and cannot quite define the story description, the story is not mature at all.  You can use this flag during planning, as you will likely not want to start development on stories that are not mature.

 

Certainty:  Certainty is an attribute that allows you to express how certain you are that the story is accurate.  Some stories may be fully written, however, you can use this certainty flag to indicate that you require additional validation before proceeding.

 

Notify me when others change this item:  If the notification system has been enabled and correctly configured, this check box will allow individual users to request email notifications when this story has been updated. The value displayed here is relative to the user currently viewing the story. You will not be notified if you are the only person who has changed the story even if you have asked to be notified.

 

Sync with TFS:  If the project has been connected to a TFS project, this check box will mark this item as included in or excluded from the synchronization process.  To immediately sync this story, click the Sync item now button.  For more information about TFS synchronization see Synchronization.