Continuous Learning

Idea: Create culture of continual learning and experimentation. A Symmathesy.

Leadership sets tone that making mistakes, learning, try again is okay
Make Improvement of Daily Work part of everyone’s daily routine
Bubble up knowledge so that local discoveries become global improvements
- Discoverable Knowledge
- Collaboration between teams, projects, etc., is difficult if people don’t have visibility into what’s happening
Add Resiliance patterns into daily work
Reinforce a learning culture
Called out explicitly in Phoenix Project: 3 Ways but all healthy learning systems tend towards this mindset. See Comparing Learning Systems.

Enabling a growth mindset in teams requires Psychological Safety.

Links to this page

Symmathesy

A flow of mutual learning. Critical to enabling Continuous Learning.
Software Engineering as a Team Focus

Continuous Learning
Services

Facilitates Continuous Learning
Project Metrics

As one works on Developing Good Explanations, there needs to be a way to analyze the work that’s being done and to reason about it. Otherwise, Continuous Learning won’t happen and it will become harder and harder to know that your software is a Good Explanation. Even more so if you desire for your Good Explanations to be Self-Validating Good Explanations.
Phoenix Project: 3 Ways

Continuous Learning
Performer Metrics

Sharing (Continuous Learning, Discoverable Knowledge)

Metrics in this sense are really a more formal and principled way of reflecting on Development Environments as a way of achieving Continuous Learning and Improvement of Daily Work. They won’t be effective or even be possible to truly obtain until the environment is an empowering one Empowering Environments. Put another way, performer metrics are a way to ask the question “if one wants to increase Joy at Work, how can they do so most effectively?”
Good Explanation

What’s even better than a good explanation is to have Self-Validating Good Explanations. Continuous Testing and Continuous Delivery enables Continuous Learning, which is what enables Continuous Compliance.
Empowering Environments

Continuous Learning
Disposability

Facilitates Continuous Learning and fearless and rapid iteration of Theories Under Test
Developing Good Explanations

Continuous Learning
DevOps Topologies

Different teams and topologies have differing levels of effectieness. Some are very effective, some are conditionally effective, and some are so commonly ineffective that they are known as anti-patterns. Ultimately, every topology should serve the purpose of enabling Continuous Compliance, and fostering Continuous Learning.
Continuous Compliance

Continuous Learning
CAP Theorem for Software Engineering

They offer more advice on ways to improve the process as part of an emphasis on Continuous Learning as a means of Focus, Flow, Joy, rather than for the sake of facilitating Joy at Work.
Build Quality In

Relentlessly Pursue Continuous Improvement: Continuous Learning

Having Continuous Learning implies that once things are learned, they don’t need to be re-evaluated. This is why it’s so important to have Self-Validating Good Explanations. Creating and evolving Feedback Loops to detect problems as early as possible is essential.

#culture