[{"_1":2,"_48":-5,"_49":-5},"loaderData",{"_3":4,"_10":11,"_46":-5,"_47":-5},"root",{"_5":-5,"_6":-5,"_7":-5,"_8":9},"user","shoppingCartId","toast","locale","en","routes/_store+/_readers+/email_author.$slug/route",{"_12":13,"_45":-5},"book",{"_14":15,"_16":17,"_18":19,"_20":21,"_22":23,"_24":25},"id","Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6Qm9va1Byb2R1Y3QvMTE4NTQ","title","Diving For Hidden Treasures","state","published","contactAuthorMethod","email","aboutText","

Does your organization use estimation to value and rank projects in the project portfolio? Except for the shortest projects, estimation is often wrong. With incorrect estimates, the projects don't return the value you expected when you wanted. How can you finish projects in time to realize their potential value?

Instead of estimation, consider using the cost of delay to evaluate and rank projects. Cost of Delay accounts for ways projects get stuck. You've probably seen some typical Costs of Delay:

Multitasking
Other projects missing their expected release dates
Work queuing behind experts
Excessive attention to code cleanliness
Management indecision

Once you know about the Cost of Delay, you can decide what to do about it. You can stop multitasking. You can eliminate the need for experts. You can reduce the number of projects and features in progress. You can use the cost of delay to rank projects and work in your organization. Learn to use the Cost of Delay to make better decisions for your project, program, or project portfolio.

","authors",[26,39],{"_14":27,"_28":29,"_5":30},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci8xMjM3OA","name","Jutta Eckstein",{"_31":32},"avatar",{"_33":34,"_35":36,"_37":38},"url","https://d308did4coypzi.cloudfront.net/avatars/57975/medium/Jutta-OOP.jpg?1607000703","styleName","medium","exists",true,{"_14":40,"_28":41,"_5":42},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci8xMjM3OQ","Johanna Rothman",{"_31":43},{"_33":44,"_35":36,"_37":38},"https://d308did4coypzi.cloudfront.net/avatars/4167/medium/JRsmall.png?1607562128","currentUser","routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

Email the authors