3 Measuring Your Way to PE Success
This chapter covers
- Using data and measurements to determine success
- Assessing engineering practice and quality over the entire end-to-end delivery lifecycle
- Acting on platform product KPIs and Developer experience impact
- Planning for maturing capabilities
So far in our journey at Epetech, we have established a vision and strategy based on the business need for building an engineering platform, and have put together the foundational engineering practices to create it. We have also looked at software-defined platforms and the cloud-native approach, which simplifies the process. The last critical element of our planning process comes - measuring what we will build. This chapter will round out all the pieces required to ensure we are setting up the platform engineering journey to succeed, not just in the short term but for scaling.
3.1 Organizational aspects of PE success
3.1.1 Changes needed for an organization to prepare for platform engineering
3.1.2 Prerequisites for the change
3.1.3 Implementing organizational changes
3.1.4 Building platforms in organizations
3.2 Path-to-production and Platform Value Metrics
3.2.1 How do you identify the scope of your engineering platform?
3.2.2 Platform Value Modeling and Metrics
3.3 Cognitive load and mechanical sympathy for developers and platform engineers
3.3.1 What is cognitive load for developers, and how do we measure it?
3.3.2 Why reduce cognitive load?
3.3.3 Techniques for reducing cognitive load
3.3.4 The need for mechanical sympathy
3.4 Common Platform Performance Metrics
3.5 Evolving Measures
3.5.1 Cost planning
3.5.2 Risk assessment
3.5.3 Mapping measurement to Core platform principles
3.5.4 Mapping measurement to platform engineering domains
3.6 Summary