Define Metrics ? Explain about process and project metrics?

Metrics:  IEEE defines metric as 'a quantitative measure of the degree to which a system, component, or process possesses a given attribute.' The goal of software metrics is to identify and control essential parameters that affect software development.

Process Metrics:
·        Private process metrics (e.g. defect rates by individual or module) are only known to by the individual or team concerned.
·        Public process metrics enable organizations to make strategic changes to improve the software process.
·        Metrics should not be used to evaluate the performance of individuals.
·        Statistical software process improvement helps and organization to discover where they are strong and where are week.

Project Metrics:
·        A software team can use software project metrics to adapt project workflow and technical activities.
·        Project metrics are used to avoid development schedule delays, to mitigate potential risks, and to assess product quality on an on-going basis.
·        Every project should measure its inputs (resources), outputs (deliverables), and results (effectiveness of deliverables).


Different project management metrics can be defined based on a project’s objective and complexity.
  1.  Productivity – This metric allows project managers to assess the utilization of resources. It compares the total effort to the budgeted effort, which has a direct impact on the bottom line. Delays in the timeline, underperformance by staff or vendor and unavoidable circumstances can all impact the productivity metric.
  2.  Scope of Work – A project’s scope is typically established right up front, but changes and additions can derail even the best project manager’s efforts. Tracking change requests is necessary, to control them and keep the project on time and budget.
  3.  Quality and Satisfaction – Quality assurance is a truly customer-focused metric. Assuring low defects throughout the project, as well as a quality deliverable at its end, should be part of every project. Catching defects early can also help prevent the entire project from losing focus and failing.
  4.  Cost – Measuring how costs are managed is often critical to a project’s success. Cost management is related to other variables, such as quality, scope and productivity, so if it varies above or below projections, the project can suffer. Ideally, cost is closely monitored throughout the project so if costs rise unexpectedly, variables such as scope or time are adjusted and the project can still achieve its objectives.

  5.  Gross Margin – Typically, a project’s ultimate goal is to contribute to the organization by increasing profits. The gross margin is the difference between total income achieved and total costs spent on the project. A project should have a target gross margin established in the planning stages, and it should be measured throughout. Project managers who achieve or exceed target gross margins are often extremely valuable.

Related

Software engineering 7770223945317867676

Post a Comment

emo-but-icon

item