Lifecycle project templates

The Lifecycle Project Administration user interface includes predefined templates that you can use to create a lifecycle project and the project areas that belong to that lifecycle project. The predefined templates define which application project areas to create and which associations are established between those project areas.

The Lifecycle Project Administration user interface includes the following predefined lifecycle project templates.

Quality Professional, Analyst, Developer

This template sets up associated project areas for quality management, requirements management, and change and configuration management. The testers (in quality management) and analysts (in requirements management) work with developers (in change and configuration management). Quality management tasks and requirements change requests are tracked in the change and configuration management project area. The change and configuration management project area can be configured to use the Scaled Agile Framework (SAFe) 4.0 Program, SAFe 4.0 Portfolio, Scrum, or Formal Project Management process template. The quality management project area can be configured to use the Quality Management for SAFe or default process template. The requirements management project area can be configured to use the SAFe 4.0 Portfolio Component, Requirements Template for Testers, Use Case, Agile Requirements, or Traditional Requirements project template.

This image shows three project areas within the lifecycle project. The CCM project area stores quality management tasks and defects for QM project area testers. The CCM project area stores implementation requests and requirements change requests for RM project area analysts. The RM project area stores requirements for QM project area testers.

Quality Professional, Analyst, Developer – with Design Management

This template sets up associated project areas for quality management, requirements management, change and configuration management, and design management. The testers (in quality management), analysts (in requirements management), and architects (in design management) work integrated with development (in change and configuration management). Quality management tasks, requirements change requests, and architecture change requests are tracked in the change and configuration management project area. The change and configuration management project area can be configured to use the Scaled Agile Framework (SAFe) 4.0 Program, SAFe 4.0 Portfolio, Scrum, or Formal Project Management process template. The quality management project area can be configured to use the Quality Management for SAFe or default process template. The requirements management project area can be configured to use the SAFe 4.0 Portfolio Component, Requirements Template for Testers, Use Case, Agile Requirements, or Traditional Requirements project template. The design management project area can be configured to use the Basic or Blank template.

This image shows four project areas in the lifecycle project. The CCM project area stores Quality Management tasks, defects, and change requests for QM users; implementation requests and Requirements change requests for RM users; and change requests for DM users. The QM project area stores Quality Management artifacts for DM users. The RM project area stores requirements for QM users and DM users.

Product Engineer, Developer

This template sets up associated project areas for change and configuration management and product line engineering.

Quality Professional, Developer – without Requirements

This template sets up associated project areas for change and configuration management and quality management. The testers (in quality management) work with developers (in change and configuration management). Quality management tasks are tracked in the change and configuration management project area. The change and configuration management project area can be configured to use the Scaled Agile Framework (SAFe) 4.0 Program, SAFe 4.0 Portfolio, Scrum, or Formal Project Management process template. The quality management project area can be configured to use the Quality Management for SAFe or default process template. Capabilities for requirements are not set up, assuming that other tools and integrations will be used for this capability.

This image shows two project areas in the lifecycle project. The CCM project area stores quality management tasks and defects for QM project area testers.

Quality Professional, Analyst

This template sets up associated project areas for quality management and requirements management. Quality management tasks and requirements change requests are tracked in a separate change and configuration management project area. The quality management project area can be configured to use the Quality Management for SAFe or default process template. The requirements management project area can be configured to use the SAFe 4.0 Portfolio Component, Requirements Template for Testers, Use Case, Agile Requirements, or Traditional Requirements project template. Capabilities for Defects are not set up, assuming that other tools and integrations will be used for this capability.

This image shows three project areas in the lifecycle project. The CCM project area stores quality management tasks for QM project area testers, and requirements change requests for RM project area analysts. The RM project area stores requirements for QM project area testers.

Analyst, Developer

This template sets up associated project areas for requirements management and change and configuration management. The analysts (in requirements management) work with developers (in change and configuration management). Requirements change requests are tracked in the change and configuration management project area. The change and configuration management project area can be configured to use the Scaled Agile Framework (SAFe) 4.0 Program, SAFe 4.0 Portfolio, Scrum, or Formal Project Management process template. The requirements management project area can be configured to use the SAFe 4.0 Portfolio Component, Requirements Template for Testers, Use Case, Agile Requirements, or Traditional Requirements project template.

This image shows two project areas in the lifecycle project. The CCM project area stores requirements change requests and implementation change requests for RM project area analysts.

Analyst

This template sets up a project area for requirements management. Requirements change requests are tracked in a separate change and configuration management project area. The requirements management project area can be configured to use the SAFe 4.0 Portfolio Component, Requirements Template for Testers, Use Case, Agile Requirements, or Traditional Requirements project template.

This image shows two project areas in the lifecycle project. The CCM project area stores requirements change requests for RM project area analysts.

Analyst – without Requirements Change Requests

This template sets up a project area for requirements management. The project area can be configured to use the SAFe 4.0 Portfolio Component, Requirements Template for Testers, Use Case, Agile Requirements, or Traditional Requirements project template.

Quality Professional – without Defects and Requirements

This template sets up a project area for quality management. Quality management tasks are tracked in a separate change and configuration management project area. The quality management project area can be configured to use the Quality Management for SAFe or default process template. Capabilities for defects and requirements are not set up, assuming that other tools and integrations will be used for these capabilities.

This image shows two project areas in the lifecycle project. The CCM project area stores quality management tasks for QM project area testers.

Developer

This template sets up a project area for change and configuration management. The change and configuration management project area can be configured to use the Scaled Agile Framework (SAFe) 4.0 Program, SAFe 4.0 Portfolio, Scrum, or Formal Project Management process template.

This image shows one CCM project area.

Quality Professional, Analyst, Developer – with separate Quality Management Tasks and Requirements Change Requests

This template sets up project areas for quality management, requirements management, and change and configuration management. The testers (in quality management) and analysts (in requirements management) work independently from the developers (in change and configuration management). Quality management tasks and requirements change requests are tracked in separate change and configuration management project areas. The change and configuration management project area can be configured to use the Scaled Agile Framework (SAFe) 4.0 Program, SAFe 4.0 Portfolio, Scrum, or Formal Project Management process template. The quality management project area can be configured to use the Quality Management for SAFe or default process template. The requirements management project area can be configured to use the SAFe 4.0 Portfolio Component, Requirements Template for Testers, Use Case, Agile Requirements, or Traditional Requirements project template.

This image shows three CCM project areas, a QM project area, and an RM project area. One CCM project area stores quality management tasks for QM project area testers. The second CCM project area stores requirements change requests for RM project area analysts. The third CCM project area stores defects for QM project area testers, and implementation requests for RM project area analysts. The RM project area stores requirements for QM project area testers.

Architect, Analyst

This template sets up associated project areas for design management and requirements management. The architects (in design management) work integrated with analysts (in requirements management). Artifacts in the design management project elaborate requirements in the requirements project. The requirements management project area can be configured to use the SAFe 4.0 Portfolio Component, Requirements Template for Testers, Use Case, Agile Requirements, or Traditional Requirements project template. The design management project area can be configured to use the Basic or Blank template.

This image shows two project areas in the lifecycle project. The RM project area stores requirements for DM users.

Architect, Developer

This template sets up associated project areas for design management and change and configuration management. The architects (in design management) work integrated with development (in change and configuration management). Architecture change requests are tracked in the change and configuration management project area. The change and configuration management project area can be configured to use the Scaled Agile Framework (SAFe) 4.0 Program, SAFe 4.0 Portfolio, Scrum, or Formal Project Management process template. The design management project area can be configured to use the Basic or Blank template.

This image shows two project areas. The CCM project area stores change requests for DM users.

Architect, Developer, Product Engineer

This template sets up associated project areas for design management, change and configuration management, and product line engineering.

Architect, Product Engineer

This template sets up associated project areas for design management and product line engineering.

Architect

This template sets up a project area for design management. The design management project area can be configured to use the Basic or Blank template.

Product Engineer

This template sets up a project area for product line engineering.

video icon Watch videos

CLM playlist
Jazz.net channel
User Education channel

learn icon Learn more

CLM learning circle
Agile learning circle
Learning circles

ask icon Ask questions

Jazz.net forum
developerWorks forums

support icon Get support

Support Portal
Deployment wiki
Support blog