Difference between revisions of "IS480 Team wiki: 2014T1 AT Co JR RISKS"
Jump to navigation
Jump to search
(21 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: | + | |
+ | =<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]] | ||
+ | |||
+ | |||
+ | ==<div style="font-size:100%; background-color: #f1c40f; color: white; width: 1000px ; padding-left: 10px; padding-bottom: 10px; padding-top: 10px"><font face = "century gothic" color="white"> Project Requirement </font> </div><br/>== | ||
{| class="wikitable" style="text-align: center; height:80px; width: 90%; font-size:100%;" | {| class="wikitable" style="text-align: center; height:80px; width: 90%; font-size:100%;" | ||
! scope="col" width="30" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">#</font> | ! scope="col" width="30" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">#</font> | ||
! scope="col" width="350" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Risk Description</font> | ! scope="col" width="350" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Risk Description</font> | ||
− | ! scope="col" width=" | + | ! scope="col" width="350" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Example</font> |
− | ! scope="col" | + | ! scope="col" width="100" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Likelihood</font> |
− | ! scope="col" width=" | + | ! scope="col" width="100" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Impact<br></font> |
− | + | ! scope="col" width="100" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Risk Value<br></font> | |
− | + | ! scope="col" width="350" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Mitigation<br></font> | |
− | !scope=" | ||
− | <font color="white"> | ||
− | |||
− | <font color="white"> | ||
|- | |- | ||
− | + | | scope="row" style="text-align: left; background-color: white"| | |
'''1.1''' | '''1.1''' | ||
− | |style="text-align: left;"| | + | |style="text-align: left; background-color: white"| |
− | *'''Unclear Requirements | + | *'''Unclear Requirements'''<br> |
− | |style="text-align: left;"| | + | :System requirements is not clearly identified, is unclear or is incorrect, leading to continuous change of requirements |
− | * | + | |style="text-align: left; background-color: white"| |
− | |style="text-align: center;"| | + | *Client is indecisive of his business plan, which might leads to requirements are not clear for the team <br> |
− | + | *The team may not know what is best for the client as the idea is relatively new to the industry. Conversely, the client might not have a clear idea on the deliverables of the project as well | |
− | |style="text-align: center;"| | + | |style="text-align: center; background-color: white"| |
− | + | 4 | |
+ | |style="text-align: center; background-color: white"| | ||
+ | 4 | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 16 | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :Work closely with client, and review the requirements list with client at every iteration so changes can be addressed as soon as possible. | ||
|- | |- | ||
|- | |- | ||
− | + | | scope="row" style="text-align: left; background-color: white"| | |
'''1.2''' | '''1.2''' | ||
− | |style="text-align: left;"| | + | |style="text-align: left; background-color: white"| |
− | *'''Continuous Changes of Requirements | + | *'''Continuous Changes of Requirements''' <br> |
− | |style="text-align: left;"| | + | :Unforeseen change in requirements due to lack of experience or expectations towards requirements |
− | * | + | |style="text-align: left; background-color: white"| |
− | |style="text-align: center;"| | + | *Client may have new ideas coming out during development phase |
− | + | *Tendency to add additional functionalities and try to deliver more than agreed which will ultimately cause the team to not be able to meet deadlines | |
− | |style="text-align: center;"| | + | |style="text-align: center; background-color: white"| |
− | + | 4 | |
+ | |style="text-align: center; background-color: white"| | ||
+ | 4 | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 16 | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :Evaluate priority and feasibility of new requirements before taking action | ||
+ | |||
|- | |- | ||
+ | |} | ||
+ | |||
+ | ==<div style="font-size:100%; background-color: #f1c40f; color: white; width: 1000px ; padding-left: 10px; padding-bottom: 10px; padding-top: 10px"><font face = "century gothic" color="white"> Design and Developement </font> </div><br/>== | ||
+ | |||
+ | {| class="wikitable" style="text-align: center; height:80px; width: 90%; font-size:100%;" | ||
+ | ! scope="col" width="30" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">#</font> | ||
+ | ! scope="col" width="350" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Risk Description</font> | ||
+ | ! scope="col" width="350" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Example</font> | ||
+ | ! scope="col" width="100" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Likelihood</font> | ||
+ | ! scope="col" width="100" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Impact<br></font> | ||
+ | ! scope="col" width="100" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Risk Value<br></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"| | ||
|- | |- | ||
− | + | | scope="row" style="text-align: left; background-color: white"| | |
− | |||
− | |||
− | |||
− | |||
− | |||
'''2.1''' | '''2.1''' | ||
− | |style="text-align: left;"| | + | |style="text-align: left; background-color: white"| |
− | *'''Technology and Learning | + | *'''Technology and Learning''' <br> |
− | |style="text-align: left;"| | + | :Project involves the use of new technology not used by members of the team prior to project or technology with inherently high level of technical complexity. This risk is extremely exposed to team members who are '''inexperienced, inadequately trained, or lacking in specialized skills'''. This leads to steep learning curve and potential personal “shortfalls” by team members, requiring long amount of time to complete tasks |
− | * | + | |style="text-align: left; background-color: white"| |
− | |style="text-align: center;"| | + | |
− | + | *This risk is extremely exposed to team members who are inexperienced, inadequately trained, or lacking in specialized knowledge | |
− | |style="text-align: center;"| | + | :eg: new file framework, javascript library or other useful web service |
− | + | *This leads to steep learning curve and potential personal “shortfalls” by team members, requiring long amount of time to complete tasks | |
+ | |||
+ | |style="text-align: center; background-color: white"| | ||
+ | 4 | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 4 | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 16 | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :Provide more buffer time in the first few iterations for developer to explore the new tools | ||
+ | |||
|- | |- | ||
+ | |||
|- | |- | ||
− | + | | scope="row" style="text-align: left; background-color: white"| | |
'''2.2''' | '''2.2''' | ||
− | |style="text-align: left;"| | + | |style="text-align: left; background-color: white"| |
− | *'''Integration of Project | + | *'''Integration of Project''' <br> |
− | |style="text-align: left;"| | + | :The lengthened integration of all different levels due to the complexities of the front-back end integration might result in a delay in the schedule |
− | * | + | |style="text-align: left; background-color: white"| |
− | |style="text-align: center;"| | + | *Varied coding competency and coding style of each team member might result in difficulties during integration |
− | + | |style="text-align: center; background-color: white"| | |
− | |style="text-align: center;"| | + | 4 |
− | + | |style="text-align: center; background-color: white"| | |
+ | 3 | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 12 | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :Work closely with client, and review the requirements list with client at every iteration so changes can be addressed as soon as possible. | ||
+ | |||
+ | |- | ||
+ | |||
+ | |- | ||
+ | | scope="row" style="text-align: left; background-color: white"| | ||
+ | '''2.3''' | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | *'''Critical Bug''' | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | *Application may contain some bugs that crashes the whole application in the last phase | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 4 | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 4 | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 16 | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :Constantly test the system and have proper testing documentation | ||
+ | |||
+ | |- | ||
+ | |||
|- | |- | ||
+ | | scope="row" style="text-align: left; background-color: white"| | ||
+ | '''2.4''' | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | *'''Platform incompatibilities''' | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | *Versioning software currently used goes down or encounters problems preventing the retrieval of project source codes<br> | ||
+ | *Unforeseen incompatibilities between various software uses may also arise | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 3 | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 4 | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 12 | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :Constantly test the system and have proper testing documentation | ||
|- | |- | ||
− | !scope=" | + | |
− | <font color="white"> | + | |} |
− | | | + | |
− | <font color="white"> | + | |
+ | ==<div style="font-size:100%; background-color: #f1c40f; color: white; width: 1000px ; padding-left: 10px; padding-bottom: 10px; padding-top: 10px"><font face = "century gothic" color="white"> Project Management </font> </div><br/>== | ||
+ | {| class="wikitable" style="text-align: center; height:80px; width: 90%; font-size:100%;" | ||
+ | ! scope="col" width="30" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">#</font> | ||
+ | ! scope="col" width="350" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Risk Description</font> | ||
+ | ! scope="col" width="350" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Example</font> | ||
+ | ! scope="col" width="100" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Likelihood</font> | ||
+ | ! scope="col" width="100" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Impact<br></font> | ||
+ | ! scope="col" width="100" style="background-color: black"| <font face = "helvetica" font color="white" font-size: "150%">Risk Value<br></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"| | ||
|- | |- | ||
− | + | | scope="row" style="text-align: left; background-color: white"| | |
'''3.1''' | '''3.1''' | ||
− | |style="text-align: left;"| | + | |style="text-align: left; background-color: white"| |
− | *''' | + | *'''Scheduling Creep''' <br> |
− | |style="text-align: left;"| | + | :Tendency to add additional functionalities and try to over-deliver which will ultimately cause the team to not be able to meet deadlines |
− | *Project | + | |style="text-align: left; background-color: white"| |
− | |style="text-align: center;"| | + | *Project manager is not sure of the competency of each team member, task allocation might not accurate which leads to project milestones or schedule inaccurately defined |
− | + | |style="text-align: center; background-color: white"| | |
− | |style="text-align: center;"| | + | 3 |
− | + | |style="text-align: center; background-color: white"| | |
+ | 4 | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 12 | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :Constantly track the task hour in the first iteration, and estimate task distribution based on that | ||
+ | |||
|- | |- | ||
+ | |||
|- | |- | ||
− | + | | scope="row" style="text-align: left; background-color: white"| | |
'''3.2''' | '''3.2''' | ||
− | |style="text-align: left;"| | + | |style="text-align: left; background-color: white"| |
− | *''' | + | *'''Monitor & Management''' |
− | |style="text-align: left;"| | + | : |
− | * | + | |style="text-align: left; background-color: white"| |
− | |style="text-align: center;"| | + | *There is an absence of adequate project management or there is ineffective project managers |
− | + | *The project progress may also not be monitored closely enough | |
− | |style="text-align: center;"| | + | |style="text-align: center; background-color: white"| |
− | + | 3 | |
+ | |style="text-align: center; background-color: white"| | ||
+ | 4 | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 12 | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :PM need to constantly monitoring whether the milestone being hit | ||
+ | |||
+ | |- | ||
+ | |||
+ | |- | ||
+ | | scope="row" style="text-align: left; background-color: white"| | ||
+ | '''3.3''' | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | *'''Communication''' | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | *Ineffective communications is carried out by team members | ||
+ | *This can be due to various barriers of communication | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 3 | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 4 | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 12 | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :PM need to make sure the team is bonded | ||
+ | :PM need to make sure everybody’s voice is heard | ||
+ | :FYP meeting will be on a routine basis to make sure | ||
+ | |||
+ | |||
+ | |- | ||
+ | |- | ||
+ | | scope="row" style="text-align: left; background-color: white"| | ||
+ | '''3.4''' | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | *'''Team Conflicts''' | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | *Team member doesn’t have a common understanding of the project, resulting difficulties in deriving final decisions | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 3 | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 4 | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 12 | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :Seek for supervisor and client’s idea when necessary | ||
+ | |||
+ | |- | ||
+ | |||
+ | |- | ||
+ | | scope="row" style="text-align: left; background-color: white"| | ||
+ | '''3.4''' | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | *'''Unforeseen Absence''' | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | *Team member withdraw from the project due to unexpected reason eg: family, personal issue. | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 2 | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 5 | ||
+ | |style="text-align: center; background-color: white"| | ||
+ | 10 | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | :Allocate a 2nd-person in charge to take over the responsibilities when needed | ||
+ | |||
+ | |- | ||
+ | |||
+ | |} | ||
+ | |||
+ | |||
+ | =<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"| | ||
|- | |- | ||
|- | |- | ||
− | + | |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 | ||
+ | *Review on roles and capabilities | ||
+ | *Reschedule the task | ||
+ | *Source for another team member and reevaluate the roles | ||
+ | |||
|- | |- | ||
− | + | |style="text-align: center; background-color: white"| | |
− | + | Project Management | |
− | |style="text-align: | + | |style="text-align: left; background-color: white"| |
− | + | :Changes in business concept leading to changes in system requirements | |
− | |style="text-align: left;"| | + | |style="text-align: center; background-color: white"| |
− | + | Medium | |
− | |style="text-align: center;"| | + | |style="text-align: left; background-color: white"| |
− | + | *Conducted business and competitor analysis for sponsor | |
− | |style="text-align: | + | *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: | + | |style="text-align: left; background-color: white"| |
− | + | :Client was overseas and not able to meet with team physically. | |
− | |style="text-align: left;"| | + | |style="text-align: center; background-color: white"| |
− | |||
− | |style="text-align: center; | ||
− | |||
− | |||
Low | Low | ||
+ | |style="text-align: left; background-color: white"| | ||
+ | Online tools were being used. Regularly email client about the team's progress. | ||
|- | |- | ||
+ | |||
+ | |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 | ||
|- | |- | ||
− | + | ||
− | <font color="white"> | + | |style="text-align: center; background-color: white"| |
− | | | + | Project Requirement Risk |
− | <font color="white"> | + | |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: | + | |style="text-align: center; background-color: white"| |
− | + | Project Management | |
− | |style="text-align: left;"| | + | |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;"| | + | |style="text-align: center; background-color: white"| |
High | High | ||
− | |style="text-align: | + | |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: | + | |style="text-align: left; background-color: white"| |
− | + | : Client changed the business requirement | |
− | |style="text-align: left;"| | + | |style="text-align: center; background-color: white"| |
− | + | High | |
− | |style="text-align: center;"| | + | |style="text-align: left; background-color: white"| |
− | High | + | : |
− | |style="text-align: | + | *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 |
|