IS480 Team wiki:2015T2 Team Elements FinalWiki

From IS480
Revision as of 00:03, 10 April 2016 by Jy.thai.2013 (talk | contribs)
Jump to navigation Jump to search
Team Elements Logo.jpg

Team Elements Home.png   HOME


Team Elements AboutUs.png   ABOUT US


Team Elements PrjOverview.png   PROJECT OVERVIEW


Team Elements PrjMgmt.png   PROJECT MANAGEMENT


Team Elements Documentation.png   DOCUMENTATION

Main Wiki Midterm Wiki NavigationElements.png Final Wiki

Project Progress Summary

TE Slides Icon.jpgFinals Slides Elements Deployed Icon.jpgDeployed Site WP Postericon.JPGPoster WP Video.pngPitch Video

Project Highlights

TE Overview Highlights.png

  • Our project schedule is divided into 12 iterations.
  • Till date of 12 April 2016, we have completed 100% of our development progress. We are now left with 2 milestone (Final Presentation and Poster Day) and the last iteration (iteration 12)
  • Beta Release - The system has been released on 17 February 2015.
  • Check out our beta release here!

  • Current iteration: 12
  • Iteration 13: 13 April 2016 - 22 April 2016
  • The project has officially been handed over to Sterling Training Hub.

Development Progress

Progress: 100 % Completed Link to the Development metrics: https://docs.google.com/a/smu.edu.sg/spreadsheets/d/1M9W9tuOnP9srr3V0IeMDBQZcdv3H7c9bQ0i-TfhwkTk/edit?usp=sharing

Project Management

Project Scope

Original Final

Team Elements Scope Acceptance.jpg

FunctionalitiesScope MidTerms.png

Major Scope changes

  • Removal of online payment as requested by the sponsor

View our Change Management Here!

Project Schedule

View detailed Project Schedule here!

Planned Actual

Team Elements ProjectSchedule Planned.png

Team Elements ProjectSchedule Actual.png

Schedule Highlights

  • There are no major changes to major project milestones such as UT, UAT, deployment. However, the team added a Beta Release after the first deployment. This is to allow Sterling Taining Hub to use our system during oeprations.


Schedule Metrics

View our Schedule Metrics Here!

Elements Schedule Metrics Final.JPG
Schedule Metrics Highlights
Iteration Planned Duration (Days) Actual Duration (Days) Schedule Metric Score Action Status
4 14 17 82% The team is behind schedule.Under-estimated the effort required. Re-estimate tasks for future iterations.

Delayed due to the potential change in sponsor and the team was changing some aspects of the interface after acceptance presentation. Follow up action: Iteration 4 was delayed by 3 days. However, the following iteration started after the exam break. No buffer day is used.

10 14 19 93%

Iteration 10 was delayed by 5 days due to the change in a fundamental database structure
Follow up action: Drop functionalities for this iteration and rescheduled them to the next iteration.


Bug Metrics

View our Bug Metrics here!

Bug Score
Elements Bug Finals.png

Iteration Bug Score Summary of bugs Action Taken
4 33
2 High
There was a problem with iron router during deployment. It worked on our local host but not on the deployment server. Stop current development and resolve the bug immediately. Project Manager reschedules the project.
5 29
1 High
Meteor underwent a version change and this new version was buggy, causing compatibility issues and the application could not run. Stop current development and resolve the bug immediately. Project Manager reschedules the project.
8 33
2 High
Due to a confusion in the template names, the options at the side bar were gone Stop current development and resolve the bug immediately. Project Manager reschedules the project.
10 8
1 High
3 Low
The emails did not work and always caused an error when creating a new class. Stop current development and resolve the bug immediately. Project Manager reschedules the project.

Project Risks

Activated Risks

View our risk management here! The below table only highlights the two top risks that have been mitigated.

No Risk Description Impact Likelihood Impact Category Mitigation Plan Status
1 Sponsor changes requirements on an ad hoc basis Project schedule will be affected Medium Medium B Project Manager and Business Analyst to work with sponsor closely to monitor and modify the team plan after every iteration. Team to evaluate on a case-by-case basis Mitigated
2 Unable to get the administrators to test the system as the training facility is still being built Unable to get genuine feedback from users and hence affect the usability of the system High High A Project manager will work closely with the sponsor to source for similar training facilities and conduct observations and tests with them.

Project Manager to work closely with sponsor to plan each functions.


The above two risks has been mitigated.

  1. Risk 1: The team implemented change management plan in order to evaluate the changes requested by the client. View our Change Management Here!
  2. Risk 2: Sponsor and the team went to find through their own personal contacts and managed to gather a total of 2 other training hubs to help.

Future Risks

No Risk Description Impact Likelihood Impact Category Mitigation Plan Status
1 Future developers unfamiliar with technologies used Unable to hand over to future developers for future application enhancement High High A Provide proper documentation such as deployment guide and include comments in the codes. Mitigated

The above two risks have not occurred. However, our team anticipated the possibility of it and managed to mitigate these risks.

Technical Complexity

Generation of Certificates

  • Sterling needs to generate certificates for pupils who have completed their courses
  • Populate certs in a given format and exporting them to pdf for printing

Elements cert generation.png

  • The above image is generated from the class list

Excel Read&Write

Elements excel screenshot.png

  • For the convenience of the trainer, the trainer can download a copy of the class list into excel and use it to fill up the class' grades and attendance.
Quality of Product


Stage Specification Modules
Project Requirements Purpose and Motivation Purpose and Motivation

Market Research

Project Management Minutes Meeting Minutes
Project Management Metrics, Risks, Change

Schedule Metrics
Bug Metrics
Bug Management
Change Management

Analysis and Design DB Diagram, As-Is, To-Be Processes DB Diagram, As-Is, To-Be Processes
Design Prototype Persona and Prototype
Testing User Test Plan

Heuristic Evaluation
User Testing 1
User Testing 2
User Testing 3

Handover User Manual, Project Closure Sign Off, UAT Sign Off

User Manual Guide
UAT Sign Off
Project Closure Sign Off


Deployed Link: http://sterlingtraininghub.com/


We have conducted three user tests and one heuristic evaluation.

Heuristic Evaluation

  • Venue: Singapore Management University, School of Information Systems
  • 5 participants
  • This is to learn more about the usability of our application and improve it further in our future designs. This was conducted with a paper prototype. A paper prototype was used because we want to be able to discover UI issues early, so that the cost of changing will not be so high.

View our Heuristics Evaluation documentation here!

User Testing 1

  • Date: 10 October 2015
  • Venue: Sterling Training Hub
  • 4 Training Hub Administrators

View our UT1 documentation here!

User Testing 2

  • Date: 29 January 2016
  • Venue: Sterling Training Hub
  • 3 Sterling Training Hub administrators

View our UT2 documentation here!

User Testing 3

  • Date: 25 March 2016
  • Venue: Sterling Training Hub and web
  • 8 Sterling Training Hub Trainers, 20 Students

View our UT3 documentation here!


TE Learning Outcomes 1.pngTE Learning Outcomes 2.png