Evidence Based Management - trying to understand proposed metrics

Last post 03:00 am August 7, 2020 by Ian Mitchell

1 reply

11:41 am August 6, 2020

Hi,

I'm about to propose EBM or at least part of it to my organisation in order to start discussions about actual value of our products. Also I try to start decision-making based on something more than gut feeling or loudest voice.

However there's thing I struggle to understand. What's the difference between cycle time, lead time and time to learn (metrics proposed at the end)? Cycle time is the shortest period (between start of development team work and release), lead time stretches it from the left (if we would be using some timeline) to include some plannings, analysis, discussions etc and time-to-learn stretches it to the right to include what's happening after the release?

I'll be happy to discuss that!

Ian Mitchell

03:00 am August 7, 2020

For empirical process control to be most effective, my advice is that there ought to be as little difference as possible between the measures you refer to.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.