Difference between revisions of "IS480 Team wiki: 2015T1 4Sight Risk Management"
Jump to navigation
Jump to search
Line 166: | Line 166: | ||
|- | |- | ||
|External Risk | |External Risk | ||
− | | | + | |If the client decides to expand the project in the future to include additional features, incoming developers might not be familiar with the codes written and the technologies that the team have used. |
− | | | + | |1. The new team might have to spend a lot more time trying to comprehend the codes and devise ways to build new functionalities on top of existing ones. <br/> 2. The new team might consider building again from scratch due to the challenges they face in the above mentioned point. |
| align=center | Medium | | align=center | Medium | ||
| align=center | High | | align=center | High | ||
− | | | + | | 1. Well commented codes to ensure code readibility. <br/> 2. Modularize the application by functionalities so that there is minimal dependency considerations when scaling it. Modularized functions are coded to be reusable by any new feature set. |
| align=center | Mitigated | | align=center | Mitigated | ||
|- | |- | ||
|} | |} |
Latest revision as of 20:03, 29 November 2015
HOME | ABOUT US | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
Project Schedule | Software Development Methodologies | Schedule Metrics | Task Metrics | Bug Metrics | Risk Management | Change Management |
- Risks categorise as high require urgent attention. They are high in impact level and high in probability of occurrence. Crafting of the mitigation plans have to be well analyzed and developed
- Risks categorise as medium require moderate attention. They have a medium impact level and occur on an occasional basis
- Risks categorise as low require the least attention. They have a low impact level and occasionally or rarely occur
- Risks categorise as none require no attention
Activated Risks
- These risks have occurred. Team has taken the necessary actions to mitigate the risks.
|
|