Difference between revisions of "IS480 Team wiki: 2012T2 DaDa Achievers Project Management"
Line 114: | Line 114: | ||
<div style="border-left: #585858 solid 12px; padding: 0px 30px 0px 18px; "> | <div style="border-left: #585858 solid 12px; padding: 0px 30px 0px 18px; "> | ||
− | [[Image: | + | [[Image:DaDaScheduleMetricsnew.GIF | 500px|]] |
===='''Individual Efficiency Metric'''==== | ===='''Individual Efficiency Metric'''==== |
Revision as of 12:51, 21 February 2013
Welcome to DaDa Achievers FYP Wiki!
|
Home | Project Overview | Project Management | Project Documentation | Project Progress Summary | Reflections |
Contents
Project Management
Project Schedule
Iteration No. | Description | Progress (%) |
---|---|---|
1 | Authorization, add/delete/update product and show product status | 100% |
2 | Barcode creation and scanning | 60% |
3 | Inventory tracking | 100% |
4 | Online ordering, order request and order tracking | 100% |
5 | Update order and process payment | 100% |
6 | Inventory Management System and E-commerce Internal Testing | 100% |
7 | Customer Records Management | 90% |
8 | Usability Testing 1 | 100% |
9 | Import/Export wizard for excel | 100% |
Detailed project schedule with comparison between planned and actual duration can be found over the link: Detailed Project Schedule-DaDa Achievers
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 |
|
0.7 ≤ X < 0.9 |
|
0.9 ≤ X ≤ 1.1 |
|
1.1 < X ≤ 1.3 |
|
X < 1.3 |
|
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:
• Individual EC = Actual duration of allocated task/ planned allocated duration of each task to each member.
• Average Individual AEC = Sum of EC of each team member / number of tasks allocated
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%. |
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
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 |
Project Risks
Classification | Risk Description | Impact | Probability | Mitigation Strategy and Triggers (if applicable) | Status, and Remarks (if any) |
---|---|---|---|---|---|
Technology | Unfamiliarity of Flash technology for development of the Ring Customization tool | High | High | Allocate time for adequate learning as well as approaching people with relevant experience, if possible, for guidance. | Risk have not occurred yet |
Technical & Learning Risk | Delay of prototype development due to technical challenge | High | Medium | Trigger: Schedule Delay Initiate research on any technologies that would be easier to implement, and if possible, produce a prototype to confirm the technology switch. |
Controlled The team plans to firm up technology decisions via working prototypes by week 2. |
Technology | Over-reliance on 3rd Party API such as PhoneGap and E-nets | High | Medium | Conduct proper research and seek alternatives | Followed Mitigation Strategy: Implemented Paypal instead of E-nets |
Project Management | Client is resistant to change of business processes and adoption of new technologies | Medium | Low | Conduct thorough analysis and provide a concise solution. Walk client through the needs for such changes. | Controlled We have met up with the client several times to review the proposed solution and changes. |
Project Management | Scope creep: Client requests to add on functions above and beyond what was agreed upon | Medium | Low | Perform thorough requirements analysis and create a baseline. When change is required, PM will meet with the team and compare against baseline and project schedule to see if change can be allowed. | Risk have not occurred yet |
Resolved Risks |