HeaderSIS.jpg

WRESSENCE Project Management

From IS480
Jump to navigation Jump to search
Team WRESSENCE

Schedule Management

Quality Management

Risk Management

Team WRESSENCE
Team WRESSENCE
Team WRESSENCE
Team WRESSENCE
Team WRESSENCE
Team WRESSENCE


Team WRESSENCE
Project Management


Schedule Management

Planned Schedule

Click here to download our detailed schedule plan.


Schedule Metric

Index (i) Impact Level Severity Action Plan
i < 0.5 Critical Task is completed much earlier than the estimated time frame. Action needs to be taken immediately. Project Manager will hold a meeting with the whole team to re-allocate manpower for ongoing tasks. New task may be assigned to the member for that iteration.
0.5 ≤ i < 0.75 High Task is completed earlier than the estimated time frame but the difference is still acceptable. Project Manager will re-evaluate abilities of the member in-charge of the task to better estimate time frame for future tasks allocated for this member.
0.75 ≤ i < 1.25 Neutral Schedule is on the right track and no action is required. Good estimation of schedule so no action is needed.
1.25 ≤ i ≤ 1.5 High Task is completed later than the estimated time frame but the difference is still acceptable. Project Manager will re-evaluate abilities of the member in-charge of the task to better estimate time frame for future tasks allocated for this member.
i > 1.5 Critical Task is completed much later than the estimated time frame. Action need to be taken immediately. Project Manager will call for an emergency team meeting to complete task as a team. Cause of the delay will be investigated by the Project Manager so that scheduling of future tasks and manpower allocation can be better estimated.


Click here to view a detailed summary of the schedule metric.

Back to Top



Quality Management

Bug Metric

Severity Level Description
Critical (10 Points) Bugs affect the other functionalities of the system and delay the progress of development. System crashes due to these bugs. Need to fix immediately.
Moderate (3 Points) Part of the non-critical functionalities are not working. Business logic affected.
Low (1 Point) User Interface-related issues and typo errors. These bugs do not affect the functionality of other development segment and not important.


Points During Iteration Action Plan
Points < 3 Assign a member to fix the bug only when there is buffer time.
3 ≤ Points ≤ 10 Pair up members to fix the bug during scheduled debugging slot.
Points > 10 Team to stop the tasks on hand. Project Manager to call for an emergency meeting to solve the bug as a team.


End of Iteration Points Action Plan
Points < 15 Quality of codes is good.
15 ≤ Points ≤ 35 Quality of codes is not up to standard and need to be monitored closely for the next iteration.
Points > 35 Quality of codes is bad and need to redefine requirement for good coding quality.


Click here to view a detailed summary of the bug metric.


Back to Top


Risk Management

Risk Metric


Risk Metric























Click here to view a detailed summary of the risk analysis.

Back to Top