A few days ago, I published an introduction to Cost of Delay over on the LeadingAgile blog. I asked some of my colleagues to check my numbers because the one thing I've noticed, people can be pretty unforgiving with spelling and math errors. The interest and response from both my colleagues and readers has been really positive. What I demonstrated in the blog post is, surprisingly, doing the most valuable feature first in your portfolio backlog is not always the best economic decision. Next time you prioritize your portfolio, do not just try to maximize value delivered. Limit your cost of delay. - See more at: http://www.leadingagile.com/2015/06/an-introduction-to-cost-of-delay/#sthash.ODrAFTyO.dpuf

An Introduction to Cost of Delay http://t.co/uDCHt115Ra #Agile

— Derek Huether (@derekhuether) June 11, 2015