IS480 Team wiki: 2015T1 Vulcan Midterm
HOME | ABOUT US | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
Contents
Project Progress Summary
Highlights of Project:
- LiveLabs relocation of servers on Oct 5th 2015, two days before Midterms Presentation
- LiveLabs servers overload (data increase 1GB/minute), seemed to have been caused by us
- API level of phone borrowed from school too low for our development
Project Management
Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.
Project Status:
Please refer to Planned vs Actual Tasks Metrics for the detailed breakdown of our individual tasks.
Project Schedule (Plan Vs Actual):
Compare the project plan during acceptance 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
Actual Schedule
Project Metrics:
Schedule Metric Formula: (Estimated Days / Actual Days) x 100%
Iteration | Planned Duration (Days) | Actual Duration (Days) | Schedule Metric Score | Action | Status |
---|---|---|---|---|---|
2 | 18 | 32 | 56.25% | Team is behind schedule. This is due to the complexity of the tasks planned (Android App and Smart Watch). Follow up action: Rescheduled the future iterations, deducted days from buffer days. |
Completed |
4 | 18 | 24 | 75% | Team is behind schedule. This is due to Livelab's server permission issues. Follow up action: Rescheduled the future iterations, deducted days from buffer days. |
Completed |
Project Risks:
These are the top risks we have identified and has happened before Mid Term. We have followed the mitigation steps listed above and successfully managed the risks.
Technical Complexity:
Quality of product
Intermediate Deliverables:
Stage | Specification | Modules |
---|---|---|
Project Management | Minutes (Sponsor,Supervisor, Team) | Minutes |
Metrics | Schedule, Bug, Change Management Metrics | |
Requirements Gathering | Design Documents | Scenario,Storyboard,Navigation Diagram,Prototype |
Market Research | Market Research | |
Analysis | Use case | Participant & Researcher Use Cases |
Business Process Diagram | Business Process Diagram | |
Logical Diagram | Logical Diagram | |
Testing | User Testing | User Test |
Test Plans | Test Cases |
Deployment:
We have launch our Alpha Version of our mobile application on the google playstore, the instructions for the Alpha tester to participate can be found here: Instructions to download
We have also deployed our web application to the Livelabs Web Server (Hestia), ReFokus Web Application
Testing:
Number of User Tests: 3
Tester Profile:
Our testers consist of users with research backgrounds, specifically research assistants currently pursuing their PhD in Psychology. With their experience, we were able to gain valuable feedback with regards to the creation of studies.
For more information about the user tests and the detailed results, please visit the link below:
User Test
Test Cases:
For each iteration, we have functional test cases to test individual functions. Towards the end of the iteration, we will do regression testing and go through the entire flow of the project to ensure all parts are working.
For the detailed test cases, please visit the link below:
Test Cases
For our bug metrics score, we can see that iteration 5 had an exceptionally high score. This was due to the aftermath of User Test 2 and 3, which proved to be useful for us with the functional and UI bugs spotted. Even though the bug score was well above the threshold level of 10, we managed to solve all the bugs in the scheduled debugging time.
For the detailed bug reports, please visit the link below:
Bug Metrics
Reflection
In this section, describe what have the team learn? Be brief. Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.
Team Reflection:
Any training and lesson learn? What are the take-away so far? It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.
Benjamin Gan Reflection:
You may include individual reflection if that make sense at this point. The team is uncooperative and did not follow my instructions.