A progression is a defined set of one or more Phases through which package revisions or features move in order to be delivered to end users. Each package revision or a feature contains one or more workitems (stories or defects) with associated changes (commits).
When a progression is created, Continuum offers two different perspectives of looking at the progression: the Package Progression and Feature Progression.
In addition to presenting the Package Revision perspective of workitems, for every workitem that's being tracked, Continuum collects the feature data (the parent of workitems) from tools like Jira and VersionOne Lifecycle and presents the same in the progression board from a features perspective.
Once phases are defined for a progression, Package Revisions may be promoted through the phases. Each package can have a discrete set of Activities and Controls defined which will be executed as the package revisions arrive at that particular phase.
Creating a Progression
- Click the Administration icon ( ) at the top right and select Workflow > Progressions from the menu.
- Click Add New.
- Provide a name and description for your progression and then click Create.
Provide a relevant name for your progression so it can be easily identified at a later time. If different categories of software (ie products or micro-services) go through a different process in order to be delivered, create different progressions for each.
Defining Progression Phases
Once the Progression has been created, its phases may be defined. Each phase represents a discrete step in the software delivery process through which value (work items) is moved as software gets closer to delivery for end users.
- Click Add Phase.
- Enter a "Phase" name and "Description" then click Add.
- Repeat step 2 and create as many phases as you want in your Progression.
- Click Done once all the phases have been defined.
Defining the "Code Complete" Phase
Given all phases in a progression have been defined, one of the phases must be designated as the "code complete" phase; this is defined as the phase where work arrives in its final state and no further changes will be made to the contents (workitems) of the relevant package revision. When work arrives at this phase, it is considered ready to be delivered to the end-user.
This threshold is defined so that Continuum can track the time it takes for a workitem to become "code-complete" and provide code commit reporting around risk and quality.
To define the code-complete phase, tick the radio button to the left of the phase name. In the below example, the "Ready for Delivery" phase is defined as the code-complete phase for the "Authentication Service" progression.
In the above example, code commits that appear on or after this phase should be considered out of the process and thus high-risk. This is further detailed in the Progression Metrics section.
Once Progression and Phases have been defined, you can start moving package revisions through it by using the Flow plugin "Package - Promote Revision".