Controlling differs from directing. When you have a finalized project plan that you're going forward with, and you are making sure that the deliverables you're creating meet the metrics you set down during requirements definition, you are controlling the project. For example, a piece of code that does a calculation should meet a success criterion that clearly indicates whether the code works as needed and expected. The controlling aspect of the project looks at metrics. When assessing the project, you might ask, "How well were the metrics formulated, and did they meet expectations?"

Don' t forget that during the planning stages you pinpointed the risks to the project—did any of those risks materialize while in the controlling phase? If so, how did you spot them and then deal with them? Risk assessment and response control is an important facet of any project.

Was this article helpful?

0 0

Post a comment