Skip to main content

Agility Path: "Cost of Delay"

Last post 11:18 am September 24, 2013 by Ian Mitchell
2 replies
05:54 am September 24, 2013

Does anyone know if "Cost of Delay" is a recognized measure in Agility Path? It seems to go against the spirit of measuring actuals, and is a clear example of how forecasts can become subject to commoditization. As such it is arguably unagile.

Nevertheless, Product Owners find it useful for Product Backlog prioritization and release management...many do it informally even if they don't know the term. What position is being taken on this?


10:59 am September 24, 2013

Cost of Delay is not one of the measures used in Agility Path. We focus on value delivered to the organization by increased organizational agility. If I reverse "cost of delay" I would get something like "value of speed to market". Some of our metrics get at that: cycle time, release frequency, revenue, customer satisfaction.


11:18 am September 24, 2013

That's a good explanation. Thanks.


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.