Audience question: What will be delivered when?
July 24, 2022How do you create a plan for a team as to what will be delivered when?
On one of my Slack groups, I was recently asked:
How do you create a plan for a team as in what will be delivered when?
Here’s my answer:
In general, there is no way to know what will be delivered when. This is just a fact of life in software delivery.
So the challenge is determining how to deal with this reality.
The best approach is usually to just determine what single, small piece of work is most valuable to the client, customer, or business, and do that first. Then repeat.
By doing so, you’re guaranteed that you will always have delivered the most valuable software given whatever time frame you have.
Of course this approach is not without its challenges. If it were easy, there’d be no need for people like me to help teams achieve fast, reliable software delivery.
Question to readers: What are the challenges of incremental software delivery?
What makes working on the single most important, small change you can do, a challenge?
You don't always need to measure a metric to improve it
You don't need a dashboard until the difference you're trying to measure is too small to be casually obvious.
Platform engineering FTW
With a platform-team, there's no confusion over the question of specialization, as it's clear who does dev work and who does ops work.