HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T2 DaDa Achievers Project Management Project Metrics"

From IS480
Jump to navigation Jump to search
 
Line 78: Line 78:
  
 
[[Image:Schedule metrics iterations 1-17.PNG | 500px|]]
 
[[Image:Schedule metrics iterations 1-17.PNG | 500px|]]
 
===='''Individual Efficiency Metric'''====
 
 
 
'''Goal:''' To ensure that each team member’s skills are utilized which leads to greater team productivity. This in turns leads to complementing the project planning and task completion rate.
 
 
'''Frequency of measurement:''' At the end of every iteration/phase
 
 
Formula of individual productivity coefficient: <br>
 
• Individual EC = Actual duration of allocated task/ planned allocated duration of each task to each member.<br>
 
 
• Average Individual AEC = Sum of EC of each team member / number of tasks allocated  <br>
 
 
 
{| class="wikitable"
 
|-
 
! Average Individual Efficiency Coefficient (AEC) Score
 
! Observation
 
! Action Plan
 
|-
 
|
 
AEC < 1
 
|
 
Very efficient and finishes tasks slightly ahead of time.
 
|
 
Start next task earlier or PM to allocate lesser hours for subsequent tasks.
 
|-
 
|
 
AEC = 1
 
|
 
Task duration planning is accurate.
 
|
 
None required. Team member is efficient in completing his/her task on time.
 
|-
 
|
 
1 < AEC ≤ 2
 
|
 
Team member is a slightly behind estimated schedule.
 
|
 
Acceptable. An additional 12 hours are given to the member to finish up the task.
 
|-
 
|
 
2 < AEC
 
|
 
Team member is too far behind schedule or PM has estimated too short a duration for the allocated tasks.
 
|
 
Bad. The team member had exceeded the planned duration for more than 35%. <br> The project manager will either assign another teammate to assist in finishing the task or to arrange for an ad-hoc meeting to solve the problem.
 
|-
 
|}
 
 
</div>
 
</div>
  

Latest revision as of 02:48, 19 April 2013


Home Project Overview Project Management Project Documentation Project Progress Summary Reflections
Project Schedule Project Metrics Project Risks Technologies Used


Project Metrics

Schedule Metric

Goal: We want to improve upon overall project task completion time
Question: How accurate are my schedule estimates?
Metric Score (X): Actual Duration / Estimated (Planned) Duration
Usage: Refer to table below

Metric Score Action Plan
X < 0.7
Project is way ahead of schedule.
PM to decide whether to revisit project scope, and explore more functions to include.
0.7 ≤ X < 0.9
Project is slightly ahead of schedule.
No re-scoping necessary. Channel excess time into testing.
0.9 ≤ X ≤ 1.1
Project is on schedule.
1.1 < X ≤ 1.3
Project is behind schedule.
PM to work with team to redeploy and possibly re-adjust schedule to increase length of iteration.
X < 1.3
Project is severely behind schedule.
PM to communicate problems for delay to stakeholders, and if necessary, discuss and agree upon a reduction in project scope.

Schedule metrics iterations 1-17.PNG

Bug Metric

Goal: We want to improve the software quality of our product
Question: What are the bugs that occur during development, what are their impact and how will they affect the overall project schedule?
Frequencey of measurement: At the end of every iteration
Bug Severity Index (BSI) Total = 1 x num (low) + 5 x num (high) + 10 x num (critical)

Severity Description

Low Impact (1 points)

Occurs due to typo error or minor code errors with the system logic.

High Impact (5 points)

The inventory management and e-commerce system runs but certain functions are broken.

Critical Impact(10 points)

The server or database is unstable and the e-commerce site is down

Action plan

DaDaBugMetrics.GIF
BSI Action
Points =< 5 Fix during development time only.
5 < Points< 10 PM to assign other team members to help out in debugging.
Points>=10

The current iteration will be put on hold. The PM will need to make adjustments to the project schedule
The PM will also have to call for an urgent meeting with the team to reassess severity and work out an solution.