Categories: Configuration-Management

"Area Path" and "Iteration Path" are standard fields in Azure DevOps (ADO), and they are used to organize work items by product classification, team, and time period.

Definition

For an introduction to the concept of baselining, see the Highlevel baseline guide.

This guide describes the recommended branching strategy to manage code repositories.

This guide describes how bugs – when they are created in Azure DevOps (ADO) – also are classified to ensure that they are handled with regards to their severity and potential impact.

This conceptual guide explains the purpose of configuration audits and presents the main parts of a configuration audit and the highlevel approach adopted in PCP.

Configuration Management is the process of identifying and defining the items in the system, controlling the change of these items throughout their lifecycle, recording and reporting the status of items and change requests, and verifying the completeness and correctness of items. [IEEEStandard7291983].

This is the overall description of how to handle configuration release management within ABB PCP.

The term Document Management includes both Office files and wiki pages. While the general processes are the same – such as version control, review, and approval – the specific procedures for each type of document differ and are described in the relevant guides.

A product issue is a uniquely identified problem impacting a product, requiring clear communication with various stakeholders. It must be documented with accurate information and version details and managed in parallel with bug management and product releases.

An existing Azure DevOps (ADO) project onpremises or in the cloud may differ from the current standard PCP work item templates due to historical reasons or tailoring. This guide lists the steps and tools to adopt standard work item templates in an existing ADO project with existing data.

This guide focuses on describing the practical change of the work item, starting from a process change request received, to the completion of a pull request updating the template.

Introduction

A bug can exist in multiple releases, and such bugs can be challenging to track and fix. This guide describes how to manage them.

During the development of a release, if a bug is found but the CCB decides to fix it in a later version, the bug is deferred. After the official release, it will then be a known bug in the product or system.

A work item of type "Bug" can be used to suggest an enhancement, something that is not a real defect, but an idea for improvement. This guide describes how to handle enhancements as bugs.

A bug is an unexpected problem in the software or hardware which can be reported for any issue in a product by e.g. product managers, product owners, test engineers, or customers (via L3 or L4 Support).

Dashboard creation can be repetitive and time consuming. This guide describes how to manage dashboards automatically.

Query creation can be repetitive and time consuming. This guide describes how to manage queries automatically.

The purpose of configuration auditing is to objectively assess the integrity of a product, both from a functional and physical perspective.

Defining a team in Azure DevOps (ADO) allows the use of planning and visualization features, for example, the team backlog, sprints, capacity planning, boards, and team dashboard.

A regression bug is a bug that causes a completed feature that worked correctly to stop working after updates (e.g., system upgrade, system patching, or bug fixes). This definition applies both before and after releasing the feature to customers.

This is a sample Handlebars template for generating a release change list for a multistage yaml pipeline that consumes multiple artifacts

This guideline describes the custom standard fields used in bug templates. For a more general picture of the standard work item template change process in Azure DevOps, see ADO standard work item template change management process.

This guideline describes the Document Update work item type and the custom standard fields used in its template. For a more general picture of the standard work item template change process in Azure DevOps, see ADO standard work item template change management process.

This guideline describes the custom standard fields used in the Epic template. For a more general picture of the standard work item template change process in Azure DevOps, see the ADO standard work item template change management process.

This guideline describes the custom standard fields used in the Feature template. For a more general picture of the standard work item template change process in Azure DevOps, see the ADO standard work item template change management process.

This guideline describes the fields used in the system epic template.

This guideline describes the custom standard fields used in the Test Case template. For a more general picture of the standard work item template change process in Azure DevOps, see ADO standard work item template change management process.

This guideline describes the custom standard fields used in the User Story template. For a more general picture of the standard work item template change process in Azure DevOps, see ADO standard work item template change management process.

Overview

This guide describes the different states of Azure DevOps (ADO) work items. Consistent work item state transitions are essential to enable consistent follow up on status.

The traceability of the work items shows the relationship between them in Azure DevOps (ADO).

This guide describes traceability between work products that are not in Azure DevOps (ADO).