Roles: Quality-Control-Manager

This checklist supports documentation teams in ensuring that userfacing content is accessible to all users, including those using assistive technologies. It can be applied during content creation, review, and prepublication.

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

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.

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

The quality dashboard can help teams measure and compare product quality by setting appropriate widgets and queries. A common template based on standardized queries will help save effort and improve efficiency. By setting appropriate widgets and queries, the quality dashboard can help teams measure and compare product quality. A template based on standardized queries helps save effort and improve efficiency.

Below is a short introduction to testing on different DMS link types. Use this page to take a look at how to get and how DMS links work. Before going to the DMS links URL, here are some tips for URL anatomy. For more details, please see the DMS documentation.

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.

This guideline outlines how to organize and manage product and project documents during development and maintenance. It applies only to internal R&D documents at the product and project level, not for publication through the ABB Library or other channels.

Introduction

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.

When starting a new project there are several tasks to be performed to ensure that tools and systems are well set up when M0/G0, M1/G1, and M2/G2 are reached.

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.

This guide describes the routines for stopping and restarting the manufacturing, delivery and/or ordering of products within PCP.

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

R&D quality dashboards can be automatically created, based on Azure DevOps (ADO) data, to support the organization in visualizing project progress based on quality key performance indicators (KPIs).

The PCP System Epic Dashboard is used to visualize the implementation progress of system epics, by planning and tracking child epics and features whose completion is required to fulfill a given requirement.

The quality process describes how to create and maintain the PCP R&D processes. It also includes quality control, definition and evaluation of KPIs, and how to facilitate process improvements.

The quality control manager (QCM) performs quality assurance activities on development and system streams, identifies quality issues, and ensures they are managed to closure. He/she coordinates the activities required to ensure that the quality meets customer expectations, required quality standards, and defined processes.

Key performance indicators (KPIs) are used within PCP R&D to better understand, control, and manage the organization.

The "R&D Quality Criteria" is a tool and checklist for Quality Control Managers (QCM), and is used to plan quality audits and assessments for project milestones and report quality status.

References between artifacts (e.g., documents and web pages) support the user to find more information easily. It also ensures the same content isn't repeated in several places and can therefore simplify maintenance. But wrongly used, with too many references, the contents can be hard to read for the user and become costly to maintain.

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 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.

Test case audit checklist.

This tutorial gives an overview of how to work with Markdown. It describes how to change content on the "PCP R&D Processes" website, and can also be valuable for anyone using Markdown in Azure DevOps (ADO).

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).