Task: Perform retrospective |
...
Disciplines: example_discipline.assign
Purpose
[ Mandatory: The Purpose field describes the reason for the method element. For example, for a Task: Why is the task being performed? When a task is defined to get a work product to a particular state, identifying the purpose of the work product state may help to clarify why the task has been broken down as it has. What is the goal of the task? ]
Relationships
Roles | Primary Performer: -role_responsible_for_work_product-.assign_wp | Additional Performers:
Outputs | [ Example Practice Artifact ]
Main Description
[ Optional (main description or task steps must be provided): For tasks, if individual steps are not being used, this should explain the execution of the task. Mention the input and output work products. ]
Steps
[Example Step]
[Steps can be specified to provide a more detailed set of instructions for the practitioner on to how to complete the task. Tasks can be defined: By providing a Main Description only, with no Steps By providing only Steps, and no Main Description By providing a summary or overview of the steps in the Main Description, along with specific Steps. A Step is described using: Name: This is the brief description of the step. Description: This optional field provides more detail for the specific step. ]
Key Considerations
[ Optional: This field contains useful material that does not easily fit into any of the other sections, such as advice and guidance of a critical nature. as well as warnings, cautions, pitfalls and dangers. ]
Alternatives
[ Not used: This field is no longer recommended. ]
More Information
Concepts | [ Example Practice Concept ]
Guidelines | [ Example Practice Guideline ]
Tool Mentors | [ Example Practice Toolmentor ]
© Copyright IBM Corp. 1987, 2009. All Rights Reserved.