IS480 Team wiki: 2017T2 Mavericks Finals Wiki
Iteration | Scope | Module | Task | Planned/New Feature | Status | Confidence Level | Comments |
---|---|---|---|---|---|---|---|
2 | Core | Account Module | Login/Logout | Planned | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
2 | Core | Customer Request Module | - View Account Balance - View Account Details - Funds Transfer - Add Payee - View Payee |
Planned | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
2 | Core | Chat Module | View Chat History | Planned | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
2 | Core | Dialog Flow Module | Manage Entities & Intents | Planned | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
3 | Core | Security Module | OTP Management | Planned | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
3 | Core | Dialog Flow Module | Process User Requests - AI Events & Exception Handling |
Planned | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
3 | Core | Chat Module | Speech-to-text Processing | Planned | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
3 | Core | Admin Module I | - Live Chat Takeover - Receive Notifications |
Planned | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
4 | Core | Admin Module I | View All Chats | Planned | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
5 | Core | Admin Module I | Receive Notifications | Planned | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
5 | Core | Customer Request Module | View Transaction History | Planned | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
6 | Core | Customer Request Module | - Request Loan - Agg. Expense View - Loan Calculator - Bill Payment |
Planned | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
7 | Core | Educational Module | Assessment Quiz (Backend Logic) | Planned | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
8 | Core | Educational Module | Glossary of Terms | Planned | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
8 | Core | Customer Request Module | - View Standing Instructions - Create Standing Instructions |
Planned | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
9 | Core | Educational Module | - Assessment Quiz (Creation) - Architecture View |
Planned | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
9 | Core | Admin Module II | Live Scoreboard | Planned | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
11 | Core | Educational Module | Request-Reply Details of API | Planned | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
11 | Core | Admin Module II | Descriptive Analysis | Planned | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
12 | Core | Educational Module | Assessment Quiz (New Changes) | New | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
12 | Core | Admin Module II | Live Support Analysis | New | Fully deployed and tested 100% | 1 | Reviewed and accepted by sponsor |
Stage | Specification | Modules |
Project Management | Minutes | |
Schedule | ||
Metrics | Bug Metrics, Task Metrics | |
Risk Mitigation | ||
Requirements | Overview | |
Scope | ||
Scenarios | ||
Analysis | System Architecture Diagram | |
Technologies Used | ||
Design | ER Diagram | |
Prototype | Video of tBuddy Prototype | |
Testing | User Testing 1 | UT1 - 6 Nov 2017 |
User Testing 2 | UT2 - 26 Jan 2018 | |
User Testing 3 | UT3 - 13 Feb 2018 | |
User Testing 4 |
Internal Testing is performed for every new function developed.
Team Mavericks has scheduled for 4 User Testings in total.
We have accomplished all User Testings as of Iteration 14.
For more information regarding User Testing and view results, please click here.
Team Reflection:
Key lessons learned – indicating where the team improved, or would do things differently next time. You may refer to the learning outcome summary in your proposal. A very short checklist style will suffice. It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.
Individual Reflection:
Describe in a paragraph, the key areas of learning or improvement. These should be personal areas of growth or learning. Each individual should list his/her effort, responsibility, actual contributions and personal reflection. Do not repeat team project contributions or member roles. Link if necessary.
Jamie's Reflection
I have learnt the importance of my role in team and stakeholder management, as well as maintaining overall responsibility of the project. As much as communication is essential within a team, it is also important for me to recognise every member's strengths and weaknesses, so that everyone can achieve their fullest potential to accomplish a common goal.
Yi Xiang's Reflection
We should be open to change in order for us to improve. Even if we have a good idea, which we believe to be the best, we should be open to feedback and make necessary changes. The ones who decide whether if the idea is good or not are the target users. Thus, it is important to have proof of deploment and user testing to get users' feedback for improvements.
Gerald's Reflection
As the Tech Architect, there is always something new to learn, best practices that we ought to adopt. It’s important that I’m up to speed with the right implementation to ensure that the application performs according to expectation. I’ve learnt that other than implementing a feature, we ought to implement it well so that it is usable for the users.
Bertran's Reflection
What I have learnt is that in a software project, non-functional requirements are extremely important. In fact, it might even be more difficult to fulfil a non-functional requirement, and these are often overlooked or underestimated in project plans.
Yi An's Reflection
As the Quality Assurance Lead, I learnt that having attention to details is crucial in making a excellent product. Additionally, adapting to changes is the key to creating a holistic product.
Sponsor Comment:
Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.