HeaderSIS.jpg

IS480 Team wiki: 2016T2 Team VI Midterm Wiki

From IS480
Revision as of 08:39, 19 February 2016 by Huiqi.ong.2013 (talk | contribs)
Jump to navigation Jump to search
Team VI Logo.PNG


HOME

 

ABOUT US

 

PROJECT OVERVIEW

 

PROJECT MANAGEMENT

 

DOCUMENTATION

 

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 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.

    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 on how to deploy the application onto the DigitalOcean Server after the MId Terms. 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
    Team VI Project Schedule.png Actualschedule.png

    The full Change Management Log can be found here.

    Metrics

    Schedule Metric

    Team VI Schedule Metrics Graph.png

    Highlights of Schedule Metrics

    Iteration Planned (Days) Actual (Days) SM Score Action Status
    5
    14 18 78% Underestimated time required, PM to re-estimate tasks for future iterations. Delayed due to bugs found. Team was unfamiliar with QR code scanning and email notification. Reduced 4 Days of Finals Break Completed
    9
    14 20 70% Underestimated time required, PM to re-estimate tasks for future iterations. Delayed due to the database changes required to mimic the business rules, wherey timeslot is not course unique and a teacher is able to teach more than 1 courses at the same time. Use 6 buffer days. Completed

    Bug Metrics

    Bug Metrics Bug Count by Category
    Screen Shot 2016-02-14 at 2.09.58 pm.png
    Bug Count.png


    Iteration Bug Score Number of Issues Summary of Bugs and Issues Action Taken
    3
    30
    20 Low Impact Bugs & 2 High Impact Bugs Most bugs are due to validation errors. Developers stopped all current development and resolve the bugs.

    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

    Team VI Technical Complexity 1.png
    Team VI Technical Complexity 2.png
    Team VI Technical Complexity 3.png

    Technical Complexity 2: Database Structure

    Before After
    Team VI Technical Complexity 4.png
    Team VI Technical Complexity 5.png

    Deliverables

    Type Description Documentation
    Requirement Gathering Market Research Market Research
    Project Management Minutes, Metrics, Risks, Change

    Meeting Minutes
    Schedule & Effort Metrics
    Bug Metrics
    Risk Management
    Change Management

    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
    User Interface
    • Easy to Navigate
    • Users found it intuitive and could know exactly where to click
    • Application is useful for business owner
    • Yellow Colour theme too bright for some users
    Functionality
    • Creating of respective users are straightforward
    • Viewing of users are easily accessible by users
    • Creation of schedule is useful and easy for administrator and teacher
    • Marking Attendance with QR code is very interesting
    • SMS and email idea are very parent-centric, and parents will be more involved and aware of what is happening in the enrichment enter
    • Editing of parent details are easy
    • Should have a dropdown of NRIC for the administrator to choose from
    • Didn't like how we must create a diagnostic record in order to assign the student to a schedule
    • Results should be in A,B,C format instead of numerical
    • Have to remember the exact schedule event to assign the student to the schedule

    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
      VersionA.png
      VersionB.png
      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

      TEAM REFLECTIONS

      Team VI Mid Term Slides