Difference between revisions of "IS480 Team wiki: 2013T1 Altitude/Final/Project Management"
Line 380: | Line 380: | ||
|- | |- | ||
| style="background: #C0C0C0"|<center>''' 1.'''</center> | | style="background: #C0C0C0"|<center>''' 1.'''</center> | ||
− | | | + | | Platform updates happening near project milestones |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
| Closer to final presentation date, we need to ensure our application is fully deployed and ready for demonstration | | Closer to final presentation date, we need to ensure our application is fully deployed and ready for demonstration | ||
| <center>High </center> | | <center>High </center> | ||
− | | | + | | We sought out the Client’s technical leads, and we communicated with their Senior Engineer based in Germany early via email to re-configure our platform to accommodate our project schedule. |
− | + | ||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
+ | |||
|} | |} | ||
Revision as of 00:32, 1 December 2013
Overview | Project Management | Documentation | |||
---|---|---|---|---|---|
Project Progress | Project Management | Quality of Project | Reflections |
---|
Project Management
Project Timeline
- As a Team, Altitude has completed :
- 12 sprints
- 168 days
- 4 hours per day
- 5 developers
- Calculation : (Number of days) * (Hours per day) * (Number of developers)
- Calculation : 168 * 4 * 5 = 3360
- Total hours 3360 man hours
Project Scope (Planned Vs Final)
Project Scope
|
---|
Latest Scope
Features | Status | Confidence Level (0-1) | Member In-Charge |
---|---|---|---|
Login | 100% developed and deployed | 1 | Justin |
Take in Requirements from RFP | 100% developed and deployed | 1 | Kenneth |
Generate Proposal | 100% developed and deployed | 1 | Max |
Download PDF | 100% developed and deployed | 1 | Max |
Design ontology | 100% developed and deployed | 1 | Kenneth |
Match Options | 100% developed and deployed | 1 | Kenneth |
Review and Edit Proposal | 100% developed and deployed | 1 | Max |
Recommended Options | 100% developed and deployed | 1 | Yao zong |
Modify Recommended Options | 100% developed and deployed | 1 | Max and Si min |
Save Current Input | 100% developed and deployed | 1 | Yao zong |
Furnish Proposal | 100% developed and deployed | 1 | Max |
Integration | 100% developed and deployed | 1 | Yao Zong and Kenneth |
Preserve Proposal | 100% developed and deployed | 1 | Yao Zong and Kenneth |
Edit Proposal | 100% developed and deployed | 1 | Max |
Project Schedule (Planned Vs Actual till Final)
Features changes
Before Mid-term presentation
Delay #1: Spring 2
Task delayed:Implementation of Take in requirements for proposal took longer than expected
Reason: The team needs more time to explore on the few unfamiliar technologies therefore the implementation was not able to complete on time
Delay #2: Spring 3
Task delayed: Delay in previous sprint
Reason: Due to the sprint delay in sprint 2, the team had a shorter period of time to finish match options.
Delay #3: Sprint 5
Task delayed: No prior knowledge on how ontology should be designed
Reason: The team spend long hours exploring on how ontology should be designed. After a session with our end users, we realized that we took a wrong approach to design our ontology.
After Mid-term presentation
Delay #4: Sprint 10
Task delayed:Affected by the change/update of Maven dependencies again
Reason: On 19th October, our client informed us that our application would break due to a maven dependencies updates and would requires a few hours to solve it. However, It was clearly not the case when we saw the changes later at night.
Schedule Metric
FORMULA:
Schedule Ratio = Remaining Time ÷ Remaining Effort |
---|
Schedule Ratio | Description | Response |
---|---|---|
> 1.2 | Project is ahead of schedule | Project Manager assigns tasks from next sprint to current sprint. |
Between 0.8 and 1.2 | Project is within schedule | No action is required for ratio of 1. Keep a look out when nearing below 1. |
< 0.8 | Project is behind schedule | Project Manager will reschedule tasks while the team will put in additional man hours for the week. In addition, the PM will need to identify root causes of delays by end of sprint, communicate with the team about solutions to the issues and inform client about the project status. |
The diagrams below show the burndown charts & schedule ratio charts of Sprint 8 - 12 since Midterms.
Number | Description | Links |
---|---|---|
1 | Schedule Metric Calculation | Schedule Metric Calculation Link |
2 | Schedule Metric Documentation | Schedule Metric Documentation for Sprint Number: |
Bug Metric
FORMULA:
Bug Ratio = (2X No. of low severity bugs) + (4X No. of medium severity bugs) + (10 X No. of high severity bugs) |
---|
Severity Score | Severity Level | Description |
---|---|---|
2 | Low | Cosmetic defects. Developed functions are functional, but at a sub optimum level |
4 | Medium | Defects that cripple a function |
10 | High | Defects that cripple more than 1 function |
Sprint Response
Bug Score Sum | Response |
---|---|
6 and below | Bugs are to be resolved at the end of the sprint. |
Between 7 and 9 | Resolve bugs that are medium severity within the sprint, else schedule the bugs to be resolved in future sprints. |
10 and above | Developer working on non-critical functions will assist the developer on the critical bug. |
Bugs Chart
No of Bugs Discovered (All Sprints)
Number of bugs (Sprints 8-12)
Number | Description | Links |
---|---|---|
1 | Bug Metric Calculation | Bug Metric Calculation Link |
2 | Bug Log |
Risk Management
Platform updates happening near project milestones | Closer to final presentation date, we need to ensure our application is fully deployed and ready for demonstration | We sought out the Client’s technical leads, and we communicated with their Senior Engineer based in Germany early via email to re-configure our platform to accommodate our project schedule. |
Number | Description | Links |
---|---|---|
1 | Risk Management Calculation | Risk Management Link |
Technical Complexity
The technical complexities of our tools employed are in the following descending order:
COMPLEXITY | DESCRIPTION |
---|---|
SAPUI5 |
|
Ontology Framework |
|
Ontology
Sublime :: Instantiating Individuals (Platform schema) | Sublime :: Instantiating Individuals (Application Schema) |
---|---|
|
Sublime :: Instantiating Individuals (Application Integration Schema) |
---|
Protege :: Creating class | Protege :: Drawing relationships |
---|---|
|
Protege :: Defining Attributes | Protege :: Instantiating individuals |
---|---|
|