It Isn't what you Know that Counts, It's what you can Prove
- pvaughan30
- Mar 20
- 1 min read
As simple as this may sound, there is a fair degree of effort that needs to go into the actions necessary to attain this.
Record keeping is king in this regard and the possibility of complacency setting in is the one danger that needs to be avoided wherever possible.
Repetition of inputs at regular times and in regular formats such that any one person can conduct the same action even if the original author is indisposed is desirable.
Ultimately when one looks at the vast array of documentation that has been amassed the hope is - and this will seem counter-intuitive - that there will never be any need to review the same presupposing the Project is completed successfully without disputes about time or cost.
Pre-planning of what is to be accumulated during the day-to-day workings should be established and maintained.
In that regard, the use of junior members of staff is preferred as it provides them with a grounding in what is to be considered as relevant and also does not over-burden the more senior members with relatively mundane tasks to the detriment of the more urgent ones that transpire at inopportune times.
Collating of data should also be done in such a manner that the data therein can be readily abstracted and presented to show meaningful renditions of progress and/or lack thereof.
Comments