LACE (CCSQ Lean Agile Center of Excellence)

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

Expected of CMS




help

Icon Legend

close legend
  • learning icon
    Learning Opportunity - click the icon to be directed to the corresponding trainings for the subject
  • learning hcd icon
    HCD Learning Opportunity - click the icon to be directed to the corresponding HCD training
  • persona icon
    HCD Persona - click the icon to be directed to the corresponding HCD persona
  • hcd link icon
    HCD Topic - click the icon to be directed to the corresponding HCD topic


The following artifacts should be created and maintained by CMS (Business Owners, Solution Management, Product Management) and should be provided to ADOs and other Stakeholders.

Vision 


The Vision 1 is a description of the future state of the Solution under development. It reflects customer and stakeholder needs, as well as the Feature and Capabilities proposed to meet those needs.

Operational Value Stream Map


Operational Value Streams 1 (OVS) are the sequence of activities needed to deliver a product or service to a customer.

Objectives and Key Results (OKRs)


Objectives and Key Results, or OKRs, for short, are plain language goals and the measures of success for those goals. How do we know what the goal is? How do we know if reached the goal? Does everyone agree on what success is?

The goal of using OKRs for strategic themes 1 is to define and track their progress through concrete, specific, and measurable actions. “OKRs are frequently set, tracked, and re-evaluated – usually quarterly. OKRs exists to create alignment and to set the cadence for the organization. The goal is to ensure everyone is going in the same direction, with clear priorities, in a constant rhythm.”

OKRs Training

Program Backlog


The Program Backlog 1 is the holding area for upcoming Features, which are intended to address user needs and deliver business benefits for a single Agile Release Train 3 (ART). It also contains the enabler features necessary to build the Architectural Runway 2.

The Program Backlog is created, refined, and prioritized by Product Management 4.


Expected of Software Development Partners

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

  • No labels