LACE (CCSQ Lean Agile Center of Excellence)

Page tree

Team Backlog


Organizing your work into a digestible, transparent artifact is not difficult. The Team Backlog 1 is the primary repository for managing work items. Specifically, User Stories 2. User Stories are discreet value propositions of a larger Feature or Enabler 4 from the Program Backlog 3. All User Stories will be tracked in Jira. This is because the CMS Jira implementation is able to read Jira projects and collect and collate pertinent metrics associated with team effectiveness.

Value Artifacts

All of the source code, infrastructure as code, documentation, dependencies, and everything else used to create the Value belong to CMS. As such, all repositories, Confluence spaces, etc. are to be provided to CMS.

Required Artifacts:

  • Personas

    "A Persona is a fictitious character embodying a segment of real-world users of your product, website or service. It is based on information gathered via research, both qualitative and quantitative."

    HCD Personas Training

  • HCD Research Methods

    HCD practices include many research and testing methods. All artifacts from these methods need to be stored, preferably in Confluence, and available for interested parties and stakeholders.

    A comprehensive list of these practices can be found in the HCD Space.

DevOps Metrics

While Team effectiveness metrics are gleaned from Jira projects, DevOps metrics must be provided.

  • Deployment Frequency
  • Deployment Lead Time
  • Mean Time To Restore
  • Deployment Failure Rate
DevOps Training

Development Value Stream Map


Getting the software value into production is just as important as the software value, itself. Automation, quality gates, package bundling and installation, and software scanning help increase quality and speed of delivery.

Mapping out the Development Value Stream 1 is critical to understand the system and where to focus on improvement opportunities.

All ADOs are required to create and maintain a Development Value Stream Map. This should be available in Confluence.

DevOps Training

Getting the software value into production is just as important as the software value, itself. Automation, quality gates, package bundling and installation, and software scanning help increase quality and speed of delivery.

Mapping out the Development Value Stream 1 is critical to understand the system and where to focus on improvement opportunities.

All ADOs are required to create and maintain a Development Value Stream Map. This should be available in Confluence. Learn more about Value Stream Mapping to request the LACE Value Stream Mapping Workshop


Software development partners are expected to provide the following artifacts, in addition to the working software that solves CMS's problems:

CMS Software


CMS uses the Atlassian Suite of software, which include Jira and Confluence.

All Software Development Partners are expected to use Jira to manage their Team Backlogs. This is required so metrics about team efficiency can be collected and shown using various dashboards.

All pertinent information, including the Development Value Stream Map, should be located in Confluence.



  • No labels