Difference between revisions of "IS480 Team wiki: 2016T2 Team VI Midterm Wiki"
Jump to navigation
Jump to search
Our team spent a large amount of time dissecting the database to fit the business rules of the enrichment centre.
Site went live and has been deployed to the enrichment center.
Able to successfully send SMS and email notification to parents upon successfully marking student's attendance.
Conducted A/B Testing which gave us the go ahead to choose Version B as our user interface for parents portal.
Embarked on Gamification and Analytics for the enrichment center.
Line 40: | Line 40: | ||
==<div style="background: #134E84; padding: 15px; font-weight: bold;text-indent: 15px;letter-spacing:-0.08em"><font color=#fbfcfd face="Helvetica">OUR PROJECT PROGRESS</font></div>== | ==<div style="background: #134E84; padding: 15px; font-weight: bold;text-indent: 15px;letter-spacing:-0.08em"><font color=#fbfcfd face="Helvetica">OUR PROJECT PROGRESS</font></div>== | ||
− | + | [[Media:.pdf|<h3>Team VI Mid Term Slides</h3>]] | |
− | Deployment Link | + | <h3>Deployment Link</h3> |
− | <h3>Summary of Project</h3> | + | <h3>Summary of Project Progress</h3> |
− | Our project iteration has 15 iterations. As at 18 February 2015, we are currently in | + | Our project iteration has 15 iterations. As at 18 February 2015, we are currently in <b>Iteration 11</b> of the project. |
− | <h3>Our | + | <h3>Project Highlights</h3> |
+ | <li>Our team spent a large amount of time dissecting the database to fit the business rules of the enrichment centre. | ||
+ | <li>Site went live and has been deployed to the enrichment center. | ||
+ | <li>Able to successfully send SMS and email notification to parents upon successfully marking student's attendance. | ||
+ | <li>Conducted A/B Testing which gave us the go ahead to choose Version B as our user interface for parents portal. | ||
+ | <li>Embarked on Gamification and Analytics for the enrichment center. | ||
==<div style="background: #134E84; padding: 15px; font-weight: bold;text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#fbfcfd face="Helvetica">OUR PROJECT MANAGMENT</font></div>== | ==<div style="background: #134E84; padding: 15px; font-weight: bold;text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#fbfcfd face="Helvetica">OUR PROJECT MANAGMENT</font></div>== | ||
− | <h3>Project | + | <h3>Project Status</h3> |
+ | {| class="wikitable" style="margin: auto;width:80%; text-align:center; background: white;" | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Task/Function/Feature | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Status | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Confidence Level (0-1) | ||
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Comment | ||
+ | |- | ||
+ | | Deploy onto Digital Ocean | ||
+ | | Our application is currenly deployed on OpenShift and our team is exploring how to deploy the application onto the DigitalOcean Server. | ||
+ | | 0.9 | ||
+ | | Sponsor requested for the team to deploy the application to Digital Ocean instead of the original Amazon Web Service (AWS). This is because our sponsor has the relevant experience and it would facilitate the process of future updates of the system. | ||
+ | |- | ||
+ | |} | ||
+ | <br> | ||
+ | <h3>Project Schedule</h3> | ||
{| class="wikitable" style="margin: auto;width:50%; text-align:center; background: white;" | {| class="wikitable" style="margin: auto;width:50%; text-align:center; background: white;" | ||
! style="background: #134E84; color: white; font-weight: bold; width:50px" | Planned | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Planned | ||
Line 63: | Line 82: | ||
The full Change Management Log can be found [[IS480_Team_wiki:_2016T2 Team VI Change Management|here]]. | The full Change Management Log can be found [[IS480_Team_wiki:_2016T2 Team VI Change Management|here]]. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<h3>Metrics</h3> | <h3>Metrics</h3> | ||
<h4>Schedule Metric</h4> | <h4>Schedule Metric</h4> | ||
Line 96: | Line 104: | ||
<h4>Bug Metrics</h4> | <h4>Bug Metrics</h4> | ||
− | [[Image:Screen_Shot_2016-02-14_at_2.09.58_pm.png|500px|center]] | + | {| class="wikitable" style="margin: auto;width:80%; text-align:center; background: white;" |
− | [[Image:Bug_Count.png|500px|center]]<br> | + | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Bug Metrics |
+ | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Bug Count by Category | ||
+ | |- | ||
+ | | [[Image:Screen_Shot_2016-02-14_at_2.09.58_pm.png|500px|center]] | ||
+ | | [[Image:Bug_Count.png|500px|center]] | ||
+ | |- | ||
+ | |} | ||
+ | <br> | ||
+ | |||
{| class="wikitable" style="margin: auto;width:80%; text-align:center; background: white;" | {| class="wikitable" style="margin: auto;width:80%; text-align:center; background: white;" | ||
! style="background: #134E84; color: white; font-weight: bold; width:50px" | Iteration | ! style="background: #134E84; color: white; font-weight: bold; width:50px" | Iteration |
Revision as of 18:12, 18 February 2016
HOME |
Final Wiki
|
OUR PROJECT PROGRESS
Team VI Mid Term Slides
Deployment Link
Summary of Project Progress
Our project iteration has 15 iterations. As at 18 February 2015, we are currently in Iteration 11 of the project.
Project Highlights
OUR PROJECT MANAGMENT
Project Status
Task/Function/Feature | Status | Confidence Level (0-1) | Comment |
---|---|---|---|
Deploy onto Digital Ocean | Our application is currenly deployed on OpenShift and our team is exploring how to deploy the application onto the DigitalOcean Server. | 0.9 | Sponsor requested for the team to deploy the application to Digital Ocean instead of the original Amazon Web Service (AWS). This is because our sponsor has the relevant experience and it would facilitate the process of future updates of the system. |
Project Schedule
Planned | Actual |
---|---|
The full Change Management Log can be found here.
Metrics
Schedule Metric
Highlights of Schedule Metrics
Iteration | Planned (Days) | Actual (Days) | SM Score | Action | Status |
---|---|---|---|---|---|
iteration | planned | actual | % | description | Completed |
Bug Metrics
Bug Metrics | Bug Count by Category |
---|---|
Iteration | Bug Score | Number of Issues | Summary of Bugs and Issues | Action Taken |
---|
Project Risks
Category | Description | Likelihood | Impact | Mitigation |
---|---|---|---|---|
Project Management | High | High | ||
Technology | Medium | High | To duplicate a copy |
The risks above have been managed and mitigated.
Technical Complexity
Technical Complexity 1: Rescheduling
Deliverables
Type | Description | Documentation |
---|---|---|
Requirement Gathering | Market Research | Market Research |
Project Management | Minutes, Metrics, Risks, Change |
Meeting Minutes |
Analysis and Design | Use Case, ER Diagram, Technology and Tools Used | Use Case & ER Diagram |
Analysis and Design | Architectural Diagram, Technology and Tools Used | Architectural Diagram & Technology and Tools Used |
Design | Prototype | |
Testing | User Test Plan | Test Plan |
OUR QUALITY ASSURANCE
User Testing
Objective:
- Gather feedback from students in SMU
- Identify usability issues based on observations
- Improve web application based on user testing results
- Identify potential bugs that was not found during testing phase
- Testing of functionality
Users: 15 SMU Students, 4 IT Consultant, 1 Digital Marketing Consultant
Venue: SMU , FYP Labs, Starbucks at Parkway
Date: 4,5,6 Feb 2016
Duration: 20 Minutes / User
>Scope of User Testing 2
- Branch Manager to successfully create a Parent and Student.
- Branch Manager to create a schedule, and assign the student into a class
- Teacher to mark the attendance of a student using the QR code
- Teacher to create a feedback for the student
- Parents to edit their own and child's information/li>
- Parents to successfully receive an SMS, Email when their children has attended lesson
- Parents to view the feedback given to their children by their teachers
User Testing 2 Focus Group:
- Branch Manager
- Parent
- Teacher
User Testing 2 Results
Likes | Dislikes | |
---|---|---|
|
| |
|
|
AB Testing
Objective:
- Compare two version of the web portal and identify the preferred version
- Users to perform the task of viewing the students feedback
- Improve aesthetics of web application Participants Demographics:
- 10 Actual Parents from the center Experiment Design :
Version A | Version B |
---|---|
Feedback is appended at the bottom after selection of each feedback. Users have to scroll up and down to view the feedback. | Feedback is displayed in tabs. Can only view one feedback at a time |
Results For AB Testing can available at: AB Testing Results