Time Efficient ⏱ Sprint Planning With Kanban Metrics

No video

Time Efficient ⏱ Sprint Planning With Kanban Metrics

Рет қаралды 2,989

Күн бұрын

Have you ever been in a dreaded Sprint Planning where the majority of the time is spent on debating the story points for each Product Backlog item. In this video we will explore how to save time and make a forecast with #NoEstimates
This video is supported by Kanbanize. If you subscribe to Kanbanize from this link, I will get a small commission that can support this channel. Kanbanize Referral Link: kanbanize.com/...
#scrum #kanban #programmer

Пікірлер: 20

@jdpartogi 2 жыл бұрын

Wow! Thanks a lot the sprint planning advice, I think this is a great video to share amongst people who want to use scrum in their companies. One question though. Will you pin this comment?

@scrummasterinblack 2 жыл бұрын

Ok. Pinned. Thanks for watching. :) I hope you enjoyed it.

@thigorharahap 2 жыл бұрын

Fun to watch, well produced! ton of wigs you have

@scrummasterinblack 2 жыл бұрын

Thanks for watching. 🙈

@freddymu 2 жыл бұрын

Great! I've read a NoEstimate book and this video makes me "click" with the idea

@rotuapanjaitan5299 2 жыл бұрын

Niat bener coach!! :D with the wigs and mustache and everything :))

@scrummasterinblack 2 жыл бұрын

🙈

@nickfifield1 2 жыл бұрын

Funny video. However really interesting tool. Will take a look . Thanks

@scrummasterinblack 2 жыл бұрын

All the best Nick 🙌

@donye3286 2 жыл бұрын

Hahahaaa... Menghibur 😍

@locbkit 2 жыл бұрын

Thanks for introducing the tools. I knew Monte Carlo simulation in practical Kanban book but difficult to find out a tool to simulate, mostly we are using Jira. One more concern about the team should focus on the outcome instead of output (number of items can be done).

@scrummasterinblack 2 жыл бұрын

Yes. The focus should still be outcome metrics. Monte carlo can help for forecasting.

@JM-jc8ew 2 жыл бұрын

Dev: I picked 5 SP because .... Technical explanation .... ScamMaster: 5SP, I don't think it's 5SP, lets put 3SP for now. (estimate shaming) (End of Sprint) ScamMaster: Why can't you guys provide an accurate estimate we are always behind. (blaming) I know you have to put food in the table, but we know that you're a SCAM master if you don't understand what you're here for. (Unfortunately, based on a real situation)

@scrummasterinblack 2 жыл бұрын

Hahahaha 🤣

@bradwhiteau 2 жыл бұрын

Just to clarify something, I assume that in order for this to work the PBI's should be roughly the same size comparatively? Otherwise the overall simulation would be inaccurate? Or is the assumption that with enough history, the variance in PBI size would be taken into account?

@scrummasterinblack 2 жыл бұрын

It doesn't has to be equally the same size BUT the width of the bell curve will be wider and the forecast will not be as accurate.

@alexanderleanzabhnsdalen8847 3 ай бұрын

So then you have to end up doing some sort of sizing? Planning poker or any other type? The team has to have an idea if the items are too large and need to be split in smaller ones somehow. The team has to be very good in refining and having good quality stories and be able to split in similar sizes I would assume?

@g-ronnmendoza 2 жыл бұрын

Can we say that from the start, no need to have estimates since Monte Carlo simulation does ‘t look for story points in forecasting? How many sprints at least will this simulation be reliable to compute?

@scrummasterinblack 2 жыл бұрын

I once worked with a team who just jumped and go in the first three months just to have the data for Monte Carlo simulation. Monte Carlo simulation will be reliable as long as there is no changes in the team composition and as long as the team have a consistent slicing heuristics.