Lifecycle project templates

Edit online

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.

Note: SAFe 6.0 templates for IBM Engineering Lifecycle Management (ELM) are available on Jazz.net. You can download the templates from SAFe 6.0 templates for IBM Engineering Lifecycle Management. The available predefined process templates are Full SAFe 6.0 and Essential SAFe 6.0. You can use them to configure tooling environment for SAFe Portfolio, Large Solution, Portfolio, or Essential SAFe 6.0 configuration in ELM. For more information, see Say Hello to SAFe 6.0!.

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) 5.0 Essential, SAFe 5.0 Full, Scrum, or Formal Project Management process template. The quality management project area can be configured to use the SAFe 5.0 Essential, SAFe 5.0 Full, or default process template. The requirements management project area can be configured to use the SAFe 5.0 Essential, SAFe 5.0 Full, Base, 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, Architect

This template sets up associated project areas for quality management, requirements management, and change and configuration management. The change and configuration management project area is configured to support architecture management. The testers (in quality management), analysts (in requirements management), and architects (in change and configuration 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) 5.0 Essential, SAFe 5.0 Full, Scrum, or Formal Project Management process template. The quality management project area can be configured to use the SAFe 5.0 Essential, SAFe 5.0 Full, or default process template. The requirements management project area can be configured to use the SAFe 5.0 Essential, SAFe 5.0 Full, Base, Use Case, Agile Requirements, or Traditional Requirements project template.

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) 5.0 Essential, SAFe 5.0 Full, Scrum, or Formal Project Management process template. The quality management project area can be configured to use the SAFe 5.0 Essential, SAFe 5.0 Full, 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 SAFe 5.0 Essential, SAFe 5.0 Full, or default process template. The requirements management project area can be configured to use the SAFe 5.0 Essential, SAFe 5.0 Full, Base, 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) 5.0 Essential, SAFe 5.0 Full, Scrum, or Formal Project Management process template. The requirements management project area can be configured to use the SAFe 5.0 Essential, SAFe 5.0 Full, Base, 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 5.0 Essential, SAFe 5.0 Full, Base, 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 requirements management project area can be configured to use the SAFe 5.0 Essential, SAFe 5.0 Full, Base, 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 SAFe 5.0 Essential, SAFe 5.0 Full, 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) 5.0 Essential, SAFe 5.0 Full, Scrum, or Formal Project Management process template.

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) 5.0 Essential, SAFe 5.0 Full, Scrum, or Formal Project Management process template. The quality management project area can be configured to use the SAFe 5.0 Essential, SAFe 5.0 Full, or default process template. The requirements management project area can be configured to use the SAFe 5.0 Essential, SAFe 5.0 Full, Base, 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 change and configuration management and requirements management. The change and configuration management project area is configured to support architecture management. The architects (in change and configuration management) work integrated with analysts (in requirements management). Artifacts in the change and configuration management project area elaborate requirements in the requirements project area. The requirements management project area can be configured to use the SAFe 5.0 Essential, SAFe 5.0 Full, Base, Use Case, Agile Requirements, or Traditional Requirements project template. The change and configuration management project area can be configured to use the Scaled Agile Framework (SAFe) 5.0 Essential, SAFe 5.0 Full, Scrum, or Formal Project Management process template.

Architect, Developer

This template sets up a change and configuration management project area that is configured to support architecture management. The architects work integrated with development in the same project area. Architecture change requests are tracked in the project area. The change and configuration management project area can be configured to use the Scaled Agile Framework (SAFe) 5.0 Essential, SAFe 5.0 Full, Scrum, or Formal Project Management process template.

Architect, Developer, Product Engineer

This template sets up project areas for change and configuration management and product line engineering. The change and configuration management project area is configured to support architecture management. The change and configuration management project area can be configured to use the Scaled Agile Framework (SAFe) 5.0 Essential, SAFe 5.0 Full, Scrum, or Formal Project Management process template. The product line engineering project area uses the Product Management Default Process proecess template.

Architect, Product Engineer

This template sets up associated project areas for change and configuration management and product line engineering. The change and configuration management project area is configured to support architecture management.

Architect

This template sets up a project area for architecture management.

Product Engineer

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