Difference between revisions of "IS480 Team wiki: 2014T1 AT Co JR RISKS"
Jump to navigation
Jump to search
(10 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | |||
{| style="background-color:white; color:black; height: 90px" width="100%" valign="top" border="0" cellpadding="200"| | {| style="background-color:white; color:black; height: 90px" width="100%" valign="top" border="0" cellpadding="200"| | ||
Line 30: | Line 29: | ||
− | |||
+ | =<div style="font-size:100%; text-align:center; background-color: LightSeaGreen; color: white; width: 1000px ; padding-left: 10px; padding-bottom: 10px; padding-top: 10px"><font face = "century gothic" color="white"> Risks & Mitigation </font> </div><br/>= | ||
+ | <center> | ||
[[File:ATNCOJR Metrics.001.jpg|800px|center]] | [[File:ATNCOJR Metrics.001.jpg|800px|center]] | ||
Line 288: | Line 288: | ||
− | <div style="font-size: | + | =<div style="font-size:100%; background-color: LightSeaGreen; color: white; width: 1000px ; padding-left: 10px; padding-bottom: 10px; padding-top: 10px"><font face = "century gothic" color="white"> Risks & Mitigation (Acceptance) </font> </div><br/>= |
− | {| | + | {| class="wikitable" style="text-align: center; height:80px; width: 90%; font-size:100%;" |
+ | ! scope="col" width="300" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Type of Risk</font> | ||
+ | ! scope="col" width="350" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Risk Description</font> | ||
+ | ! scope="col" width="150" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Risk Level</font> | ||
+ | ! scope="col" width="350" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Mitigation<br></font> | ||
+ | |-!scope="row" style="background-color: LightSlateGray"| | ||
|- | |- | ||
− | |||
− | |- align = "left" | + | |- |
+ | |style="text-align: center; background-color: white"| | ||
+ | Project Management | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :Unexpected absence of team members | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | High | ||
+ | |style="text-align: left; background-color: white"| | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
*Assistant of the task owner will take over the task on his or her behalf | *Assistant of the task owner will take over the task on his or her behalf | ||
*Review on roles and capabilities | *Review on roles and capabilities | ||
Line 320: | Line 314: | ||
|- | |- | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | Project Management | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :Changes in business concept leading to changes in system requirements | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | Medium | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | *Conducted business and competitor analysis for sponsor | ||
+ | *Use prototypes were used for discussion during sponsor meeting | ||
+ | |- | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | Design and Development | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :Steep learning curve when using new language or frameworks | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | Medium | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | *The team has performed extensive research and practice on the technologies | ||
+ | *Knowledge sharing sessions were conducted | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
+ | =<div style="font-size:100%; background-color: LightSeaGreen; color: white; width: 1000px ; padding-left: 10px; padding-bottom: 10px; padding-top: 10px"><font face = "century gothic" color="white"> Risks & Mitigation (Mid-Term) </font> </div><br/>= | ||
− | + | {| class="wikitable" style="text-align: center; height:80px; width: 90%; font-size:100%;" | |
+ | ! scope="col" width="300" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Type of Risk</font> | ||
+ | ! scope="col" width="350" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Risk Description</font> | ||
+ | ! scope="col" width="150" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Risk Level</font> | ||
+ | ! scope="col" width="350" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Mitigation<br></font> | ||
+ | |-!scope="row" style="background-color: LightSlateGray"| | ||
+ | |- | ||
+ | |- | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | Project Management | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :Team members might underestimate school commitments and conflicting priorities. This might affect the completion of deliverables and even the quality. | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | Medium | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :Every week, all the members have to filling the "Time for FYP" sheet and clarify if he/she has other school commitments, so that PM can better schedule the task for each member. | ||
− | |||
|- | |- | ||
− | + | |style="text-align: center; background-color: white"| | |
+ | Project Management | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :Client was overseas and not able to meet with team physically. | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | Low | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | Online tools were being used. Regularly email client about the team's progress. | ||
+ | |- | ||
− | |- align = "left" | + | |style="text-align: center; background-color: white"| |
+ | Design and Development | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :We have underestimated the difficulties of Facebook integration | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | Medium | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :Reschedule and shift independent development in front | ||
− | | | + | |- |
− | | | + | |
− | + | |style="text-align: center; background-color: white"| | |
− | | | + | Project Requirement Risk |
− | + | |style="text-align: left; background-color: white"| | |
− | | | + | : Client raise concern of the pricing model. Project schedule may be affected to accommodate the changes to the project. |
− | + | |style="text-align: center; background-color: white"| | |
+ | High | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :Work with the sponsor to create a requirement document that both parties agreed on. Come to an understanding that any change requests would subject to the other party’s approval based on their judgment of necessity of the change | ||
− | | | + | |} |
− | |||
− | |||
− | + | =<div style="font-size:100%; background-color: LightSeaGreen; color: white; width: 1000px ; padding-left: 10px; padding-bottom: 10px; padding-top: 10px"><font face = "century gothic" color="white"> Risks & Mitigation (Final) </font> </div><br/>= | |
− | |||
− | |||
− | |||
+ | {| class="wikitable" style="text-align: center; height:80px; width: 90%; font-size:100%;" | ||
+ | ! scope="col" width="300" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Type of Risk</font> | ||
+ | ! scope="col" width="350" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Risk Description</font> | ||
+ | ! scope="col" width="150" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Risk Level</font> | ||
+ | ! scope="col" width="350" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Mitigation<br></font> | ||
+ | |-!scope="row" style="background-color: LightSlateGray"| | ||
|- | |- | ||
+ | |- | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | Project Management | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | : During week11&12, the entire team was overwhelmed by projects from different modules, which reduced the time we have spent on FYP. | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | High | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | : Estimate the time for the to be developed functions, adjust the project scope and drop certain tertiary functions accordingly. | ||
+ | |- | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | Project Management | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | : It's very hard for the team to meet physically when we are overwhelmed by different projects. | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | Medium | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :Facebook chat and google hangout are being used to facilitate our communication | ||
+ | |- | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | Business Requirement Risk | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | : Client changed the business requirement | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | High | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | : | ||
+ | *Adjust the project scope | ||
+ | *Re-schedule the project | ||
+ | |- | ||
+ | |style="text-align: center; background-color: white"|Business Requirement | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :There is insufficient promotions posted on the website. | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | Medium | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | *Push sponsor refer us more merchant to post on our website | ||
+ | *Visit restaurant to promote TheFoodieMarket | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} |
Latest revision as of 12:03, 20 November 2014
AT+Co. Jr. | OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
[ TIMELINE ] | [ SCHEDULE ] | [ METRICS ] | [ RISKS ] | [ TECHONOLOGY ] |
Contents
Risks & Mitigation
Project Requirement
# | Risk Description | Example | Likelihood | Impact |
Risk Value |
Mitigation |
---|---|---|---|---|---|---|
1.1 |
|
|
4 |
4 |
16 |
|
1.2 |
|
|
4 |
4 |
16 |
|
Design and Developement
# | Risk Description | Example | Likelihood | Impact |
Risk Value |
Mitigation |
---|---|---|---|---|---|---|
2.1 |
|
|
4 |
4 |
16 |
|
2.2 |
|
|
4 |
3 |
12 |
|
2.3 |
|
|
4 |
4 |
16 |
|
2.4 |
|
|
3 |
4 |
12 |
|
Project Management
# | Risk Description | Example | Likelihood | Impact |
Risk Value |
Mitigation |
---|---|---|---|---|---|---|
3.1 |
|
|
3 |
4 |
12 |
|
3.2 |
|
|
3 |
4 |
12 |
|
3.3 |
|
|
3 |
4 |
12 |
|
3.4 |
|
|
3 |
4 |
12 |
|
3.4 |
|
|
2 |
5 |
10 |
|
Risks & Mitigation (Acceptance)
Type of Risk | Risk Description | Risk Level | Mitigation |
---|---|---|---|
Project Management |
|
High |
|
Project Management |
|
Medium |
|
Design and Development |
|
Medium |
|
Risks & Mitigation (Mid-Term)
Type of Risk | Risk Description | Risk Level | Mitigation |
---|---|---|---|
Project Management |
|
Medium |
|
Project Management |
|
Low |
Online tools were being used. Regularly email client about the team's progress. |
Design and Development |
|
Medium |
|
Project Requirement Risk |
|
High |
|
Risks & Mitigation (Final)
Type of Risk | Risk Description | Risk Level | Mitigation |
---|---|---|---|
Project Management |
|
High |
|
Project Management |
|
Medium |
|
Business Requirement Risk |
|
High |
|
Business Requirement |
|
Medium |
|