Scaled Agile Framework 4.0 Quality Management process template

Use this template to follow the Scaled Agile Framework® (SAFe®) methodology. SAFe defines the roles, activities, artifacts, and work flow and provides best practices and guidance to help enterprises embrace lean and agile principles from the business level, what SAFe calls the Portfolio level, into Value Streams that orchestrate the delivery of software and products across Programs of agile Teams.

The Portfolio is responsible for driving investment in software and product development aligned with business strategy across Value Streams. Each instance of SAFe is a Portfolio of Value Streams realized by Programs that orchestrate the delivery of capabilities across multiple, self-governing agile Teams. By providing Quality Management support in the SAFe Portfolio process template, we enable you to easily align the validation of value delivery via preconfigured elements to create a SAFe-enabled full testing Portfolio. The process template provides a new project area with the process configuration, iteration structure, and test artifact templates.

You can use the Test Administrator role to assign permission to configure the Quality Management project area on behalf of the team.

The template includes commonly used SAFe artifacts and provides the workflows for test artifacts:

  • Iterations

    The SAFe process template has one top-level Testing timeline, which consists of multiple Program Increment (PI) iterations. Each PI iteration is further divided into multiple sprint iterations.

  • Artifact templates
    Project areas that are based on the SAFe process template include the following templates that you can use to create test artifacts:
    • Value Stream Test Plan: Use to create value stream-level test plans and link to value stream development plans.
    • Program Test Plan: Use to create program-level test plans and link to program development plans. Use the Child Test Plans section to link to team-level test plans and roll up team-level quality objectives.
    • Team Test Plan: Use to create team-level test plans and link to team development plans.
    • Test Case: Use to create test cases for either program-level or team-level tests, and then link to program-level features or team-level stories.
    • Test Suite: Use to create test suites to organize program-level or team-level tests.
  • Artifact categories

    Project areas that are based on the SAFe process template include the following test artifact categories that you can use to classify test artifacts for further querying and reporting:

    Test Plan:
    • Program: Indicates which program a test plan is aligned with.
    • SAFe Level: Indicates which level of SAFe a test plan is aligned with: Value Stream, Program or Team.
    • Test Level: Indicates which level of testing is in scope: Unit, Integration, System, or User Acceptance.
    Test Case:
    • Component: Indicates which part of the system is in the scope of testing.
    • Test Type: Indicates which kind of test: Functional, Usability, Reliability, Performance, or Supportability. Aligned with SAFe requirement types.
    Test Suite:
    • Test Objective: Indicates the goal of the test suite: Smoke, Initial, Regression, or Final.
  • Dashboard template
    Project areas that are based on the SAFe process template include a starter dashboard template with the following tabs:
    • My Work: Captures information about the currently logged-in user.
    • Portfolio: Captures information for the entire portfolio, including team members, test plan traceability, and test plan execution status.
    • Value Stream: Captures information for a single value stream within the portfolio, including test plan traceability, execution status, execution trends, and test coverage.
    • Program: Captures information for a single program within the portfolio, including test plan traceability, execution status, execution trends, and test coverage.
    • Team: Captures information for a single team within a program, including test plan traceability, execution status, and execution trends.
      Note: Dashboard widgets might need to be configured after one or more test plans are created.
  • Related sites

    Project areas that are based on the SAFe process template include links to SAFe and Quality Management content in the Related Sites section of the right sidebar.

For more details on process templates, see Working with process templates. For guidance on working in a team that uses the SAFe process, see Scaled Agile Framework.


video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki