• Home
  • BVSSH
  • C4E
  • 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

  • Increased learning velocity and shared mastery
  • Higher engagement and psychological safety
  • Continuous improvement becomes cultural, not episodic
  • Teams reflect, adapt, and build confidence together
  • Improved ability to tackle complex or novel challenges

Risks of Not Having This Standard

  • Learning becomes siloed, superficial, or unintentional
  • Valuable lessons are forgotten or repeated
  • Missed opportunities to reinforce good practices
  • Innovation is limited by fear or perfectionism
  • Low morale when growth isn't recognised or celebrated

CMMI Maturity Model

Level 1 – Initial

Category Description
People & Culture Learning is informal and relies on individual initiative.
Mistakes are often hidden or repeated.
Process & Governance No structured approaches to reflection or knowledge sharing exist.
Technology & Tools Tools for documentation or collaboration are rarely used to support learning.
Measurement & Metrics Learning outcomes are not measured or reviewed.

Level 2 – Managed

Category Description
People & Culture Some teams value learning, but it's inconsistently encouraged.
Support varies across the organisation.
Process & Governance Basic learning activities (e.g. retrospectives) occur but are uneven in quality or frequency.
Technology & Tools Informal tools (e.g. wikis, shared notes) support learning in isolated teams.
Measurement & Metrics Occasional feedback is gathered but not systematically used to improve learning practices.

Level 3 – Defined

Category Description
People & Culture Teams embrace learning practices like pairing, retrospectives, and cross-training.
Process & Governance Learning rituals are embedded in team cadence and supported by leadership.
Technology & Tools Tools like knowledge bases, communities of practice, and pairing support systems are adopted.
Measurement & Metrics Learning is reviewed through qualitative feedback and tracked outcomes.

Level 4 – Quantitatively Managed

Category Description
People & Culture Teams measure and share learning impact.
Learning is treated as a critical capability.
Process & Governance Learning investments are prioritised through evidence-based planning.
Technology & Tools Tools support discovery, reuse, and visibility of learning activities.
Measurement & Metrics Trends in improvement, time-to-mastery, and team adaptability are tracked.

Level 5 – Optimising

Category Description
People & Culture Learning is celebrated as progress.
Experimentation and reflection are cultural norms.
Process & Governance Learning loops are embedded in delivery and strategic decision-making.
Technology & Tools Platforms support continuous learning, peer-to-peer growth, and knowledge curation.
Measurement & Metrics Learning outcomes are used to drive innovation, mastery, and resilience at scale.

Key Measures

  • % of teams engaging in structured learning activities (e.g. retros, knowledge shares, pairing)
  • Frequency and quality of team-level learning reviews
  • Adoption of learning platforms or support tools
  • Evidence of continuous improvement initiatives led by teams
  • Impact of learning on delivery outcomes and team confidence
Associated Policies
  • Psychological Safety First
Associated Practices
  • Engineering Onboarding Playbooks
  • Collaborative Story Refinement
  • Guilds & Chapters
  • Dev-Product Pairing
  • Tech Talks & Showcases
  • Mob Programming
  • Psychological Safety Practices
  • Pair Programming
  • Engineering Office Hours
  • Swarming on Issues
  • Retrospective Action Loops
  • Shared Learning Days

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

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