Are you just looking for the latest articles and want to skip all the preamble and summary? Click here.

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, let me know and I'll get them fixed.

Browse by topic area:

Category	Formerly found at
Psychology & Behaviour	UnconsciousAgile.com
Flow, Kanban, Scrum	ImprovingFlow.com
Metrics and Forecasting	ImprovingFlow.com & MikesHardMetrics.com
Technical Practices	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!

• Neuroscience / Psychology
  • 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.
  • 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.
• How to improve...
  • Meetings: The common problems with meetings. Improving the standup / daily coordination meeting. Retrospectives are covered in my popular video course Retrospective Magic. Then what if your people won't participate?
  • Improving learning: with neuroscience and LEGO.
  • Improvement: Continuous improvement in general. Understanding the metaphor of "lowering the water level".
• Flow of value
  • Metrics: Flow metrics, probabilistic forecasting.
  • Waste: Overview of waste. Understanding the cost of interruptions, and the kinds of waste that gets in the way of flow.
  • Work in progress (WIP): Setting initial WIP limits. What to do when we're overwhelmed with WIP
  • Metrics and Forecasting: All of these have their own category now.
• Technical practices: Continuous integration, TDD as design, and ensemble programming.
• Ensuring we're building the right thing: Slicing stories and epics. Understanding the context of what we're building. Knowing how to prioritize that work.
• Something fun: The millennial whoop, and inattentional blindness.
• Recommended reading: I'm often asked for book recommendationsbook recommendations.

---

Jira’s Start Standup Button

For a while now, I’ve been noticing a “start standup” button at the top of Jira boards and I’ve been wondering what it did. Today I pushed that button in the hope that it would do something to help make the standup more effective, and now I wish I hadn’t.

Explaining technical work in business terms

IT people are notoriously bad at explaining technology issues in business terms. So it should be no surprise when the people funding the projects don’t want to spend money on things that sound like gibberish to them. There are real product gaps that they want fixed and they have no time for “cleaning up technical debt” or “doing automation” or “upgrading framework X to version 2”.

Eisenhower Matrix

Sometimes a new piece of work will arrive and it’s not immediately obvious whether we should start it now or if it can wait. A quick triaging technique that I use is called the Eisenhower Matrix¹, an approach I first learned from Steven Covey’s Seven Habits of Highly Effective People.

1. Former US President Dwight Eisenhower developed the ideas behind this tool, and used them extensively in his work with the military and later in his role as president. ↩

Mob mentality podcast

I was interviewed on the latest Mob Mentality Show, a podcast devoted to mob programming, also known as ensemble work or software teaming.

Ensemble work feels slower, but that’s deceptive

It’s interesting that when a team tries ensemble work (also called mob programming), it feels really slow. Slower than it actually is.

Only one ticket per work item

We should only have one ticket on the board for any given piece of work. This should be obvious and yet I see this problem on a regular basis.

Basic Flow Metrics

Flow metrics tell us about the activity in the system; how well is the work flowing. These are often the first metrics that I consider when trying to improve a system. I start here partially because these metrics are easier to collect than many others, and because I can still make many effective decisions based on just this.

Survivor Bias

“Survivor bias is the logical error of concentrating on entities that passed a selection process while overlooking those that did not. This can lead to incorrect conclusions because of incomplete data.”
— Wikipedia”

Cognitive Bias

It would be easy to think that all cognitive bias is a bad thing. When we hear people talking about it, it’s often in the context of the collection of biases that make up racism or sexism or other generally negative things. Yet, the truth is that cognitive bias is the way that our brain manages energy use and is overwhelmingly a positive thing for us.

Continuous improvement

Back in the days when faxing between companies was a popular thing, I recall a client that had a workflow like this:

1. Fax arrives and is printed by the fax machine
2. Paper is picked up by a person and carried to the scanner where is it digitized.
3. Paper is immediately shredded because there was confidential information on it.