• Home
  • BVSSH
  • Engineering Enablement
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Standard : Developer workflows are fast and frictionless

Purpose and Strategic Importance

This standard ensures developer workflows are optimised for speed, clarity, and flow-minimising friction, blockers, and waste. It enables engineers to focus on delivering value, not fighting tools or processes.

Aligned to our "Automate everything possible" and "Developer Experience Matters" policies, this standard drives both team efficiency and satisfaction. Without it, productivity drops, morale suffers, and the cost of change increases.

Strategic Impact

Clearly defined impacts of meeting this standard include improved delivery flow, reduced risk, higher system resilience, and better alignment to business needs. Over time, teams will see reduced rework, faster time to value, and stronger system integrity.

Risks of Not Having This Standard

  • Reduced ability to respond to change or failure
  • Accumulation of technical debt or friction
  • Poor developer experience and morale
  • Decreased confidence in releases and features
  • Misalignment between technical implementation and business priorities

CMMI Maturity Model

  • Level 1 – Initial: Developers frequently encounter blockers and wait states.

  • Level 2 – Managed: Some teams use tools to streamline workflows but experiences vary.

  • Level 3 – Defined: Developer toolchains are consistently adopted and documented.

  • Level 4 – Quantitatively Managed: Developer efficiency and satisfaction are measured.

  • Level 5 – Optimising: Workflow friction is continuously identified and removed through feedback and telemetry.


Key Measures

  • Adoption metrics relevant to the standard (to be defined)
  • Quality, throughput, and system health metrics aligned to capability
  • Maturity scores based on structured assessment
Associated Policies
  • Developer Experience Matters
  • Minimise Handoffs
Associated Practices
  • Code Reviews & Pull Requests
  • Data Mesh
  • Dependency Management Policies
  • Event Sourcing
  • Evolutionary Architecture
  • Linting and Static Code Analysis
  • Mocking and Stubbing
  • Secure Code Training
  • Security as Code
  • Serverless Architecture
  • Security Testing in CI/CD
  • Developer Environment Automation
  • Engineering Onboarding Playbooks
  • InnerSource Development
  • Operational KPIs for Dev Teams
  • Service Mesh Implementation
  • Twelve-Factor App
  • Working Agreements
  • Health Checks & Readiness Probes
  • Log Correlation for RCA
  • On-Call Rotation Health Checks
  • Runbooks and Playbooks
  • User Session Replay Tools
  • Customer Feedback in Dev Loops
  • Feedback Loops from Ops to Dev
  • Real-time Event Streaming
  • Automated Rollbacks
  • Static Application Security Testing (SAST)
  • Ensemble Testing
  • Shift-Left Testing
  • Test Coverage Analysis
  • Test Data Management
  • Mobile-First Design
  • Observability-Driven Design
  • Value Stream Mapping
  • Async Collaboration Norms
  • Onboarding Playbooks
  • Sprint Demos for Stakeholders
Associated Measures
  • Deployment Frequency
  • Lead Time for Change
  • Code Review Cycle Time
  • Cycle Time
  • Developer Satisfaction (DevEx NPS)
  • Onboarding Time
  • Time to First PR
  • Automated Test Coverage
  • Automated Test Pass Rate
  • Code Churn
  • Code Coverage

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering