Difference between revisions of "IS480 Team wiki: 2012T2 Viaxeiros Project Management"
Line 99: | Line 99: | ||
Each members are allocated with a few functions to complete. The schedule will then follow this metric: | Each members are allocated with a few functions to complete. The schedule will then follow this metric: | ||
− | [[Image:ScheduleMetric.jpg| | + | [[Image:ScheduleMetric.jpg|450px]] |
This metric will be tied to an action plan as follows: | This metric will be tied to an action plan as follows: | ||
− | [[Image:ScheduleActionPlan.jpg| | + | [[Image:ScheduleActionPlan.jpg|550px]] |
'''Bug Metric''' | '''Bug Metric''' | ||
+ | |||
+ | To manage the quality of the work, a bug metric will be used with the following formula: | ||
+ | |||
+ | [[Image:Bug Metric.jpg|450px]] | ||
'''Work Stress Metric''' | '''Work Stress Metric''' | ||
+ | In order to make sure each members are able to cope with their current workload, each members have to fill in their stress percentage based on the following table: | ||
+ | |||
+ | [[Image:Workload table.jpg|550px]] | ||
Revision as of 10:04, 14 October 2012
Welcome to Viaxeiros FYP Wiki Page
Home | Team Viaxeiros | Project Overview | Application Development | Project Management | Project Documentation | Resources |
Framework
Agile Unified Process Adapted from the Rational Unified Process (RUP), Agile Unified Process (AUP) provides a simplified framework catering primarily for companies with an agile environment. Documentations are prepared to be "barely just good enough" to enable the flexibility required in an agile process.The process is broken down into 4 phases : Inception, Elaboration, Construction and Transition.
In AUP, iterations tend to be small and many. In our team, each iterations spans for 3 weeks.
Due to the agile process, changes to the requirements of the projects are rapid and regular. In this case, it is necessary to track and manage changes of the sponsors. Our team implements a change request log that tracks the changes sponsors wants to have. As a team, we will decide the importance of this change and hence change our schedule accordingly.
As part of the request of the sponsor, the native application has to be deployed to Google PlayStore. However, the first deployment will take a much longer time than that of subsequent deployment as multiple testing. This concept is similar to the AUP. |
Milestones
Text here |
Schedule
Text here |
Metrics
Schedule Metric Each members are allocated with a few functions to complete. The schedule will then follow this metric:
To manage the quality of the work, a bug metric will be used with the following formula:
In order to make sure each members are able to cope with their current workload, each members have to fill in their stress percentage based on the following table:
|
Risk Analysis
In order to manage the probable risk involved in the project, our group takes into account 2 variables: Impact and Likelihood. Based on the criteria mentioned below, the risk rate for each risk is accessed and a mitigation cum action plan is created.
Impact High - Chances of the occurrence happening is almost regular (very high) Moderate - Chances of the occurrence happening is irregular (sometimes) Low - Chances of the occurrence happening is seldom (very little)
High - The occurrence has a very great detrimental effect on project Moderate - The occurrence has a significant effect on the project Low - The occurrence has a limited effect on the project
|