Activities

Activities complete a Task.

Team leads review Tasks and determine what Activities are needed to complete them. Often a single Task requires the work of multiple users. An Activity is created and assigned to a single team member to complete a discrete unit of work. An Activity:
  • Is owned by an individual contributor on the project team.
  • Represents a single unit of work.
  • Refers back to the Task which it helps to complete.
  • Can be enabled for UCM.

The Submitted state is the starting point for an Activity. Activity records are moved to the Activated state when work is being done. When the solution is complete, the record is moved to a Completed state.

Activity records are assigned to a person that is a member of one of the roles for that activity type. The owner reviews the Activity records assigned to them, and then completes work on the activities. Typical types of Activity records are:
  • Assess Results
  • Build
  • Create
  • Test Case
  • Define Requirements
  • Define Vision
  • Design Implementation
  • Design Solution
  • Detail Requirement
  • General Implement
  • Implement Developer Test
  • Implement Test Script
  • Manage Iteration
  • Outline Architecture
  • Outline Requirements
  • Plan Project
  • Plan Iteration
  • Refine Architecture
  • Review
  • Run Developer Test
  • Run Tests
  • Test

Developers work on Opened state activities that are assigned to them. Review or assessment activities are for reviewing or assessing information in a developer Activity for an indication of whether other work, such as documentation, is needed. If additional work is needed the reviewer or assessor creates development activities to resolve the need.

Test activities are for Testers to test and qualify Developer activities. A Test Activity contains all testing information and results.