Roles: Product-Manager

This checklist ensures that user documentation adheres to relevant regulatory, legal, and organizational standards. It is particularly important for regulated industries (e.g. medical, automotive, and industrial IoT) or when documentation is published publicly.

The definition of done (DoD) for L4 bugs are the checks performed when an L4 bug is considered completed.

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.

In emergency situations, software corrections may be required in a short time frame to solve a critical issue on the customer site. This type of emergency correction will be handled as a temporary correction (TC).

This guide provides handson support for the roles involved in executing test cases and reviewing test results.

This guide describes the process for handling software vulnerabilities in products within PCP R&D. It includes instructions on everything from recording a description of a reported issue to documenting and communicating its remediation.

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.

Various certifications are applied for in the development of products. This guide covers the ten activities of the general certification flow, and includes specific information regarding marine certifications, certifications for hazardous areas, certification affecting manufacturers, and the order of certification applications.

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

This guide describes how to handle epics in streams. It includes examples of epic descriptions and information about the epic definition, grooming, and change management.

This guide describes how to handle features in streams. It includes examples of feature descriptions and information about the feature definition, grooming, and change management.

This guide describes how to handle system requirements and system epics. It includes descriptions and information about the system requirement / system epic definition, workflow, grooming, and change management.

For a new epic, feature, or user story, there may be a need to write new test cases or modify existing test cases. The purpose of this guide is to provide handson support to the roles involved in writing, updating, or reviewing test cases of a product.

Product capabilities describe what the product “can do” for anyone who wants to understand its capabilities. They represent the product's property and are updated throughout its lifecycle through multiple releases.

This guide describes how system requirements in Decision Focus are broken down into system epics, epics and features in Azure DevOps (ADO).

This guide describes different types of software vulnerabilities and associated threats. It also describes various defense mechanisms that are typically needed to be prepared for software attacks.

The system test is a crucial step in the development process as it integrates and tests deliverables from the various development streams.

This process area is responsible for the key processes involved in creating and maintaining user documentation. It covers principles, activities, artifacts, and dependencies to ensure comprehensive and accurate documentation.

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