HeaderSIS.jpg

IS480 Team wiki: 2012T2 CHARIS ProjectManagement Risk

From IS480
Jump to navigation Jump to search

Charis Logo.png

Home The Team Project Overview Project Management Project Documentation Team Resources Team Reflection Portfolio
Project Schedule Framework Metrics Risk Management


Risk Metric

Risk table Charis3.png


Project Risks

S\N Risk Impact Likelihood Impact Level Risk Level Mitigation Strategy Comments
Security Risk
1 Security compromise of system Reliability of system wil be called into serious question. Client data may be leaked. Entire system may be compromised. Medium High A Continue to change relevant passwords regularly and test system for security loopholes. Engage proper encryption and security techniques.
Resource Risk
2 Linode server we are using goes down or the service is no longer under subscription Our application will have no server to be host on, thus the application will not be available Low High B Ensure monthly payments to the service is made regulalry and has been accounted for. Have an alternative backup server should the initial server used fails
Scope Risk
3 Sponsor change of requirements Schedule will be affected. Possibility of Core Functionalities and requirements not met on time Medium Medium B Regular fortnightly feedback and update sessions with the client to ensure both parties are up to date with the requirements and expectations to be met. Have a clear plan which will be shown to the client so that expectations can be managed should a change in requirement.
4 Scope being too big and complex. (Coding a modular facilities booking system/"Social networking platform"/Use of NFC Technology") Client dissapointment due to over-promise and under-delivering situation. Project might not be completed in time. Low Medium C Plan out entire project schedule. Use and close monitoring of schedule metrics to ensure project is kept on track. Consistent communication between Supervisor and client on scope and requirements to see if tasks are achievable and and feasilble.
Schedule Risk
5 Unable to complete scheduled tasks during Decemeber Period due to majority of team leaving for overseas vacation The project will fall behind in terms of project schedule which may lead to the dropping of functionalities Medium Medium B Plan for more buffers during the December period in event the team does not make the schedule requirements.
Usability Risk
6 Residents of the condomenium do not like the user interface of our system. Residents will stop using the system and revert to the previous paper based system of booking facilities Low Medium C Conduct sufficient user-testing on condo residents to ensure system is user-friendly enough for all possible condo residents.
Technical Risk
7 Use of PHP programming language due to hosting server technical requirements Team is not proficient In PHP language hence project development will be slower and pushed back due to steep learning cureve Low Medium C Discuss with the client on the possibility of using an alternative server which is compatible with java development. Client has agreed to used the hosting server the team has recommended which allows for java based development
8 Use of new technology such as NFC and Mobile App Development: NFC and Mobile Apps are new to the team hence coding using these new technologies might take longer than predicted The team may take more time then expected to learn and implement the NFC functionality hence delaying the project timeline Medium Medium B Ensure that sufficient time is allocated for the learning of NFC technology. Allow for greater buffers during the development iterations for NFC.
9 Use of Stripes Framework: Stripes implementation is new to most members of the team. Lack of online help and documentation for Stripes related programming problems Team may face a difficulty in implementing stripes effectively hence affecting coding efficiency and ultimately the project timeline Low Medium C Allocated time for the learning of Stripes Framework. Arrange weekly sessions at the start of the coding iterations to ensure team is sure of the concepts and knows how to implement stripes correctly.
10 Difficulty integrating application with online social media e.g. Facebook. Pushed back development timeline due to inability to complete the functionality Low Medium C Allocate time for research. Ask for help from friends or experience people in this subject matter
11 Condominium's DNS goes down. Despite the rest of the application working, users will be unable to access the application. Medium Medium B Provide backup access via IP Address (direct link) or by using URL shortening services such as TinyURL.
Development Risk
12 Application contains a critical bug that crashes the application Development will halt. Schedule will be pushed back Medium High A Create and use a bug metric. Ensure proper use of versioning software to ensure there are backup versions of the application the team can revert to. In our case we use Git Hub.
13 Versioning software we are currently using (GitHub) goes down or encounteres some problems preventing the retrieval of project source codes Application development will grind to a halt. Project schedule is pused back Low High B Make manual weekly backups of project source code. Since risk of this is low and GitHub has versioning capabilities, doing it once a week (half an interation) should be sufficient.
14 The condominium users find out the application is developed by University students and demand a paid professional system. Project client has a high possibility of withdrawing from the is480 project. Low High B Ensure that when conducting user testing/requirements gathering, condo residents who take part welcome the idea of the application regardless the developer.
15 The managing agent of the condominium is replaced Testing schedule will be set back, due to the necessity of retraining the administrator. Low High B Ensure that the application is easy to use and as user-friendly as possible to the admin. Ensure that there are sufficient guides to admin and residents.