Process for Engineering Managers
Engineering process is how a team plans and tracks work: agile ceremonies such as sprint planning, standups and retrospectives, estimation and roadmap planning, and metrics that show how delivery is going. Common metrics are the four DORA measures, deployment frequency, lead time, change failure rate and time to restore.
Stage: Delivery and Execution · Part of the Engineering Manager roadmap · Last reviewed 19 November 2026
What to learn in Process
- Run sprint planning and retrospectives that produce concrete, owned actions
- Break large projects into milestones and communicate honest delivery ranges
- Track the four DORA metrics and explain what each one reveals
- Avoid using velocity or lines of code to compare or rank individuals
- Adapt the process to the team's maturity instead of copying a framework wholesale
Process interview questions
What are the DORA metrics?
They are four delivery measures: deployment frequency, lead time for changes, change failure rate and time to restore service. Together they show both speed and stability. Teams use them to spot trends and bottlenecks, not to rank people.
Why is story point velocity a poor performance measure?
Velocity is a team-specific planning aid and points are relative, so they cannot be compared across teams. Treating it as a target invites inflated estimates and gaming. It is useful for forecasting a team's own capacity, not for judging output.
Where Process fits in the Engineering Manager roadmap
Process belongs to the Delivery and Execution stage (advanced level), which takes about 5 hours. Predictable output.
Other units in this stage
Back to the full Engineering Manager roadmap