HeaderSIS.jpg

IS480 Team wiki: 2016T1 IPMAN Risk Management

From IS480
Jump to navigation Jump to search
Team IPMAN Logo 1600x800.png


Team IPMAN Icon Home.png   HOME

 

Team IPMAN Icon AboutUs.png   ABOUT US

 

Team IPMAN Icon ProjectOverview.png   PROJECT OVERVIEW

 

Team IPMAN Icon ProjectManagement.png   PROJECT MANAGEMENT

 

Team IPMAN Icon ProjectDocumentation.png   DOCUMENTATION

 


IPMAN RiskManagement Title.png


IPMAN RiskManagement Chart.png


IPMAN RiskManagement 1.png


Risks & Challenges Faced

S/N Risk Type Risk Event Likelihood Impact Level Category Strategy Adopted Actions
1 Technical Risk Team was unfamiliar with project technologies such as PostgreSQL, ReactJS, Django and etc. High Medium A Mitigate Team members researched on the technologies and discussed the knowledge as a team.
2 Stakeholder Management Risk Team had to manage not only sponsors but also the developer team that the sponsors engaged. High High A Mitigate Team came out with a communication protocol between the sponsors, developer team and team. Team is using Trello and Telegram for communications and updates.
3 Technical Risk Conflicts arise during integration as IPMAN and developer team simultaneously commit to the same test server. High High A Mitigate Team came out with a communication protocol between the sponsors, developer team and team. Team is using Trello and Telegram for communications and updates.
7 Client Management Risk There might be postponement in our scheduled sponsor meetings which leads to delay in getting feedback from business owners and delays in convergence of the product toward delighted customers or users. Medium Medium B Mitigate Prepare frequent feedback through communication channels used by our clients (for e.g. Telegram).
8 Human Risk Various team members have different priorities in work which leads to inefficient allocation and completion of tasks. Low Medium C Mitigate Establish weekly Sunday afternoon meetings to coordinate work and establish consensus. Also, conduct daily scrums virtually on Slack/Telegram to update each other on our progress.
9 Technical Risk Team IPMAN was unable to deploy as soon as all the bugs were resolved. Whenever sponsors report for bug issues, team immediately resolves the bugs. However, team IPMAN was unable to deploy the application with the fixed bugs as team was still building on the features in the current sprint and would only deploy the application at the end of the sprint when all features were completed. High High A Mitigate Team IPMAN came out with another branch for deployment which means there are now 2 branches, one of it is the deployment branch and another branch is to work on the existing features. Therefore, whenever sponsor raises any bug, team IPMAN would be able to resolve the bugs and deploy immediately without waiting for the features to be completed at the end of the sprint.
10 Stakeholder Management Risk Team IPMAN had to manage not only sponsors but also the developer team that the sponsors engaged. For instance, the freelancer developers have utilized Intercom to track the customers’ interaction on the application. This feature implemented affected the Smart Marketing features that we built. High High A Mitigate Team IPMAN communicated with sponsors early and found out more the implementation of Intercom. Team IPMAN also constantly met up with sponsor and checked with him about the progress of Intercom. Team IPMAN followed communication protocol between the sponsors, developer team and team IPMAN. Team IPMAN is using Trello and Telegram for communications and updates.
11 Technical Risk Team IPMAN had the risk to reformulate the analysis models because of sparse data sets. High High A Mitigate Team IPMAN consulted one of our Professors for the feasibility of the models created and also did a lot of prior research before the implementation of analysis modules. Subsequently, the team created a quick mock up for the prototype so that changes can be made easily.
12 Stakeholder Management Risk Freelancer developer created new feature on the old dashboard. Sponsors were inclined to use the old dashboard if the codes were not ported over to the new application. High High A Mitigate Team IPMAN ported over the entire code that the freelancer developers have created onto the new application as soon as they were built. Team IPMAN will schedule for a handover ceremony to present to the freelancer developers all the proper documentation we have created and assist any questions from them so as to ensure the continuity of the application.


Potential Risks

S/N Risk Type Risk Event Likelihood Impact Level Category Mitigation
4 Client Management Risk There may be changes in our client requirements which results in drastic changes to our schedule. Medium High A Our team will meet our client fortnightly to ensure that we produce based on our client’s requirements to reduce changes.
5 Project Management Risk Team may not have sufficient time to finish the tasks assigned due to heavy school workload. Medium High A Project Manager will ensure that the team is comfortable and able to deliver the product within the timeframe given to them
6 Resource Risk Laptop crashes during the FYP term Low High B Ensure that all the documentation is stored in cloud and codes are committed onto Git.
13 Integration Risk The new application that we have built is using the database models. If the database models change (such as when the internationalization functionality was built by the freelancers), these changes would impact our system. Low High B Team IPMAN took the initiative to understand what changes have been made and whether the changes are necessary by discussing with the freelancers early on. We also work to communicate with freelancers to modify models in a way such that any impact is minimized, e.g. adding fields instead of changing fields in the model.

Mitigation Plan

Communication Protocol with Sponsors and External Liaisons

IPMAN CommunicationProtocol.png


Silhouettes wiki background IPMAN.png