Skip to main content

PCP R&D Quality Dashboards

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

Intended for​

The quality dashboards provide valuable support to release owners, quality control managers (QCMs), and product owners during meetings.

For terminology and KPI descriptions, refer to the legend page on respective dashboard (or use the direct links below).

image.png

Dashboard access​

Access is provided for all PCP employees who are part of this AD group.
In case of any issues with access, please contact Piotr Salamon.

Data upload schedule​

Automatic data upload is scheduled every 4 hours, starting at 4:00 AM CET, with update times shifting to UTC+1 during daylight saving time. The latest data refresh date and time are shown in the top-right corner of the dashboard:

image.png

Projects/releases adding/updating​

Contact the respective QCM to add a new release/project setup or to modify the existing one.

Naming convention​

Release names in "Dictionary" should follow the general pattern which is specific for a given solution described below:

  • 800xA 6.2
  • 800xA 6.2 - AV
  • 800xA 7.0
  • 800xA x.y - xyz
  • S+ Phoenix

Tips & tricks​

  • There must be parent/child links between epics and features to make the project progress dashboard work. Additionally, effort and target dates should be filled in in epics and features in ADO/TFS.
  • “Project start date” on ConfigApp should be the same as the G2 date (the date when full release scope is committed).
  • All new setups and changes are implemented during the next daily data upload (at 2-4 AM CET).
  • When using a specific area path for deferred bugs, that area path must also be added in the "Product" bugs configuration (this may also be required in scope/introduced bugs configuration).
  • When configuring the area path for deferred, an "and" to "state closed / reason deferred" is required.
  • The “deferred” must rely on state (closed) and reason (deferred) to differentiate from open bugs. The configuration cannot rely solely on tags, iteration path, or others to define deferred bugs.
  • Project progress dashboard works appropriately only for work items (epics & features) using standard templates. Teams using customized work item templates are encouraged to move to the recommended ones.

Current issues/limitations​

If you encounter this issue while pasting a value (e.g., for a specific area path), you might not be able to select it. The workaround is to select a different area path first, then paste the copied value again, and it should work.

For any further issues, please contact: Piotr Salamon.

References​

Owner: Quality and KPI Team