HeaderSIS.jpg

IS480 Team wiki: 2013T2 Excelente Metrics

From IS480
Jump to navigation Jump to search

option

Home About Us Project Overview Project Management Project Documentation


Project Schedule Metrics Risk Management


Schedule Metrics

Schedule Ratio Resources Description Action Plan
< 0.8
Extra Resources were allocated
  • Project is ahead of schedule.
  • Team is able to complete tasks faster than allocated time.
  • Metric values that fall within this category is optimal.
  • Project Manager to understand why progress is faster than expected
  • Project Manager to review schedule and make better estimates for tasks that are similar in nature.
  • 0.8 - 1.2
    Adequate Resources were allocated
  • Project is on schedule.
  • Team is able to complete tasks within allocated time.
  • Metric values that fall within this category is healthy and acceptable
  • If ratio is 0.8-1, proceed as per normal.
  • If ratio is 1-1.2, Project Manager to understand what caused the slight delay.
  • Project Manager to work with Business Analyst to look for ways to improve processes further to maximise resources.
  • > 1.2
    Insufficient Resources were allocated
  • Project is behind schedule.
  • Team is unable to complete tasks within deadline.
  • Metric values that fall within this category is unacceptable and should be classified within the "danger zone".
  • Project Manager to understand cause of delay and rectify problem as soon as possible.

  • Schedule Metric By Iteration

    Excelente MetricbyIter Final.png

    Bug Metrics

    Severity Zone Legend Description Required Resources
    Low Impact

    [1 point]

    Low
  • Bug is caused by carelessness and can be solved easily.
  • Progress of Project is not affected by discovery of bug.
  • Developer(s): 1-2 Man Hours
    High Impact

    [5 points]

    High
  • Bug is caused by logic flaws/errors and can be solved with sufficient thought.
  • Progress of Project is affected by discovery of bug.
  • Developer(s): 3-6 Man Hours
    Project Manager: 1 Man Hour


    Critical Impact

    [10 points]

    Critical
  • Bug is caused by serious errors which causes application to crash or be unusable.
  • Reason behind bug is difficult to discover.
  • Progress of Project is halted until bug is completely resolved.
  • Developer(s): 7 and above Man Hours
    Project Manager: 2 and above Man Hours


    Bug Points Mitigation Plan Criticality
    <= 20
  • Update Bug Metrics accordingly
  • Sovle errors within iteration debugging session.
  • Proced with planned schedule.
  • If number of Critical Bugs >1, follow Mitigation Plan where Bug Points is 20-40


    20 - 40
  • Update Bug Metrics accordingly
  • Developers to inform Project Manager if planned debugging session is insufficient to solve the errors.
  • Project Manager to review schedule.
  • If number of Critical Bugs > 3, follow Mitigation Plan where Bug Points is >=41

    >= 41
  • Update Bug Metrics accordingly
  • Critical Delay in Project Progress expected.
  • Project Manager to gather team for discussion and review Project Scope.
  • Project Manager to review schedule.
  • If external assistance is required, seek help immediately.
  • If number of Critical Bugs > 3, follow Mitigation Plan where Bug Points is >=41


    Bug Metric By Iteration


    option