Could anybody indicate some metrics for monitor and control the advance on activities/products asociated with Requirements Engineering ? ( Currently I have: number of developed Use Cases vs Estimated number of developed subflows in UC vs Estimated ) Saving Changes...
Michael WoodProject Manager / Business Analyst / Business Process Improvement Guru| Independent ContractorGig Harbor, Wa, United States
Carlos, in my experience the requirements of an IT project fall into two basic groups. First there are the requirements of the project as they relate to achieving the benefits and improvements to the organizations stakeholders. Second are the physical requirements that take the form of system inputs, processes and outputs. The metrics for the first type of requirements should be defined by the project's goals. The trick here is to relate how the second type of requirements meet the first. Metrics for the second form of requirements are typcially based on demonstrating through documentation what screens, reports and periodic processes will appear and function. These are easy to measure because they can be inspected. The metrics related to how these defliverables of the system achieve the business case is a bit more essoteric and requires that a consnsus be achieved that confirms that what is being built will indeed satisfy stakeholder expectations. Saving Changes...
