When everything is a priority
I was asked what to do when the customer won’t prioritize the stories and insists that everything has to be done now. That brought back memories of the first time that had happened to me. This was a very long time ago and I can’t remember who had given me the idea to approach it this way.
Why we branch the code
Branching is a great workaround for problems elsewhere in the system that we are unable or unwilling to fix.
Outcome bias (Resulting)
When I first read How to Decide: Simple Tools for Making Better Choices by Annie Duke, one of my biggest aha moments was from what she calls Resulting and is more formally known as Outcome Bias.
Flow Efficiency
Flow efficiency (sometimes called Cycle Efficiency) is a metric that gives us a sense of how much time work is waiting. A flow efficiency of 100% would indicate that we are adding value to the work item for the entire time it’s in progress. 50% would imply that half the time we’re working on it and half the time the work is just waiting.
Rapid feedback
One of the key things we’re trying to get with Agile is faster and more effective feedback so that we can make better decisions. This extends into to the technical practices just as much as it does in our meetings and processes.
Self-sufficient teams
A number of years ago, a client of mine had a new feature request come to one part of the company. It was a significant change that would touch quite a few teams to get done and when they asked those teams how long it would take, the answer was somewhere between 10 and 12 weeks.
“Assume positive intent”
When dealing with troublesome or difficult situations, someone will often chime in with the advice “assume positive intent”. Sometimes teams will even bake this into their working agreements as something they should always do. While I really do like the sentiment, if taken literally as a hard rule, this can be dangerous advice.
Building capacity when hiring juniors
My comments yesterday on social media about encouraging the hiring of juniors seemed to resonate. So let me tell you about two of the very best teams I’ve worked with. Two teams of juniors, that were freshly hired, many straight out of school and none of them having worked professionally for long.
Perverse Incentives: Coffee Badging
I learned a new term today: “Coffee Badging”. This is when a company has mandated that people be in the office, so they travel in to the office, swipe their badges, grab a coffee and perhaps talk to someone, and then head home again, where they remain for the rest of their working day.
Pull requests are not a quality step
I found myself quoting Deming in a question about Pull Requests (PR’s) today.