IS480 Team wiki: 2017T2 CAVETZ Final Wiki
Contents
Project Progress Summary
Final Slides: Download Here
Project Highlights
Project Highlights
Project Challenges
Project Achievements
Project Management
Project Scope
Planned |
---|
Actual |
---|
Scope Changes
Project Timeline
Planned |
---|
Actual |
---|
Schedule Changes
Project Metrics
Schedule Metrics
Updating
Iteration | Planned Duration (Days) | Actual Duration (Days) | Schedule Metric Score | Action Taken | Status |
---|---|---|---|---|---|
4 | 32 | 35 | 3 | Underestimated time needed to fix bugs in deployment environment.
Follow up action: Informed the course coordinator about the delay. More hours put in for debugging. PM to push spreadsheet function to iteration 10 as a good-to-have function after discussion with sponsor. No major delay to overall schedule. |
Completed |
Bug Metrics
Updating
Iteration | Bug Score | Bug Summary | Action Taken |
---|---|---|---|
4 | 16 1 low |
The bugs are:
Integration error of PDF.JS which makes the ebook reader not functional (critical) Search bar in Epitrain's library (Shop) not functional (high) System is unable to resend email for password recovery (low) |
Resolve bugs immediately. PM assigned debugging task to lead backend & lead frontend developer, rescheduled User Testing as well as tasks for iteration 5 and 6. Other developers proceed with development. |
7 | 11 6 low |
The bugs are:
Unable to stop users from copying PDF's content (high) Decryption of spreadsheet not working (low) Encryption of spreadsheet not working (low) No functions to up/downvote threads (low) Unable to tag threads (low) Subscribe function for students not available (low) Unable to filter profanity in forum threads (low) |
PM assigned developers to complete missing use cases. More bugfixing time allocated to this iteration. |
10 | 16 16 low |
The bugs are:
|
Resolve bugs immediately. PM assigned developers to Integrate UI. More bug fixing time allocated to this iteration, rescheduled User Testing as well as tasks for iteration 11. Other developers proceed with development. |
Effort Metrics
Updating
Iteration | Planned Effort (Man hours) | Actual Effort (Man hours) | Effort Metric Score | Action Taken | Status |
---|---|---|---|---|---|
4 | 96 | 140 | 45.83% | Re-estimate man hours for subsequent tasks. Spread out tasks across iterations more - with the last 3 iterations being allocated more tasks. | Completed |
Project Risks
Risk Type | Risk Event | Likelihood | Impact | Category | Prevention Measures | Reactive Measures |
---|---|---|---|---|---|---|
Requirement risk | Some corner cases and scenarios - especially about security and publishers’ functions - may not be fully captured in the requirement gathering phase. | Medium | High | A | We will plan test cases carefully and conduct thorough testing in order to detect corner cases and minimize the number of glitches | We will update requirements as the development progresses along the way to cover these corner cases. |
Technology Risk | There might be inconsistency in the quality of encryption on different devices or among different types of files as our team has limited experience in implementing encryption methods. To mitigate this, our team decided to consult professors with expertise in security and do research on encryption implementation of different devices. | Medium | Medium | B | We chose a framework with support for strong encryption techniques and compatible with multiple platforms (Laravel) and conducted intensive research on security standards as well as implementation methods of these methods that are suitable to our project | We will consult professors with expertise in security and arrange meetings with clients for alternative options |
Client Management Risk | There might be misunderstanding of requirements and expectation between us and our client since they are not familiar with IT techniques and limitations. | High | High | A | The team will communicate regularly with the client to ensure that the client is satisfied with our products and to keep us on track should any change need to be made | To mitigate this, we will arrange irregular meetings with the sponsor to adjust our business and IT expectations should we know that a misunderstanding is present. |
Risk Measure Logs
Iteration | Risk Type | Event description | Measures taken | Status |
---|---|---|---|---|
5 | Technology | Clients want their macro-enabled spreadsheets to be accessed online simultaneously by 50 students. However, we have a few problems:
- Online spreadsheets application do not support macros - Online excel spreadsheet is configured by Microsoft to be accessed only one at a time (there is a locking mechanism involved that we can't change) - Spreadsheets' formulas are our sponsors' intellectual properties, thus they cannot let the students copy it out and our team has very restricted access to the spreadsheets |
Meeting with client was arranged to rectify the issue. We proposed using either d3.js to stimulate the spreadsheet or to let students have offline access to it with encryption mechanism involving the users' passwords. The client chose the second method and our team decided to consult multiple professors as well as our supervisor for help regarding encryption. | Completed |
6 | Client management | Clients' requirements for us to have all our plugins and libraries resided within our platform and for our platform to call no external service wasn't made clear at the beginning at the project. Thus, they expect our ebook highlighting & annotation functions which are calling an external service (Hypothes.is) to be ported inside our application code. However, there are no available PDF highlighting & annotation plugin that we can embed in our application and our team lacks the capability and time to develop such functions from scratch. | Meeting with client was arranged to rectify the issue. However since the CEO on our sponsor side couldn't be there, conversation through emails following the meeting were carried out to reach a consensus of having an exception for this ebook highlighting & annotation function. | Completed |
Quality of Product
User Testing
User Testing | Date | Venue | Number of Testers |
---|---|---|---|
User Testing 1 | 3.30pm – 4pm Oct 28th 2016 | SOA SR 3-1 and Off-Site | 6 Epitrain Students |
User Testing 2 | 11th Jan 2017 - 17th Jan 2017 | Off-Site | 6 SMU Students |
User Testing 3 | 7pm – 7:30pm 21st Feb 2017 | SIS SR 2-4 & Off-Site | 4 Epitrain Students |
User Testing 4 |