HeaderSIS.jpg

IS480 Team wiki: 2017T1 CodeBenders Risk

From IS480
Jump to navigation Jump to search


Codeblender logo.jpg
Home CodeBlenders.png

HOME

Users CodeBlenders.png

ABOUT US

ProjectOverview CodeBlenders.png

PROJECT OVERVIEW

Calendar CodeBlenders.png

PROJECT MANAGEMENT

File CodeBlenders.png

DOCUMENTATION

 

PROJECT SCHEDULE


S/N Risk Category Risk Type Risk Management Likelihood Impact Strategy
1 Technical Risk Team was unfamiliar with project technologies such as PostgreSQL, ReactJS, Django and etc. High Medium A Mitigate
2 Stakeholder Management Risk Team had to manage not only sponsors but also the developer team that the sponsors engaged. High High A Mitigate
3 Technical Risk Conflicts arise during integration as IPMAN and developer team simultaneously commit to the same test server. High High A Mitigate
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
8 Human Risk Various team members have different priorities in work which leads to inefficient allocation and completion of tasks. Low Medium C Mitigate
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
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
11 Technical Risk Team IPMAN had the risk to reformulate the analysis models because of sparse data sets. High High A Mitigate
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