Quality Management Process Template Scaled Agile Framework 3.0
This template is used to follow the Scaled Agile Framework (SAFe) methodology. SAFe is characterized by one or more program teams that guide the incremental delivery of value across multiple agile development teams. The highest level of SAFe is the Portfolio level, which is responsible for driving IT investment in a coherent and coordinated way with the business strategy in the value chains. Each SAFe instance is a portfolio of programs that deliver benefits to one or more of these value chains. By providing Quality Management support across the SAFe portfolio, we enable you to easily align value delivery validation using preconfigured elements to create a complete SAFe-enabled test portfolio.
The template includes commonly used SAFe artifacts and provides the workflows for the test artifacts:
The SAFe process template has a top-level testing timeline that consists of multiple Program Increment (PI) iterations. Each PI iteration is in turn divided into multiple sprint iterations.
Project areas based on the SAFe process template include the following templates, which can be used to create test artifacts:
Program Test Plan: Used 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 accumulate team-level quality goals.
Team Test Plan: Used to create team-level test plans and link to team development plans.
Test Case: Used to create test cases for testing at the program or team level and then link to program level features or team level stories.
Test Suite: Used to create test suites to organize tests at the program or team level.
Project areas based on the SAFe process template include the following test artifact categories, which can be used to classify test artifacts in subsequent queries and reporting:
Program: Indicates which program a test plan is aligned with.
SAFe Level: Indicates with which SAFe level a test plan is aligned: Program or Team.
Evidence level: Indicates the level of evidence in scope: Unit, Integration, System or User Acceptance.
Component: Indicates which part of the system is within the scope of the test.
Test type: Indicates the type of test: Functional, Usability, Reliability, Performance, or Support level. It is aligned with the SAFe requirement types.
Test Objective: Indicates the objective of the test suite: Random, Initial, Regression, or Final.
Instrument panel template
Project areas based on the SAFe process template include a getting started dashboard template with the following tabs:
My job: Captures information about the user who is currently logged in.
Portfolio: Captures complete portfolio information, including team members, test plan traceability, and test plan execution status.
Program: Captures information regarding a single program within the portfolio, including test plan traceability, execution status, execution trends, and test coverage.
Equipment: Captures information regarding a single equipment within a program, including test plan traceability, execution status, and execution trends.
Note: Dashboard widgets may need to be configured after one or more test plans have been created.
Project areas 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 information on process templates, see Working with process templates . For guidelines on working in a team using the SAFe process, see Scaled Agile Framework .
6 Agile metrics that matter
Agile project management metrics are one of the most important aspects that transformed the way knowledge teams measure their projects. These represent performance indicators related to results, which allow teams to reflect on what happened in their processes and make data-driven decisions for future actions.
To start our discussion on Agile project metrics, let’s first see how they differ from traditional ones.
Traditional KPIs vs Agile
The main difference between traditional performance metrics and Agile ones is that the former focus on production while the latter focus on results. Many traditional project management KPIs can lead teams to take the wrong actions at all levels of project management.
The quality is measured by the number of documented requirements, instead of collaborating with clients to determine whether they are satisfied with the results.
The productivity and progress are measured by tracking hours only planned vs programming, without taking into account the capabilities real of the team.
The performance is measured by the speed of delivery, even if what is delivered is incorrect.
When it comes to the high volatility of knowledge work, measuring metrics in the traditional way won’t help teams finish projects faster, but rather amplifies the pressure. So with the widespread adoption of Agile project management, new metrics have emerged. Its role is to help you better analyze and understand your workflow, discover failures and improve so that your team can focus on satisfying customers through continuous delivery of value product (project).
6 agile metrics to boost project management
Delivery time and cycle time
Two of the essential Agile project metrics that have their beginnings in the world of Lean management are lead time and cycle time. They both show how long work items take in a given process. However, there is a clear difference between the two.
Delivery time shows you the total time (including lead time) that a work item takes throughout the entire process, from the moment it is requested to the moment it is delivered. To exemplify this Agile metric, let’s say a customer has requested a service or the development of a tool. From the moment you commit to deliver said service / tool, the delivery time begins to accumulate, even when you have not started the job. A simple way of looking at delivery time is as “the customer’s timeline.”