Difference between revisions of "IS480 Team wiki: 2014T1 One Piece Project Midterm Wiki"
Hphyu.2011 (talk | contribs) |
Hphyu.2011 (talk | contribs) |
||
Line 270: | Line 270: | ||
===Project Schedule (Plan Vs Actual):=== | ===Project Schedule (Plan Vs Actual):=== | ||
− | [[File:PlanVsActual OnePieceV2.jpg| | + | [[File:PlanVsActual OnePieceV2.jpg|1000px]] |
<!-- 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. | <!-- 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.--> | 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.--> | ||
− | + | *<b>Change 1 </b> | |
+ | Two of our team member's laptops broke down one after another at the start and middle of iteration 6 which is school week 3 and 4. One member took 3 days and another member took 2 days to get back a working laptop. At first, project manager reallocated the resources with different assign not the effect the project progress. However, since two incidents occur one after another, our team decided to expand the iteration duration by 4 days. | ||
+ | <br> | ||
+ | <br> | ||
+ | *<b>Change 2 </b> | ||
+ | After resolving the laptop break down issue, the team was determined to catch up with delay. Unfortunately, we made careless mistakes in committing files to GitHub and it had messed up and effected seriously in our integration stage. Since other mid term tests and presentations are around the corner, the team timetable was so tight and not able to work day and night to resolve the integration issue and prepare for UATs (SMU and Client). Besides, the team do not want to compromise the preparation time for mid term as well. So, we decided to work harder in week 8 (recess week) and extend the iteration by 5 days. | ||
===Project Metrics:=== | ===Project Metrics:=== |
Revision as of 21:06, 2 October 2014
BPAcademy is to enable online training
for corporate employees and increase efficiency in organizations
by ensuring compulsive learning.
Back to Home Page |
WORKING IN PROGRESS PAGE!
Contents
Project Progress Summary
Our project schedule is divided into 12 iterations.
- Till date of 2 September 2014, we have completed ...... of our project
- Five user testings have been conducted.
- Two usability testings with school mates
- One user validation testing with clients
- One functionality testing with clients
- One functionality A/B testing with school mates
- Next Iteration - Iteration 8 (2 October - 30 October)
- Midterm slides: [[Media:| Midterm Presentation Slides]]
- Deployed site link:
Notes:
Project Highlights:
- Team members are busy with other school commitments and events such as career recruitment talk, CCA responsibility and job applications.
- Text Editor and Impressify JS technical complexity is more sophisticated than expected and take way longer.
- Aniket's laptop died on 5 September. He bought a new one. (Iteration 6) Luckily, it did not seriously effect the project progress.
- MiMi's laptop died before acceptance and bought a new one. Unfortunately, her new laptop stopped functioning on 23 September (Iteration 7).
It effects the development of super admin module.
- List of major requirement changes (Suggested by client, supervisor and member)
- Optional hint feature for quiz
- Individual question weightage of the quiz
- Timer feature disabled after 24 hrs of of first quiz attempt
- Display and edit users/user groups without searching
- Schedule publish/recall
- Time stamp for quiz attempts
Project Management
Project Status:
Primary
Task/function/features, etc | Status | Confident Level(0-1) | Comment | UI Link (If Available) |
---|---|---|---|---|
Validate Access and direct to the respective platform | Deployed and tested 100% | 1 | Chenguang & Ila | |
Upload slides with Apache POI and store in the database | Deployed and tested 100% | 1 | MiMi | |
Create/Modify module details and access rights with validation. | Deployed and tested 100% | 1 | Aniket & Chenguang | |
Preview uploaded/Modified slides with Impressify | Deployed and tested 100% | 1 | Ila | |
Publish/Recall modules to/from the trainee platform | Deployed and tested 100% | 1 | Chenguang & Ila | |
CRUD of timer feature with respective slides | Deployed and tested 100% | 1 | Chenguang & Ila | |
CRUD of checkpoint feature (Learning Interactive Feature) | Tested 100% | 1 | Chenguang & Ila | |
View and delete created module/quizzes | Deployed and tested 100% | 1 | Mi Mi & Phyu Phyu | |
Search feature by multiple parameter and sorting feature by columns for Trainer homepage | Implemented and tested 100% | 1 |
|
|
CRUD of take quiz with min Pass/Fail restriction | Deployed and tested 100% | 1 | Mi Mi and Chenguang | |
Assign question weightage in create and edit quiz | Deployed and tested 100% | 1 |
|
|
View pending/completed modules and new quizzes | Deployed and tested 100% | 1 | Aniket | |
Search feature by multiple parameter and sorting feature by columns for Trainee homepage | Deployed and tested 100% | 1 | Aniket | |
Take Module feature by Trainee | Deployed and tested 100% | 1 | Aniket | Click Here |
Take/Retake quizzes online and review performance status | Deployed and tested 100% | 1 | Aniket |
Secondary
Task/function/features, etc | Status | Confident Level(0-1) | Comment | UI Link (If Available) |
---|---|---|---|---|
CRUD of user groups and single user | Deployed and tested 100% | 1 | Siddhant & Mi Mi | |
Upload .csv files to add multiple users and users group | Deployed and tested 100% | 1 | Siddhant & Mi Mi | |
Optional and Mandatory names for editing of single users | Implemented and tested 100% | 1 |
|
|
Display and edit usergroups without searching in Super Admin Module | Implemented and tested 100% | 1 |
|
|
Scale/Rotate/Zoom/3D features for text editor modules | Task after mid term | 1 | Ila | |
Transition path feature for text editor module | Task after mid term | 1 | Ila | |
Text enhancing features | Task after mid term | 1 | Ila | |
CRUD of audio/video files | 40% | 1 | Chenguang & Ila | |
Add/Edit Additional slide contents | 40% | 1 | ||
View trainee performance statistic by different categories and combination | Task after mid term |
Additional
Task/function/features, etc | Status | Confident Level(0-1) | Comment | UI Link (If Available) |
---|---|---|---|---|
Generate defaulted trainee overview report | Task after mid term | 1 |
Project Schedule (Plan Vs Actual):
- Change 1
Two of our team member's laptops broke down one after another at the start and middle of iteration 6 which is school week 3 and 4. One member took 3 days and another member took 2 days to get back a working laptop. At first, project manager reallocated the resources with different assign not the effect the project progress. However, since two incidents occur one after another, our team decided to expand the iteration duration by 4 days.
- Change 2
After resolving the laptop break down issue, the team was determined to catch up with delay. Unfortunately, we made careless mistakes in committing files to GitHub and it had messed up and effected seriously in our integration stage. Since other mid term tests and presentations are around the corner, the team timetable was so tight and not able to work day and night to resolve the integration issue and prepare for UATs (SMU and Client). Besides, the team do not want to compromise the preparation time for mid term as well. So, we decided to work harder in week 8 (recess week) and extend the iteration by 5 days.
Project Metrics:
Project Risks:
Technical Complexity:
Quality of product
Intermediate Deliverables:
There should be some evidence of work in progress.
Stage | Specification | Modules |
Project Management | Meeting Minutes | Client, supervisor & team meetings |
Metrics | Schedule & bug metrics (Iteration 1 - 7) | |
Requirements | Paper Prototype (Lo Fi) & Improved Prototype (Hi Fi) | Prototype |
Analysis | Use case | overall |
System Sequence Diagram | client, server | |
Business Process Diagram | Here | |
Screen Shots | CRUD Customer, Trend Analysis | |
Design | ER Diagram | 1, 2, 3 |
Class Diagram | 1, 2, 3 | |
Testing | User Testings | User test plan |
Not all parts of the deliverables are necessary but the evidence should be convincing of the progress. Try to include design deliverables that shows the quality of your project.