The completion and success criteria you formulated when you were developing the requirements metrics will now come into play. Before deciding that the project should now be officially closed out, you should examine the requirements' success criteria to make sure you've met the mark in all ways. Dor example, suppose that you stipulated as a measure of a requirement' s success that you would install eight servers in eight different geographic locations and validate that each can communicate with the others 100 percent of the time (barring problems with WAN circuits, of course). By fulfilling the requirement and fully testing it, you have validated that the requirement has been successfully completed.
Your completion metrics can be (but don't necessarily have to be) different than your success metrics. Success metrics ask, "How do I know when I've successfully completed this requirement?" Completion metrics ask, "How do I know when I' ve successfully completed the project?" Once all requirements are completed according to your success metrics, then you potentially say that the project is done.
Note Larger projects always define completion and success criteria;
smaller projects don't necessarily need that kind of detail.
Evaluate both sets of metrics to make sure that you can truthfully say the project is over. Then move the project into the closing phase (called the ending phase in PACE). When the technical tasks have been completed and the project ' s products and results have been produced, the project has successfully concluded.
Was this article helpful?