IS480 Team wiki: 2017T1 PlusMinus RiskMitigation

From IS480
Jump to navigation Jump to search

PlusMinus Homepage.png


  PlusMinus About-us.png


  PlusMinus projectOverview.png


  PlusMinus Checklist.png


  PlusMinus Documentation.png


Project Schedule Metrics Risk Mitigation Plusminus Subplane.PNG Change Management

Risk Matrix

Plusminus riskMatrix.PNG

Identified Risks

S/N Date Risk Type Risk Title Likelihood Impact Category Mitigation Plan Escalate into Issue?
1 21/May/2017 Technical Risk The team is unfamiliar with project technologies such as ASP.NET and LUIS, and have limited experience in implementing certain functionalities/logic such as approval workflow routing logic. High High Red We will consult professors with expertise and look for alternative options to go about resolving the issues Yes
2 21/May/2017 Project Management Project will be delayed due to underestimated/unclear functionalities High Medium Dark Orange We will work with sponsor closely to refine the functionality specs prior to the start of coding phase and to clarify immediately once any forms of misconception arises

In addition, the team will work together to clarify any doubts that one another should have and assist in completing the functionality assigned.

3 21/May/2017 Client Management Sponsors might add/change their requirements High High Red For any sudden changes in requirements, we will log it under change request which the team will only get back to it after we finished all pre-stated functionalities.

To prevent this, we will work closely with sponsors to keep them updated frequently such that we can react to changes should the functionality has yet been executed.

4 04/July/2017 Technical Risk Team might not be able to configure the AI Bot to host it in AMKTHK's server. High High Red To prevent this, we will work closely with our point of contact from AMKTHK's IT Department, Mr Edy Chandra, to successfully host the AI Bot to AMKTHK's server through configurations. Yes
5 04/July/2017 Client Management Client might request to do a major change(add/drop functionalities) in project scope again Medium High Dark Orange Should client raise request to conduct any major changes to project scope, team will have to scrutinized the requested changes carefully and assess how this change will affect the project's critical path elements.

It is important to note that changes must be made sparingly and if something new goes into the scope, something else must be sacrificed. In the event when client's request would cause any delay in timeline, we will assess the situation. In the worst case scenario, the team is prepared to drop this project collaboration with AMKTHK.

6 04/July/2017 Client Management Client might request to do a minor change in tweaking pre-stated functionalities High Medium Dark Orange Should client make any minor changes in functionalities, if it can be attained easily, the team can tweak the portal accordingly after logging it under change management. If it is a complicated tweak, we will log it under change request which the team will only get back to it after we finished all pre-stated functionalities.

To prevent this, we will work closely with sponsors to keep them updated frequently such that we can react to changes should the functionality has yet been executed.

  • Complexity of the change is up to team PlusMinus discretion.
7 13/July/2017 Client Management Client might not reply to the team questions on the project requirements promptly Medium High Dark Orange If our main client(Cheryl) does not reply promptly to the team's question with regards to the project scope, we will delegate the authority to make decisions to our second client(Edy). However, Edy's decision is subjected to HR's approval.

There is no way to prevent this Risk. However, the team can contact client more often to remind them for their replies and also schedule for more face to face meetings to answer the team's queries.


Issues Log

S/N Raised Date Issue Name Raised By Description Target Resolution Date Status Final Solution
1 27/Jun/2017 Client requesting for a change in Project Scope

- Risk #5

AMKTHK HR Department AMKTHK's HR Director, Frank came to a recent understanding that there is a training module in HRIS System which the hospital had budgeted for before he came in. Therefore, AMKTHK had decided to replace the online TNF Application Functionality to an AI Chat bot, hoping that they can provide their colleagues with the relevant HR information they need at their fingertips 24/7.

This AI chatbot is integrated with the HR information system to provide immediate and personalized responses. The issue arises to whether we (PlusMinus) have ample time to test and complete the AI Chatbot as it is already the end of Sprint 3. In addition, Chatbot is a brand new functionality that no one has experience in. The team is concern that it might be a steep learning curve for the coders to take on.

2/Jul/2017 Closed We accepted the change in project scope and altered our schedule to replace TNF Application Functionality to AI Chatbot. The chatbot is scheduled for completion before Sprint 7 - 13 Aug 2017.

To help the team ease the learning curve, we will consult professors and people with expertise on AI Chatbot, to gain more knowledge about building AI.

2 01/Jul/2017 Requiring payment for license to use the AI ChatBot

- Risk #4

Tan Ming Kwang

(Backend Developer)

In order to be able to fully optimize the ChatBot, AMKTHK is required to pay for license fee. We are in the midst of calculating the expected licensing fee required to use this chatbot. We have already raised this issue up to AMKTHK but has yet quoted a sum. 16/Jul/2017 Closed We have sourced for a free Chatbot - Microsoft LUIS, who offers 1000 free query hits per month. The team will work within the free 1000 free hits. Therefore, no payment is required from AMKTHK.
3 13/Jul/2017 Client did not reply to the team's queries for more than 1 sprint

- Risk #7

Belynda Low (Project Manager) Team is unable to get a response from client with regards to the project scope. This could lead to a delay to project timeline and affect project submission. 13/Jul/2017 Closed We will change project decision-maker, Cheryl, to Edy, whom is also our secondary project client. However, Edy will still require to obtain approval from HR department(Frank) before finalizing on the project scope.
4 28/Jul/2017 Official Change in POC Belynda Low (Project Manager) There is a change in Official Point Of Contact from Client. From the original client, Cheryl and Edy, to Frank (Director) and Edy. 28/Jul/2017 Closed The new clients, Frank and Edy, will be answering to the team's queries. Issue raised and approved by Prof Benjamin and Prof Paul.
5 04/Sept/2017 Client is unable to produce SSL certificate for the team to host the AI Chatbot.

- Risk #4

Eugene Tan Wei Hong

(Backend Developer)

Team is unable to host the Chatbot on their server because we need a require a SSL certificate. This is an issue as client does not have a spare certificate for the Chatbot. They have requested for a 0 cost solution for this problem. 11/Sept/2017 Closed We will be self-sourcing for free SSL Certs online to host the Chatbot. Client has created a test server and handled full access/configuration rights for the team to configure the free SSL.
6 30/Oct/2017 AI Chatbot's monthly query hits has been maxed out

- Risk #4

Eugene Tan Wei Hong

(Backend Developer)

Team is unable to access to the Chatbot because we have maxed out the allowed query hits for the month. We need to wait for the next month to reset the query hit counter to 0. As the team do not know the exact date for the query counter to reset, the team will re-create the chatbot on a separate account and manually train the chatbot again if the current chatbot does not reset it's counter by UAT - 8 Nov 2017. 06/Nov/2017 Closed Learny the Chatbot has reset it's query hits on the 4th November. There is no need to re-create the chatbot.