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

What are you looking for?

Standard : Teams celebrate growth through deliberate learning

Purpose and Strategic Importance

This standard ensures teams embrace and celebrate growth through intentional learning practices-like retrospectives, pairing, and knowledge sharing. It cultivates curiosity, reinforces mastery, and builds collective confidence.

Aligned to our "Psychological Safety First" policy, this standard helps teams treat learning as progress, not failure. Without it, growth becomes accidental, and valuable insights are lost or overlooked.

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: Learning is informal and largely dependent on individual motivation.

  • Level 2 – Managed: Some teams prioritise learning opportunities, but support is inconsistent.

  • Level 3 – Defined: Learning practices (e.g. pair programming, knowledge shares) are standardised.

  • Level 4 – Quantitatively Managed: Learning effectiveness is reviewed and resourced based on outcomes.

  • Level 5 – Optimising: Continuous learning is embedded in culture, tied to strategy, and measured for impact.


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
  • Psychological Safety First
Associated Practices
  • Collaborative Story Refinement
  • Engineering Onboarding Playbooks
  • Guilds & Chapters
  • Dev-Product Pairing
  • Engineering Office Hours
  • Mob Programming
  • Pair Programming
  • Psychological Safety Practices
  • Retrospective Action Loops
  • Shared Learning Days
  • Swarming on Issues
  • Tech Talks & Showcases
Associated Measures
  • Developer Satisfaction (DevEx NPS)

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

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