HeaderSIS.jpg

IS480 Team wiki: 2012T2 Techbusterz Project Management

From IS480
Jump to navigation Jump to search
Techbusterz logo.png
Metrics Project Schedule Action Plan Risk Management



Metrics

Schedule Metric

x (days) = Actual Days - Planned Days

Interpretation of Metric

Days (x) Interpretation

Action Plan
x < 0 Early PM to track the total number of days ahead at the end of the iteration. If we are more than 5 days ahead of schedule, team may decide to explore additional functionalities or improve on the user interface.
0 <= x< 1 On time Keep up the good work.
1 <= x< 3 Late PM to shorten time allocated for the next iteration using the buffer days.
x =< 3 Very Late PM to understand the cause of the delay. PM to make use of buffer time from the next iteration to make up for the late days. PM may also choose to revise the schedule and remind the teams of the changes and risks involved. With the consensus of the team, PM may decide to drop functionalities in the even that all the buffer time is used up.


Bugs Metric

x (bug points) = Minor Bugs + Moderate Bugs + Severe Bugs

Interpretation of Metric

Rank in Importance Points(x) Description
Low 1 The system runs. However, the user interface has minor spelling errors and is not beautified.
Medium 5 The systems runs but some non-critical functionality not working.
High 10 The systems crashes or the system runs but core functionality not working.
Points Actions
x <= 5 Safe: Program does not require immediate attention. Bugs to be solved during coding session.
5 < x < 10 Caution: Program has issues that require fixing. Coders are to set up another session for debugging before the next iteration to prevent any delay
10 <= x Danger: Testers to inform PM immediately. PM to call for urgent meeting with entire team and declare Debugging Day. No buffer to be given as issues has to be solved immediately. Team to treat this day as main priority before proceeding to others.


Efficiency Metric

x (man hours) = Actual Man Hours - Planned Man Hours

Interpretation of Metric

Man Hours (x) Interpretation Action Plan
x < -4(lesser than -4) Very Early PM to reassess situation and find out the reason for early completion, understand the situation, re-plan man hours and allocate additional man hours if necessary.
-1 > x >= -4 (between -1 & -4) Early PM to plan and revise estimation to improve on accuracy.
-1 <= x <= 1 (between -1 & 1) On time Keep it up and continue to plan accurately
1 <= x <= 4 (between 1 & 4) Late PM to plan and revise estimation to improve on accuracy.
x > 4 (bigger than 4) Very Late PM to reassess situation and find out the reason for late completion. Understand the situation, re-plan and bring in extra manpower if necessary to minimize time waste.


Schedule


Click here to view detailed project schedule.

Milestone

Techbusterz graphicaltimeline.png


Techbusterz timelinenew.png




Action Plan

Iteration No. Affected Metric Metric Level
(High/Med/Low)
Cause Action Plan
Construction Iteration 6 Schedule Metric Red In Construction Iteration 6, we are supposed to integrate crawled data for our various categories such as Arty Farty, Local Culture, etc. However, our sponsor is not able to send us the crawled data on time due to some unforeseen circumstances. Therefore, the PM has to carry out the action plan according to the metric. PM has to reschedule plan and swap Iteration 7 and 6. Instead of working on the integrating of crawled data, our developers will work on the Facebook & Google integration
Construction Iteration 6 Bug Metric Red During our testing in Construction Iteration 6, our tester detected that the "Displaying of detail information of the place/shop is not working, thus hitting the score of 10. PM to immediately inform coders about this and declare bugging day. The bug was solved and everything returned back to normal


Techbusterz ProjectScheduleActionPlan.png

Risk Management

Types of Risk

S/N Risk Description Impact Level
(High/Med/Low)
Likelihood Impact on Objective
(High/Med/Low)
Mitigation Strategy Status

1

Project Management

1.1

  • Early estimation of Man Hours

High

High

  • Project will be delayed due to inaccurate planning
  • PM to plan buffer days to ensure higher accuracy of planning
  • PM to be constantly updated on progress by team mates

Mitigated

1.2

  • Unfamiliar with iOS coding

High

High

  • Project will be delayed due to longer learning phase
  • Have proper time management to plan for early research on technologies
  • Organize peer learning and knowledge sharing sessions

Mitigated

2

Client Management

2.1

  • Miscommunication with sponsor/client pertaining to project requirements and expectations

High

High

  • Unhealthy and relationship will sour, affecting team morale

Mitigated

2.2

  • Sever down

High

Low

  • Project slightly delayed due to application not able to load
  • Perform periodical check on sever status
  • Since our sever resides over at sponsor side, Tao will be the main person of contact if anything happens.

Mitigated

3

Team Management

3.1

  • Conflict arise among team members

Moderate

Low

  • Team efficiency dropped
  • PM to organize a "compromise" session to settle all conflicts ASAP

Risk Eliminated


Techbusterz risktable.png


Techbusterz SecondaryRole.png