IS480 Team wiki: 2016T1 PolyVision Midterm
|Home||About Us||Project Overview||Project Management||Project Documentation|
- 1 Project Progress Summary
- 2 Project Management
- 3 Quality of Product
- 4 Reflections
Project Progress Summary
- INSIGHT has been deployed and ready for clients to use since 20th September 2016
- Concluded UAT with 35 SMU students on 16th September 2016
- Tested & verified INSIGHT functionalities with sponsors on 14th September 2016
- Picked up interactive visualization tool - D3.js
- Constantly aligning INSIGHT development according to business needs (translating feedback into actions)
|1||Administrator||Fully deployed and tested on production server||100%||Completed|
|2||User Account||Fully deployed and tested on production server||100%||Completed|
|3||Company Management||Fully deployed and tested on production server||100%||Completed|
|4||Deal Management||Fully deployed and tested on production server||100%||Completed|
|5||Dashboard||Fully deployed and tested on production server||100%||Completed|
|6||VC Management||Fully deployed and tested on production server||100%||Completed|
|7||Event-Triggered Notification||Fully deployed and tested on production server||100%||Completed|
|8||Custom Notification||Fully deployed and tested on production server||100%||Completed|
|9||Reporting||Fully deployed and tested on production server||100%||Completed|
|10||Newsfeed||Fully deployed and tested on production server||100%||Completed|
|11||Backup||Fully deployed and tested on production server||100%||Completed|
|12||Search||Accepted change request||100%||Future Development|
|13||Name Card Recognition||Future Development||100%||Future Development|
|14||Usability||Future Development||100%||Future Development|
|15||Workflow History||Removed upon negotiation||N.A.||Removed upon negotiation|
|16||Usability||Removed upon negotiation||N.A.||Removed upon negotiation|
|Risk Event||Probability||Impact||Mitigation Plan|
|Incomplete deployment onto production server||Medium||High||Immediate debugging session|
|Further changes to requirements||Medium||High||Regular meetings and feedback from client to ensure timely delivery|
|1||D3.js||Change of library from Chart.js to D3.js. Found that suitability of chart.js for visualisation is inadequete, thus the change. However, due to the limited time and steep learning curve in addition to other unfamiliar technologies and libraries we had to use, the dashboard development was quite challenge.|
|3||Quartz.net||Scheduling of different threading’s to run at different timing of the days to perform automated tasks. Complex because certain automated jobs need to take place before another thread can trigger other jobs.|
Quality of Product
|Project Management||Schedule Management||A customized spreadsheet is maintained by the PM that is revised at the beginning of each Iteration ensuring that tasks are being completed.|
|Risk Management||Risk Management|
|Change Management||Change requests are raised after every meeting with the sponsor at the end of each Iteration. These requests are maintained within a spreadsheet then evaluated as a team on the priority, complexity before being included in the schedule by the PM.|
|Meeting Minutes||All meetings with the sponsor, supervisor, and team are being documented.|
|Design Diagrams||Use Case, Class Diagram, Sequence Diagram, As-Is Process Diagram, To-Be Process Diagram|| Use Case|
As-Is Process Diagram
To-Be Process Diagram
|Prototype|| Paper Prototype|
|Testing||User Test Plan|| User Testing 1|
INSIGHT application can be found at this URL: https://vgpinsight.com
We have conducted one user testing.
User Testing 2:
Click here for more details on our UT2
Collectively, Team PolyVision have a better understanding of their individual capabilities and limitations. The team has managed to pick up ASP .NET Razor markup language as a result of having every member responsible and accountable for a portion of INSIGHT application to foster greater ownership. And when the occasion arise that business needs are not fully aligned with the initial set of requirements, effective communication is paramount to align every stakeholder involved.
As the Backend Developer of PolyVision, I learn to better plan and manage my schedule. Juggling between IS480 and other school related activities.
As the Frontend Developer of PolyVision, I learn how to optimize the web application for different devices adhering to best coding practices for consistency and reusability.
As the Project Manager of PolyVision, I learn that it is important to grasp the optimum working preference and environment for the team to be productive. Most importantly, it is to enforce the above to ensure that the team can work more efficiently together.
Kong Song Wei
As the Database Architect of PolyVision, I learn the importance of good application and database design, with frequent feedbacks to limit the impact of change requests.
Ong Wee Tiong
As the Backend Developer of PolyVision, I learn how to deal with unexpected situations especially the change requirements to better fit the client business needs.