When defining a risk there are many pieces of information you may want or need to enter to capture the essence of the problem and provide the detail necessary for a team member to begin work towards a resolution. The editing options available on this screen depend on your permissions in the project.
Name: This is a quick way to reference the risk, which ideally will provide a brief summary of the potential problem in question.
ID: This is the TeamPulse numeric identifier for the risk. This number is system generated and is not editable.
Tags: Tags allow you to label your risks 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 basic details of the risk in the description field. This is a rich text field that allows for very descriptive formatting to be applied and help to describe the risk. The description area can be enlarged to provide more screen real estate for enhanced entry or viewing.
Blocking: A risk can be marked as Blocking to indicate that it may prevent or is already preventing other work from being completed. A risk marked as blocking will acquire a special icon as well as be highlighted in red throughout the system.
Assessed: A risk can be marked as Assessed to indicate that it is ready to be assigned to team members for working toward resolution. For more information on the process of assessment please view the Risk Assessment documentation.
Assigned To: This is the member of the team actively working on the risk. For more information on assignment workflows please view the Risk Assignment documentation.
Status: Status indicates where your risk is on the way to getting resolved. When you created your project you selected a project template; this template defines the different statuses your risk can have. For example, the default Scrum project template has the following statuses your risk can be in: Open and Closed.
Estimate: Represents the size of the Risk. Some teams may use Story Points to represent size, whereas other teams may represent the size of a risk in hours, days, or weeks estimated to resolve the problem. We have made no assumptions regarding the unit of work for this field.
Priority: This is a value that you can use to help prioritize the Risk in relation to other Risks. Most templates define accepted values of 1, 2, 3, and 4, however these are configurable via the project template advanced settings XML.
Severity: This value can be used to indicate the impact this Risk has on the system, and can also be used to help prioritize the Risk in relation to other Risks. Most templates define accepted values ranging from Low to Critical or Blocking, but these are all configurable via the project template advanced settings XML.
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 risk has been updated. The value displayed here is relative to the user currently viewing the risk. You will not be notified if you are the only person who has changed the risk 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 risk, click the Sync item now button. For more information about TFS synchronization see Synchronization.
Area: Areas can be very helpful for managing risks. You can create an area and assign similar risks to it.
Iteration: The iteration dropdown shows you to what iteration the risk is assigned for resolution.
Resolution: This is a rich text field that can be used to fully describe the actions taken to resolve the Risk.
Tasks: Resolving the risk can be split up into tasks to help you better track the work that need to happen.
Visit Task Management page for more detailed information regarding tasks.
Related Stories: This area can be used to link the Risk to Stories within the TeamPulse system. This can be useful for understanding which Stories are impacted by a specific Risk.
Attachments: Using the attachments tab you can attach files to your risk. After a file is attached it can also be downloaded or streamed to the browser using the grid.
Links: Use the links tab to add links to external content. Clicking the 'open' button in the grid will open the link in a new window.