No single right answer
All too often we focus on a single problem and make statements as if solving this one thing will solve everything. While that one thing might certainly make things better, it’s never the only answer. Everything we do is within the context of a complex adaptive system and changing any one thing will have ripple effects everywhere else in the system.
Driving to the airport
Imagine we wanted to estimate how long it would take to drive to the airport. You might see that it’s 50km to the airport and that your car can drive at 100km/hour. Therefore it will take 30 minutes, right?
WIP by Parent
One of the charts built into JiraMetrics is WIP by Parent, as shown below. What this shows is the total work in progress (WIP) on each given day. The WIP is then grouped by colour according to the parent (Epic in this case) that the original ticket belonged to.
Orientational metaphors and WIP
We all have an unconscious bias that says that up is good and down is bad. Lakoff and Johnson expand on this in their classic book “Metaphors We Live By”.
AI and Critical Thinking
While it doesn’t seem surprising that reliance on AI tooling would blunt our critical thinking, I am surprised how quickly it’s happening. AI tooling really hasn’t been in common use for all that long and already there are enough observable effects to be able to have studies on it.
Social proof in meetings
I’ve been in quite a few meetings recently where people are speaking in a passive voice, and saying things like “maybe someone could do this thing”. Naturally nobody does.
SpecFlow becomes Reqnroll
A number of my clients use SpecFlow and this will be relevant to them. SpecFlow has been end-of-lifed and replaced by ReqNRoll.
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 Matrix1, an approach I first learned from Steven Covey’s Seven Habits of Highly Effective People.
-
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. ↩