All of this content used to be spread over three different blogs at three different domains and it's now been merged into one. Why was it ever three? Because at the time it seemed reasonable that each of them was for a different audiences, and yet over time I've found that the lines between topic areas got blurrier and tended to overlap. So now they're all together in one place.
If you encounter things that seem broken, please let me know and I'll get them fixed.
Browse by topic area:
- Psychology & Behaviour (Formerly UnconsciousAgile.com)
- Flow, Kanban, Scrum (Formerly ImprovingFlow.com)
- Technical Practices (Formerly AgileTechnicalExcellence.com)
There's a lot here and if you're not sure where to start, here are some popular starting points. From these, you'll find crosslinks to even more topics. Enjoy!
- Psychological Safety: An overview. For the science, see the SAFETY model. For Google's research into why it's important for high performing teams, see Project Aristotle. What happens when we don't have that safety?
- Anxiety and Stress: For the science, see Polyvagal Theory or a description of some neuroscience, illustrated with a bear encounter. To let go of that anxiety, see the Anti-Anxiety toolkit.
- Recommended reading: I'm often asked for book recommendations.
- Generally more about the brain: Cognitive bias, motivation, default mode network, systems 1 & 2 and neurotransmitters (chemicals) that drive behaviour.
- Language patterns: Why language is so important, and Clean Language, a specific language pattern that has excellent application for coaching.
- Improving your meetings: Specifically retrospectives (my video course), and standups. What if your people won't participate?
- Improving learning: with neuroscience and LEGO.
- Flow & Kanban: Flow metrics, probabilistic forecasting, and understanding waste.
- Technical practices: Continuous integration, TDD as design, and ensemble programming.
- Something fun: The millennial whoop, and inattentional blindness.
The millennial whoop and our brain as a prediction engine
Our brains are highly advanced prediction engines1. They are constantly trying to predict what will happen next so that we can be prepared for what’s coming. When our brain makes a successful prediction then we get rewarded with a tiny shot of dopamine that makes us feel good.
-
Professor Lisa Feldman Barrett explains how our brains evolved as a prediction engine in her excellent book Seven and a Half Lessons About the Brain ↩
Google’s Project Aristotle
You may have already heard of Google’s Project Aristotle. Back in 2012, Google set out to identify what made their most effective teams so much better than others. They wanted to reproduce that magic that some teams had across the company and so they interviewed 180 teams and collected all kinds of data.
Code coverage is a perverse incentive
While code coverage can be a useful measurement for teams to improve their own results, the moment it’s tracked by people external to the team, particularly management, it becomes a perverse incentive.
What’s wrong with the common Scrum questions?
Each day during standup, most teams will have every answer three questions. The questions most commonly asked are fairly poor and result in a undesirably bad meeting.
Waste: Psychological Distress
One of the more subtle forms of waste is psychological distress. When we are afraid or anxious, our sympathetic nervous system activates to prepare us for one of fight, flight or freeze. All good responses in a survival situation.
Understanding waste in the system
In Kanban, we are always trying to optimize for efficiency, effectiveness and predictability. Waste in the system is something that hurts all three of these objectives and is something we want to remove or reduce wherever possible.
The only way to win is to learn faster
Over the past 15 years of working with various agile techniques, practices, frameworks, and strategies I’ve found that there is one thread that ties them all together. They are all focused on improving our ability to learn and to apply that learning to our future work.
Determining cycle time from an online system
This post is aimed at a fairly niche audience so if you aren’t trying to make sense of poor data out of some ticketing system then you might want to skip this one.
Improving the daily coordination meeting
Just about all agile methods have some kind of a daily coordination meeting. It might be called a standup or a daily coordination meeting or a daily scrum or any number of other things. The point is that this meeting is focused on actively managing the work and it’s frequently done poorly.
Setting initial WIP limits
When starting a team up with Kanban, one of the earliest questions is how to you set initial WIP limits. The simple rules we use are covered in this video.