Previous Topic: Scenario 1—How to Manage New Applications Using Service Desk, CA Clarity PPM, and Harvest (IDEAS)Next Topic: How Other Maintenance Work is Managed


Scenario 2—How to Manage New Applications Using CA Clarity PPM and Harvest

The following scenario ties resource/work management (CA Clarity PPM) with software change management (Harvest). In this scenario, the demand for a new application results in a new CA Clarity PPM project. The CA Clarity PPM project manager associates the project feature tasks with the Harvest project in CA Clarity PPM, which provides the link to the Harvest project in Harvest.

In CA Clarity PPM, the CA Clarity PPM project manager:

  1. Creates a new project representing the demand for a new application.
  2. Notifies the Harvest manager about the new project and communicates the CA Clarity PPM project ID.

In Harvest, the Harvest manager:

  1. Creates a new Harvest project using the Service Desk Clarity Connector lifecycle template, and uses the CA Clarity PPM project ID that was communicated from the CA Clarity PPM project manager.
  2. Communicates the Harvest project name to the CA Clarity PPM project manager.

In CA Clarity PPM, the CA Clarity PPM project manager:

  1. Creates the Harvest Project in CA Clarity PPM, and uses the Harvest project name that was communicated from the Harvest manager as the name of the Harvest project in CA Clarity PPM.
  2. Defines all tasks and WBS, and identifies the summary level tasks as the CA Clarity PPM feature tasks.
  3. Associates the CA Clarity PPM feature tasks to the Harvest project in CA Clarity PPM.
  4. Submits the feature tasks for approval.
  5. Creates the Harvest packages.

In Harvest, the Harvest manager:

  1. Creates additional packages associated to the CA Clarity PPM feature task, if needed.
  2. Reviews and promotes or demotes the packages.

In CA Clarity PPM, the CA Clarity PPM project manager:

  1. Monitors task activity and progress using CA Clarity PPM.
  2. Schedules (or manually executes) the process to send the status of Harvest packages to Service Desk.
  3. Marks the tasks as 100% complete when all of the Harvest packages have been promoted to the production lifecycle state.
  4. Marks the project as complete when all of the project tasks are complete.