Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Good morning team.
I am working on a new Kan Ban team from scratch. My question is. How or what is the best way for metrics utilization? I want to make milestones but I’m not exactly sure what metrics are used to show board meetings where we are. – hope this made sense.
Thanks
Ah – I’d tend to keep the team-level metrics away from any external group; these are things for the team to help improve throughput and delivery, not for high level discussion.
What I tend to show at a high level is a forecast for delivery based on the team’s mean 9and standard deviation) of the throughput.
We’re usually using a “feature level” upstream Kanban for large items. For the initial sizing I tend to get the team to estimate using the Fibonacci scale in sprints/iterations/weeks/months (ie a big time unit). We don’t get to a single figure always, just the range they are 85% confident in.
We then refine that work through story mapping sessions, surfacing assumptions (which can become risks to be managed), as well as unknowns (to be addressed with spikes)
That provides a pretty accurate forecast overall, with a precision that is improved as we
– story map and do spikes to refine the estimates
– do the work get feedback and discover work
It’s certainly enough for meso-scale operational planning (which quarter will X be delivered, do we need to hire more people, do we need to split a feature into parts etc.)
Once you have maybe 30-50 features completed then you’ll have enough data just to use the mean and standard deviation of the feature cycle time for forecasts.