I got this situation for Lead Time of 4 Key Metrics when a requirement involves two different teams and how to use the 4KM more effectively
The situation is a requirement for a customer that requires two different systems and therefore two teams.
How would you measure here the Lead Time when one team takes longer than the other?
Do you consider Team B Lead Time to be 5 or 10 days? Measuring one way or the other opens different ways to manage work.
I don't add "it depends" option because I know it always depends 😜
If you consider 5, you actually are measuring when you "finish" the user story, but not when it's delivered to the user.
Here you see the team performance in isolation of others.
It causes that even though the team is a high performance, the organization isn't.
Local maxima
If you consider 10 days, you might become frustrated. You were fast, but you're depending on other teams to ship it. Causing your metrics to get worse.
Yet, I consider the most insightful way to measure Lead Time. It shows team dependencies and, maybe, unclear boundaries
I'm not saying that you can avoid these situations, but by measuring them this way, you can see how many times it happens and you can take decisions to improve them.
Here you are betting for organization performance
• • •
Missing some Tweet in this thread? You can try to
force a refresh
1/ "We expect that anything can happen and we are never prepared for anything"
This sentence resonated a lot with me
Regardless of the risk management, regardless of being adaptative, regardless of how prepared do you think you're, World keeps surprising you
2/ As a manager, your job is to make the teams, product, and business more resilient and adaptative to survive in several situations.
Yet, I never felt that we reached a level where we can say
"We're safe!"
It's not viable.
3/ You manage the areas that are more probable to happen and the impact is higher. Then, you just accept those situations that are outside that scope, to be handled as you can.
1/ We have been debating with some colleagues about the importance of learning about our decisions within the organization, and how the fast rotation of talent that's happening lately is affecting the decision-making outcomes quality.
2/ Here we had the supposition that the feedback cycle between a decision is made and understanding the consequences are long enough. We always thrive for fast feedback loops, yet we acknowledge that that's not always possible.
3/ It's not the same doing TDD within a unit test - feedback cycle of seconds-minutes vs a business decision and go-to-market strategy that can take months.
We are talking about the latter. Where those business learnings are most valuable for the organization
1/ When you start doing project development, you find yourself with tight deadlines, a lot of tradeoffs in quality, and money spend.
You start feeling that you might be doing something wrongly. You feel that you're not delivering business value
Thread 🧵
2/ You learn about Agile, and why deliver working software as soon as possible. You adopt Scrum, but with a project mindset. So, it's a fake Scrum. It's more like a 2 weeks waterfall.
Yet you adopt a very important ceremony important, the Retrospective.
3/ Based on Retrospectives, you start questioning yourself how are you working. Why can we deliver value to the customer? Why aren't we customer-focused?
We have been practicing #NoEstimates for 8 months. Here are some learnings 👇
We started in a legacy code in which the people that created that service left the company some months ago and we needed to deliver some critical features
No business knowledge, no technical knowledge, a mess ahead
Business: Will you be on time?
Me: No clue yet, give me 2 weeks
Should we go for all the work for 2 weeks, analyze the Job to be Done and come back with an estimation?
We had a very tight deadline, 1month and a half to deliver