In built environment engineering (bridge, building, etc.) - Work is a function of Scope. Further the "functions" are relatively well understood based on known materials, methods and calibrated based on well recorded past examples (e.g. underpinning QS). So the project management is focused on the cost, effort, time, materials etc. needed to undertake the work.
W=f(S)
Cost = f1(W, Materials Cost, Labour Cost)
Time = f2(W, Material availability, Labour availability, Dependencies)
Risk = f3(W)
S=f(W)
Which is why the traditional methods of understanding cost, time and risk fail.
Further many of the traditional things done with advanced project planning e.g. critical path and complex task scheduling, resource levelling, etc.) just don't make sense when the function for converting Work to Time isn't well enough calibrated and the dependencies between tasks (and the components produced by them) are not fully understood.
What is needed mostly is a more sophisticated way of understanding Scope. And changes to Scope as it emerges (i.e. either through elaboration of discovery of omissions).
This understand must be shared and most criticality must understood by key stakeholders such as the funder(s), the user(s), etc. NOT just the builders.
No comments:
Post a Comment