Enable your engineers to make the right decisions with the Cost of Delay

Generally, we want to know how long the task will take and how much effort will be needed. However, we always get it wrong, don’t we? We’ll investigate why all projects fail and look into musings of one of the Agile fathers, Donald G. Reinertsen, and his approach to the so-called Cost of Delay.

Generally, we want to control things. We want to know how long things will take and how much effort will be needed. There are ways how to achieve that - we lock architect in a room and he comes with results. He’s the expert! Just for any case, we put 20% contingency on top to be safe. And then negotiate down the price to fit the budget. Later PM makes a plan what to do in what order, calls it project and the team starts to work. Simple, isn’t it? That’s what everyone does, so it should be correct… We’ll look into classical estimation and planning techniques and why they don’t work. We’ll investigate why all projects fail and look into musings of one of the Agile fathers, Donald G. Reinertsen, and his approach to the so-called Cost of Delay. We need to talk about projects versus products as well. Finally, You’ll get a chance to try this out by yourself and have some fun!

Screen and the internet are needed. That’s all.