Architecture & changeability
Map change hotspots and system boundaries; prioritize the coupling that repeatedly delays delivery.
SOFTWARE ENGINEERING · SELF-ASSESSMENT
Assess architecture, dependencies, delivery workflows, reliability and engineering ownership. Find the constraints behind risky changes and growing maintenance work.
15 questions · Around 5–7 minutes · Immediate results · No email needed for your score
WHAT WE ASSESS
Each dimension contains three questions with five concrete maturity choices. Your answers identify practices to strengthen and assumptions to confirm.
Map change hotspots and system boundaries; prioritize the coupling that repeatedly delays delivery.
Inventory dependencies and runtime support dates; assign owners and remediation targets for exposed components.
Make builds reproducible and establish automated checks and a tested rollback path for critical deployments.
Define user-facing service targets and connect actionable alerts to owners and recovery runbooks.
Reduce single-person dependencies through clear service ownership, onboarding paths and current operating documentation.
SAMPLE REPORT · ILLUSTRATIVE ONLY
Your result includes an overall maturity level, scores across five dimensions, evidence gaps and three suggested priorities. Download the full response record or use it to prepare an expert review.
Example priority: investigate the lowest-scoring dimension and confirm the evidence behind each answer.
HOW SCORING WORKS
Work depends heavily on manual response and individual knowledge.
Practices exist but are not yet consistently applied.
Core practices have defined processes and ownership.
Practices are measured, tested and improved using evidence.
Responses are scored from 1 to 5 and normalized to 0–100. Dimensions are equally weighted and require at least two known answers each. An overall score is shown only after all questions are answered and all dimensions can be scored. This framework does not compare you statistically with other companies.