Close
View this page in your language?
All languages
Choose your language
Introduction
1. Planning for your internal developer platform
1.1 Key stakeholders
1.2 Goals and Objectives
2. Design and Architecture
2.1 Connected Toolchain
2.2 Scorecard Design
3. Compass setup and integration
3.1 Populating the Component Catalog
3.2 Connecting Tools and Applications
3.3 Creating Scorecards
3.4 Creating Templates
4. Compass rollout
4.1 Rollout Strategy
4.2. Tracking Adoption and Data Hygiene

4.2 Rollout

4.2.1 Adding Component Owners and Teams to Compass

Component owners must receive the communication outlined in 4.1.2.5 prior to being added as owners in Compass. Once an adopter group has attended an information session and understands what they need to do and why, it’s time to start adding component owners to Compass.

video thumbnail
Watch now
Info icon

RESOURCES

4.2.2 Tracking Adoption and Data Hygiene

Having a complete component catalog is critical to success with Compass, and this requires little effort from component owners. Once component owners and their leaders understand what they need to do and have agreed on a timeframe (adoption window), it’s time to start tracking adoption and data hygiene.

The Component hygiene scorecard created in section 3.3 will be the data source for the weekly communication sent to the adoption groups and senior leaders (communications 4.1.2.3 and 4.1.2.4).

Message icon

Data for weekly adoption and data hygiene communications

  1. Log in to Compass and click on Components in the top navigation
  2. Click on the Scorecard filter and select Component Hygiene
Scorecard screenshot
Message icon
  1. Further filter the results by clicking on Scorecard status and selecting Needs Attention and Failing.


The list of components that have not yet been updated with the required information are returned in the component list.

4.2.3 Feedback loops and Tracking benefits

Similar to any type of project, it’s important to track and communicate the realization of benefits associated with your Compass rollout. The goals and objectives identified in section 1.2 should be revisited prior to and after each adoption window (where appropriate). Feedback should be sought from component owners and engineers after each adoption window to identify what could be improved for the next, and to validate that goals and objectives are being met. Communications should be sent to senior stakeholders and Compass adopters that outline progress with meeting the project's original goals and objectives.

PDF illustration

Improve developer experience with Compass

Download PDF