Difference between revisions of "IS480 Team wiki: 2014T1 Chocolicious Proj Management"
Line 65: | Line 65: | ||
<li>Develop diagrams</li> | <li>Develop diagrams</li> | ||
</ul> | </ul> | ||
− | + | <center> | |
− | < | + | {| style="width:100%" |
− | + | ! bgcolor="#FF6600"|Proposal deadline | |
− | </ | + | |} |
+ | </center> | ||
<b>Coding Tasks</b><br> | <b>Coding Tasks</b><br> | ||
Line 192: | Line 193: | ||
<li>Update wiki page & project progress</li> | <li>Update wiki page & project progress</li> | ||
</ul> | </ul> | ||
− | < | + | <center> |
− | + | {| style="width:100%" | |
− | </ | + | ! bgcolor="#FF6600"|Acceptance Presentation |
+ | |} | ||
+ | </center> | ||
|Acceptance Presentation<br><b>14 Aug 2014</b> | |Acceptance Presentation<br><b>14 Aug 2014</b> | ||
|1 Aug 2014 | |1 Aug 2014 | ||
Line 334: | Line 337: | ||
<li>Update wiki page & project progress</li> | <li>Update wiki page & project progress</li> | ||
</ul> | </ul> | ||
− | < | + | <center> |
− | + | {| style="width:100%" | |
− | + | ! bgcolor="#FF6600"|Mid Term Presentation | |
+ | |} | ||
+ | </center> | ||
+ | |||
|Mid Term Presentation<br><b>10 Oct 2014</b> | |Mid Term Presentation<br><b>10 Oct 2014</b> | ||
|26 Sep 2014 | |26 Sep 2014 | ||
Line 431: | Line 437: | ||
<li>Debugging</li> | <li>Debugging</li> | ||
</ul> | </ul> | ||
− | + | <center> | |
− | < | + | {| style="width:100%" |
− | + | ! bgcolor="#FF6600"|Poster Day | |
− | </ | + | |} |
+ | </center> | ||
<b>Documentation</b><br> | <b>Documentation</b><br> | ||
Line 462: | Line 469: | ||
<li>Final round of testing</li> | <li>Final round of testing</li> | ||
</ul> | </ul> | ||
− | + | ||
− | < | + | <center> |
− | + | {| style="width:100%" | |
− | + | ! bgcolor="#FF6600"|Final Presentation<br>Poster Day | |
− | </ | + | |} |
+ | </center> | ||
<b>Documentation</b><br> | <b>Documentation</b><br> |
Revision as of 15:17, 10 June 2014
|
Our Team
Time Line
Schedule
Planned | Actual | ||||||
---|---|---|---|---|---|---|---|
Iter | Tasks | Milestone | Start | End | Start | End | |
1 | Preparation
Project Management
Technical Requirements
|
23 May 2014 | 12 Jun 2014 | 23 May 2014 | |||
2 | Management & Documentation
Coding Tasks
Testing
Documentation
|
Proposal 18 Jun 2014 |
13 Jun 2014 | 26 Jun 2014 | |||
3 | Coding Tasks
Testing
Management & Documentation
|
27 Jun 2014 | 10 Jul 2014 | ||||
4 | Management
Coding Tasks
Testing
Documentation
|
11 Jul 2014 | 31 Jul 2014 | ||||
5 | Management
Coding Tasks
Testing
Documentation
|
Acceptance Presentation 14 Aug 2014 |
1 Aug 2014 | 14 Aug 2014 | |||
6 | Management
Coding Tasks
Testing
Documentation
|
15 Aug 2014 | 28 Aug 2014 | ||||
7 | Management
Coding Tasks
Testing
Documentation
|
29 Aug 2014 | 11 Sep 2014 | ||||
8 | Management
Coding Tasks
Testing
Documentation
|
12 Sep 2014 | 25 Sep 2014 | ||||
9 |
Mid term preparation Management
Coding Tasks
Testing
Documentation
|
Mid Term Presentation 10 Oct 2014 |
26 Sep 2014 | 10 Oct 2014 | |||
10 | Management
Coding Tasks
Testing
Documentation
|
11 Oct 2014 | 23 Oct 2014 | ||||
11 | Management
Coding Tasks
Testing
Documentation
|
24 Oct 2014 | 6 Nov 2014 | ||||
12 |
Prepare for Poster Day Management
Coding Tasks
Testing
Documentation
|
Poster Day 10 Nov 2014 |
7 Nov 2014 | 20 Nov 2014 | |||
13 |
Prepare for Final Presentation Management
Testing
Documentation
|
Final Presentation 24 Nov - 2 Dec 2014 Poster Day 3 Dec 2014 |
21 Nov 2014 | 3 Dec 2014 |
Risks & Constraints
Risk Table
Probability | 1-low | 2-medium | 3-high |
---|---|---|---|
Effect | 1-low | 2-medium | 3-high |
Priority | Higher number more important |
Project Risk | ||||
---|---|---|---|---|
Possible Risk | Probability (1-3) |
Effects (1-3) |
Priority (P x E) |
Strategy |
Medical Certificate or Leave Of Absence MC or LOA might be inevitable due to personal reason, such as falling sick due to over commitment or applying of LOA due to unforeseen circumstances. |
Low (1) | Medium (2) | 2 | Risk mitigation Reorganize team such that everyone understands each other’s job. |
Minimal knowledge about new languages We have no prior knowledge on these subjects and thus have to find out through reading. We would be only receiving little help from our supervisor or friends thus we have to do our own research to better understand the concept of these subjects. |
Medium (2) | Medium (2) | 4 | Risk Contingency Source for other resources that might be able to help us better understand the topic |
Minimal knowledge on accounting related software or tools We have no knowledge on accounting software or accounting related tools. |
Medium (2) | Medium (2) | 4 | Risk Contingency Source for tutorials that might be able to help us better understand the tools or software. |
Understanding of Software Tutorial Tutorials found are mainly not meant for starters; hence understanding of the tutorial can be a problem as it might be time consuming. |
Medium (2) | Low (1) | 2 | Risk Contingency Source for other tutorials that might be able to help us better understand how to use the software |
Requirements Changes We might make changes to the project’s requirement so to better fit the objective, which will result in our work being delayed. |
Medium (2) | High (3) | 6 | Risk mitigation Reorganize team such that everyone understands each other’s job. |
Personal Reasons Due to very personal reason such as family day, birthday or functions that we must attend, we might have to leave earlier than expected; this might drag down the overall performance of the team. |
Low (1) | Low (1) | 1 | Risk Avoidance The project is our main priority hence it is important that we put the project above all else. |
Hardware Unavailability Our laptop machines where the programs are installed might not be working or might be faulty and thus we are unable to carry out our task as accordingly. |
Low (1) | High (3) | 3 | Risk Contingency Ensure that other companies will be able to back up for the essential hardware. |
Incomplete Tasks If anyone were to not complete the designated task on time it will drag down the rest, this will then result in incomplete submission when it’s due. |
Low (1) | High (3) | 3 | Risk Avoidance We will be working on our project in school during the weekdays and we will also be working from home during the weekends so that we are able to fulfil our task. |
Miscommunication Due to different ideas generated by each members not all might agree thus leading to communication problems, such as getting of the wrong ideas across and unable to make up final decision. |
Low (1) | Medium (2) | 2 | Risk Mitigation Have more discussion among the team, so to ensure that the final decision is agreeable by all the team members. |
Work Efficiency Each of the members work at a different pace thus accommodating each and every one might slow down the process. Task might not be completed in time, due to the large work scope. |
Medium (2) | Medium (3) | 6 | Risk Avoidance Risk Avoidance Work together in the lab so to avoid slowing down the process for the other group members. |
Technical Risk | ||||
---|---|---|---|---|
Possible Risk | Probability (1-3) |
Effects (1-3) |
Priority (P x E) |
Strategy |
Defective Components Lab machines might be faulty which result in us not being able to fulfil our task. |
Low (1) | High (3) | 3 | Risk Avoidance Replace faulty components or get help from IT HELP DESK. |
Data Loss Thumb drive or hard disk might be corrupted and is unable to retrieve the information. |
Low (1) | High (3) | 3 | Risk Contingency Have backup copies of our work with each and every one in the team. |
Business Risk | ||||
---|---|---|---|---|
Possible Risk | Probability (1-3) |
Effects (1-3) |
Priority (P x E) |
Strategy |
Product Competition Different service or products similar to ours hence we have to make sure that our service is competitive so that we can meet the expected standard of us. |
Low (1) | High (3) | 3 | Risk Contingency Ensure that our product is made better than our competitors. |