IS480 Team wiki: 2017T1 Team Atoms Risk Management
Jump to navigation
Jump to search
Existing & Potential Risk
Currently there are no outstanding risk. All identified risk and challenges have been addressed.
Risks & Challenges Faced
S/N | Risk Type | Risk Event | Likelihood | Impact | Category | Mitigation Strategy |
---|---|---|---|---|---|---|
1 | Technical Risk | Team is unfamiliar with project technologies such as: Django, jointjs , plotly, scikit-learn, python. | Medium | High | A | Team members researched on the technologies and discussed the knowledge as a team. |
2 | Client Management Risk | There might be modifications in client requirements that requires changes to our schedule. | Medium | High | A | Our team will meet our client regularly to ensure that we are on top of our client’s requirements to lower the risk and impact of future changes to requirements. |
3 | Client Management Risk | Short duration & advance completion required for project to make it in time for in class student usage and testing | High | High | A | More functions to be completed during summer break and team members to work harder and longer during this period. |
4 | Project Management Risk | 3 out of 5 members of the team will be away on an overseas internship at different times. | High | High | A | Project Manager has accounted for everyone’s schedule when planning for the project. If there are any last-minute changes everyone is to inform the PM. Furthermore, we have arranged addition meetings before the absences of a team member to ensure more work is done. We will also engage in skype sessions for group discussion and remain active on telegram for updates. |
5 | Business Risk | High technical complexity in understanding and being familiar with data mining and KDD process. | High | High | A | Team studied IS424 resources, labs and lecture slides provided by sponsor extensively and conducted additional research on the subject matter. In addition, we will also consult the supervisor, sponsor and other professors. Lastly, we also learn from how other existing solutions have implemented the KDD process. |
6 | Resource Risk | Unexpected technology issues (laptop/repository crashes) | Low | High | B | Ensure that the latest documentation and codes are backed up in the repository and in other cloud storage as backup copy. |
7 | Project Management Risk | Team may not have sufficient time to finish the tasks assigned due to heavy school workload. | Low | High | B | Project Manager will ensure that the team is comfortable and able to deliver the product within the timeframe given to them |
8 | Human Risk | Various team members have different priorities and schedules in work which leads to inefficient allocation and completion of tasks. | Low | Medium | C | Establish weekly Saturday afternoon meetings to coordinate work and establish consensus. Also, conduct frequent updates on individual progress. |
9 | Technical Risk | Team Atoms faced problems with deploying its system on the SMU Living Analytics Research Centre (LARC) server provided by sponsor due to configuration, access rights and admin issues. | High | High | A | Team will seek an alternative server for deployment while simultaneously settling the existing deployment issues with the relevant stakeholders in charge |
10 | Client Management Risk | Team Atoms will face modifications to be made within a short period of time before every lab release. As the team will have to provide a highly customized and similar lab session experience with the existing lab exercises used in class. In addition, the team will also have to provide a new highly customized system user guide with every lab release. | High | High | A | Team will actively engage sponsor as early as possible before each lab release to provide sufficient time for changes required. In addition, the team will also dedicate time to specifically prepare for each lab release. |