Remember those metrics that you developed when you were busy writing the project s requirements? Now you can begin to use them. Suppose, for example, that you developed a requirement that when a user hits the Checkout button in an e-commerce site you re developing, the behind-the-scenes code will calculate the quantity for a given item times its price, plus the shipping rate for the items. A metric for this requirement would be that it accurately performs this calculation 100% of the time.
A fundamental function of good project managers involves frequently revisiting the requirements, measuring them against the metrics, and validating that they' re on track and complete.
Something to consider when developing tracking requirements metrics is your level of acceptance for a given requirement. Suppose, for example, that one of the requirements you 've developed is this: "When user clicks the Demographics button, the user will be presented with a pie-chart graphic that depicts a percentage separation calculated from the Student-T variable. This percentage can be within +/- 5% of actual." This metric allows for some flexibility in the acceptability of the requirement ' s outcome. Most requirements will have hard and fast metrics, but some might present an opportunity for leeway.
Was this article helpful?