Difference between revisions of "IS480 Team wiki: 2017T2 Mavericks Finals Wiki"
Line 49: | Line 49: | ||
<div style="text-align: left; text-indent: 30pt; font-size:85%; "> | <div style="text-align: left; text-indent: 30pt; font-size:85%; "> | ||
Place your Final slides link and deployed site link here | Place your Final slides link and deployed site link here | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</div> | </div> | ||
Revision as of 13:49, 3 April 2018
Place your Final slides link and deployed site link here
What unexpected events occurred and how were they handled?
- A team member left the project and dropped the course
- List of requirement changes
- CRUD items replaced with CU/Sync/Archive items
- Business analytics replaced with iPad client
- Took 8 weeks to learn Ruby on Rails
- etc.
Be brief. A couple of sentences on the event and another couple on what was done is sufficient. Do not repeat the next sub sections. If there are no highlights, remove this section
Describe areas of the project that were particularly difficult and how they were dealt with, whether successfully or not. Again, a few sentences are enough. If there are no challenges, remove this section.
Methods, technologies, processes, teamwork, etc. which were particularly successful – highlight things which worked very well towards completing the project. A bulleted list of one to two sentences each will do. If there are no achievement, remove this section.
Iteration Progress: 14 of 15
Features Completion: 100% (32 out of 32 features)
Confidence Level: 100%
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 |
Compare the project plan during midterm with the actual work done at this point. Briefly describe a summary here. Everything went as plan, everything has changed and the team is working on a new project with new sponsors or the supervisor is missing. A good source for this section comes from the project weekly report.
Provide a comparison of the plan and actual schedule. Has the project scope expanded or reduced? You can use the table below or your own gantt charts.
Planned Schedule
Contents
Actual Schedule
For more information on metrics collected, please refer here.
To be inserted
Provide more details about the quality of your work. For example, you designed a flexible configurable system using XML.config files, uses Strategy Design Pattern to allow plugging in different strategy, implement a regular expression parser to map a flexible formula editor, etc.
Project Deliverables:
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 | ||
Handover | Manuals | User tutorial, Developer manual, Setup manual |
Code | client server | |
Deployment Diagram | instructions |
Quality:
Explain the quality attributes (non functional) of your project deliverables. Have you designed the architecture, use a design pattern, etc? Does your architecture address scalability, performance, reliability, availability, fault tolerance, usability, etc. Does your design address maintainability, flexibility, configurability, etc. Be brief here but you can link to diagrams or code detail pages. Do not repeat the technical complexity part, link to it if necessary.
Deployment:
In an iterative approach, ready to use system should be available (deployed) for client and instructions to access the system described here (user name). If necessary, provide a deployment diagram link.
Testing:
- Internal Testing is performed for every new function developed
- Team Mavericks has scheduled for 5 User Testings in total
- We have accomplished 3 User Testings as of Iteration 11
For more information regarding User Testing and view results, please click here.
Describe the testing done on your system. For example, the number of user testing, tester profile, test cases, survey results, issue tracker, bug reports, etc.
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.