[ Artifacts ]

There’s plenty of advice on how to lead better, how to manage a project better, how to manage risk, and many other ‘how to’s’ out there.

What is surprisingly lacking in the advice given, is what the artifacts of the task are, or should be.  By artifact, I mean records and documents. 

Managing risk? A risk register is an artifact.  Managing a project? There are plenty of project artifacts (budget, contract, schedule are just the  beginning).  But what should be clear is a standardised set of artifacts defining what is left behind (besides the successfully completed project output, of course).

Previous
Previous

[ Version Control ]

Next
Next

[ Database ]