Difference between revisions of "IS480 Team wiki: 2016T1 PolyVision Midterm"
Line 187: | Line 187: | ||
===Project Risks=== | ===Project Risks=== | ||
+ | [[IS480 Team wiki: 2016T1 PolyVision Risk Management| Click here to view more about our risk management]] | ||
+ | |||
<center> | <center> | ||
{| class="wikitable" style="text-align: center; width:1050px" | {| class="wikitable" style="text-align: center; width:1050px" | ||
Line 197: | Line 199: | ||
|- | |- | ||
− | | | + | | Further changes to requirements |
− | | | + | | Medium |
− | | | + | | High |
− | | | + | | Regular meetings and feedback from client to ensure timely delivery |
|- | |- | ||
|} | |} | ||
</center> | </center> | ||
− | |||
− | |||
===Technical Complexity=== | ===Technical Complexity=== |
Revision as of 01:39, 6 October 2016
Home | About Us | Project Overview | Project Management | Project Documentation |
Midterm
|
Project Progress Summary
Deployed URL: https://vgpinsight.com
Midterm Deck: Coming Soon...
Project Highlights
- 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)
Project Management
Project Status
S/N | Module | Description | Confidence (%) | Status |
---|---|---|---|---|
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 |
Project Schedule
Plan | Actual |
---|---|
Project Metrics
Task Metrics
Click here to view more about how we collect our tasks metrics.
Bug Metrics
Click here to view more about how we collect our bug metrics.
(Bug metrics here)
Project Risks
Click here to view more about our risk management
Risk Event | Probability | Impact | Mitigation Plan |
---|---|---|---|
Further changes to requirements | Medium | High | Regular meetings and feedback from client to ensure timely delivery |
Technical Complexity
Frontend Technical Complexities | |||
---|---|---|---|
Rank | Complexity | Reason | Solution |
1 | |||
2 | |||
3 |
Backend Technical Complexities | |||
---|---|---|---|
Rank | Complexity | Reason | Solution |
1 | |||
2 | |||
3 |
Quality of Product
Intermediate Deliverables
Stage | Specifications | Work Products |
---|---|---|
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 | ||
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. | |
Metrics | Metrics | |
Design Diagrams | Use Case, Class Diagram, Sequence Diagram, As-Is Process Diagram, To-Be Process Diagram | Use Case Class Diagram Sequence Diagram As-Is Process Diagram To-Be Process Diagram |
Prototype | Paper Prototype Hi-fidelity Prototype | |
Testing | User Test Plan | User Testing 1 |
Deployment
INSIGHT application can be found at this URL: https://vgpinsight.com
Note: Please ensure that you are using the latest version of Google Chrome browser with Javascript enabled to enjoy the full INSIGHT experience.
Testing
We have conducted one user testing.
User Testing 2:
Click here for more details on our UT2
Reflections
PolyVision
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.
Fusen Li
As the Backend Developer of PolyVision,
Joleen Lee
As the Frontend Developer of PolyVision,
Jonathan Lee
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,
Ong Wee Tiong
As the Backend Developer of PolyVision,