HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T1 IPMAN Risk Management"

From IS480
Jump to navigation Jump to search
Line 103: Line 103:
 
|style="text-align: center;"| Mitigate
 
|style="text-align: center;"| Mitigate
 
|style="text-align: left;"| Team came out with a communication protocol between the sponsors, developer team and team. Team is using Trello and Telegram for communications and updates.
 
|style="text-align: left;"| Team came out with a communication protocol between the sponsors, developer team and team. Team is using Trello and Telegram for communications and updates.
 +
|-
 +
 +
|style="text-align: center;"| Technical Risk
 +
|style="text-align: left;"| Team 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 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.
 +
|style="text-align: center;"| High
 +
|style="text-align: center;"| High
 +
|style="text-align: center;"| A
 +
|style="text-align: center;"| Mitigate
 +
|style="text-align: left;"| Team 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 would be able to resolve the bugs and deploy immediately without waiting for the features to be completed at the end of the sprint.
 +
|-
 +
 +
|style="text-align: center;"| Stakeholder Management Risk
 +
|style="text-align: left;"|Team had to manage not only sponsors but also the developer team that the sponsors engaged. For instance, the freelancer developers had built Intercom to track the customers’ interaction on the application without us knowing. This feature implemented affected the Smart Marketing features that we built.
 +
|style="text-align: center;"| High
 +
|style="text-align: center;"| High
 +
|style="text-align: center;"| A
 +
|style="text-align: center;"| Mitigate
 +
|style="text-align: left;"| Team communicated with sponsors and found out more the implementation of Intercom. Team also constantly met up with sponsor and checked with him about the progress of Intercom. Team came out with a communication protocol between the sponsors, developer team and team. Team is using Trello and Telegram for communications and updates.
 
|}
 
|}
 
</center>
 
</center>

Revision as of 21:59, 28 September 2016

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

Risk Type Risk Event Likelihood Impact Level Category Strategy Adopted Actions
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.
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.
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.
Technical Risk Team 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 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 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 would be able to resolve the bugs and deploy immediately without waiting for the features to be completed at the end of the sprint.
Stakeholder Management Risk Team had to manage not only sponsors but also the developer team that the sponsors engaged. For instance, the freelancer developers had built Intercom to track the customers’ interaction on the application without us knowing. This feature implemented affected the Smart Marketing features that we built. High High A Mitigate Team communicated with sponsors and found out more the implementation of Intercom. Team also constantly met up with sponsor and checked with him about the progress of Intercom. Team came out with a communication protocol between the sponsors, developer team and team. Team is using Trello and Telegram for communications and updates.


Potential Risks

Risk Type Risk Event Likelihood Impact Level Category Mitigation
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.
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
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.

Mitigation Plan

Communication Protocol with Sponsors and External Liaisons

IPMAN CommunicationProtocol.png


Silhouettes wiki background IPMAN.png