Difference between revisions of "IS480 Team wiki: 2017T1 PlusMinus Midterm Wiki"
(updated AI Technical diagram size) |
(updated midterms project progress summary) |
||
Line 40: | Line 40: | ||
==Project Progress Summary== | ==Project Progress Summary== | ||
===<div style="background: #5d5d5d; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em; font-size:20px"><font color=#fbfcfd face="Century Gothic">Project Progress Summary</font></div>=== | ===<div style="background: #5d5d5d; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em; font-size:20px"><font color=#fbfcfd face="Century Gothic">Project Progress Summary</font></div>=== | ||
− | + | [[Image:plusminus_Mainpage_s11.png|center|1000px|link=]] | |
− | [[Image: | ||
<center> | <center> | ||
<table> | <table> | ||
<tr> | <tr> | ||
− | <td>[[Image:plusminus_screen.png | center | 200px | link=]]</td> | + | <td>[[Image:plusminus_screen.png | center | 200px | link=plusminus_MidTermsSlides]]</td> |
− | <td>[[Image:plusminus_learnhub_logo.png | center | 200px | link= | + | <td>[[Image:plusminus_learnhub_logo.png | center | 200px | link=https://learnhub.amkh.org.sg/learnhub/login.aspx]]</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td><center><font face="Century Gothic" size=4px color="#d1b195">[ | + | <td><center><font face="Century Gothic" size=4px color="#d1b195">[plusminus_MidTermsSlides| Mid Terms Slides]</font></center></td> |
− | <td><center><font face="Century Gothic" size=4px color="#d1b195">[https:// | + | <td><center><font face="Century Gothic" size=4px color="#d1b195">[https://learnhub.amkh.org.sg/learnhub/login.aspx| Portal Link]</font></center></td> |
</tr> | </tr> | ||
</table> | </table> | ||
</center> | </center> | ||
− | |||
==Project Highlights== | ==Project Highlights== |
Revision as of 20:17, 7 October 2017
Main Wiki | Midterm Wiki | Final Wiki |
Contents
Project Progress Summary
Project Progress Summary
Project Highlights
Project Highlights
Project Management
Project Status
Removed Functions
Project Schedule (Planned vs Actual)
The project plan was adjusted based on the change in client's needs as well as what the team feels comfortable delivering with. We placed modules that we are unfamiliar with at the start of the timeline, followed by the modules' level of importance. Each sprint is carefully planned by ensuring that workload are within the team's capability.
When 'Training Nomination Approval Workflow' Module was being re-scoped to 'AI Chatbot' Module, other related modules such as 'Certification', 'Attendance', and 'Calendar View' are removed to accommodate the new module. After proper re-planning of modules, we are able to fit in the new modules into the existing timeline.
Planned Schedule
Actual Schedule
Project Metrics
The team is using Sprint Burndown and Bug Metrics to ensure effective planning. Sprint review is conducted at the end of every sprint the team will work together to estimate the workload and effort required.
Overall Burndown Chart
[TO BE UPDATED!!!]
Burndown Chart
[TO BE UPDATED!!!]
The Burndown Chart shows the actual and estimated amount of work to be done in a sprint. The horizontal x-axis in a Burndown Chart indicates Sprint, and the vertical y-axis indicates the estimated hours required based on the estimated complexity of the module. An Overall Burndown Chart to display overall progress.
Team PlusMinus has observed that apart from the first sprint with an underestimated effort, remaining sprints are estimated more closely to the actual progress. An improvement the team adopted would be to always organize an end-of-sprint meeting to wrap up the current sprint and also discuss on the modules for the next sprint and also the estimated effort required. One improvement the team would like to adopt would be to be able to improve our estimating skills to estimate each sprint's effort to bring estimated burndown and actual burndown even closer.
Bug Metrics
TO BE CHANGED
The Bug Metrics shows how many bugs there are in each sprint and also the number of bugs that are carried forward from previous sprints. The team aims to resolve the bugs before the sprint ends and to carry forward as minimal number of bugs as possible. Should there be too many bugs to be resolved, the team will assess the bug's critical level and resolve the bugs that are more critical.
Project Risks
Some of these risks did happened and they are logged under our Issues Log Table (as shown below Risk Table).
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. |
No |
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. |
Yes |
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. |
Yes |
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.
|
Yes |
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. |
Yes |
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. |
Technical Complexity
Technical Complexity
AI Chatbot
Deployment - Web Hosting
Intermediate Deliverables
Intermediate Deliverables
Topic of Interest | Link |
---|---|
Project Management | Project Schedule |
Metrics | |
Risk Management | |
Change Management | |
Project Overview | Project Overview |
Project Scope | |
Market Research | |
X-Factor | |
Project Documentation | Diagrams |
Testing | |
Meeting Minutes |
Deployment
Deployment
You may access our portal through this link:
Test Deployment - AMK Server: https://learnhub.amkh.org.sg/learnhubUAT.login.aspx
Live Deployment - AMK Server: https://learnhub.amkh.org.sg/learnhub.login.aspx
Testing
Internal Testing
You can read more about our test plan here: Download Test Plan
This is a sample of our bug log:
User Testing
This is the key highlights of UT results:
For more information regarding User Testings, please refer to UT1/UT2
Non-Functional Testing
This is a sample of our Non-Functional Testing Log:
This is the screenshot of automated non-functional test results:
Reflection
Sponsor's Feedback
xxx
Team Reflection
1. Set up agreed name conventions for variables
2. Communication is key
Individual Reflection
Low Wen Jun:
I have learnt that as a PM, it is difficult to manage expectations between client and the team. I have also learnt on the importance of gathering clear project requirements before actual development of functions.
Al Rafid Bin Abdul Aziz:
Hosting without testing is the same as not hosting.
Tan Ming Kwang:
Scope creep happens all the time. There is a need to manage user's needs as well as to ensure project is delivered on time.
Eugene Tan Wei Hong:
Tech is a learning adventure that never ends.
Gwee Wei Ling:
Communication is vital when working together in a team
Mario Ngawing:
There's never "too much time" for coding.