IS480 Team wiki: 2012T2 box.us MidTerms

From IS480
Jump to navigation Jump to search

Acceptance Snapshots

Mid Terms Snapshots

Project Progress:


We are 70% through with the functionalities of our system.

Project Highlights:

What unexpected events occurred?

  • "Task" functionality took longer than expected to scope and develop
  • Re-working of User Interface
  • Drop of mobile functionalities
  • No clear defined business process initially

Project Status:

View the detailed Project Scope on Google Docs to have an understanding of our Project Status

Functions Prototyping Implemented User Tested Client Approved Confident Level Comment
Registration Completed In Progress User Testing 1 Pending 1 Completed this module.
Task Completed In Progress User Testing 1 Pending 1 Includes Task Review and Timesheet.
Questions Completed Completed User Testing 1 Pending 1 Final touchups to be done and then to subject to heuristics testing.
Search Completed Completed User Testing 2 Pending 1
Volunteer Records Completed In Progress User Testing 2 Pending 1
Feedback Form Completed In Progress User Testing 3 Pending 1 Requirements gathering completed. Left implementation to complete.
Statistics In Progress Not started User Testing 3 Pending 1 Includes the dashboard for volunteers, Empact and NPOs.
Notification In Progress Not started User Testing 3 Pending 1

Project Schedule (Plan Vs Actual):

Take a look at our Project Schedule @ Mid Terms

Snap 2013-02-21 at 03.12.35.png

Project Scope (Acceptance Vs MidTerms):

Schedule Ratio over Time Schedule Ratio over Time

Changes made

1) Added Interview Form

Enabled Empact to review through the information that was keyed in during the interview with the users

2) Added Feedback Form

Enabled volunteers to give inputs to Empact about whether the activity completed

3) Added Dashboard

Enabled users to access their information quickly Enabled Empact to view vital information about their system quickly

4) Dropped Mobile Functionalities

Mobile functionalities are a subset of the functionalities of the system Allows team to focus more on developing a good web application

Project Metrics:

Schedule Ratio over Time Bug Score over Time
  • We are generally meeting our schedule as the time goes by. Most of the delays are caused by a difference in the estimated time that is required to do each task.
  • Spike in Iteration 7 is due to the changes in the requirements of the Task components.
  • View our schedule metrics on our main wiki
  • Bug Score is in relatively stable mode along the iterations.
  • Spike in Iteration 9 due to major bugs found in the Task module. Additional time has been scheduled in Iteration 10 to fix this bug.
  • View our bug metrics on our main wiki

Project Risks:

Box.us uses a risk management plan to scan and mitigate risks that can arise. Please view the following for a view of how we manage our risks:

Our Top 3 Risks

Priority Type Risk Consequence Likelihood Impact Level Risk Assessment Level Mitigation Strategy


Underestimation of time taken to complete a module

  1. Delay in project schedule




  1. Buffer at the end of every iteration
  2. More buffer towards the end to act as contingency buffer in between iterations


Higher than expected number of issues raised during testing(s)

  1. Delay in project schedule
  2. Changes may affect the system or scope"




  1. Change Management process to help evaluate whether the change is necessary


Business process of client is not clearly defined, leading to constant changes in the business process and design of the system

  1. Re-doing of system design that leads to unnecessary work
  2. Delay in Schedule




  1. Client meeting at the start of iteration to be adopted and it would be able to include the review for the next iteration
  2. Require client to do up the business process diagram in order to allow client to think through the entire process.
  3. Prototyping process to let the client have a better idea of the end-product and what are the fields that would be necessary to capture within the system

Lessons Learnt from Managing Risks

Risk Management helps us to predict risk early and make necessary changes to the team even before the actual event happens.

  1. Issue Log has helped the team to have a systematic way of tracking the risks that can arise during the interactions between the team and between the meeting.
  2. Prototyping process has helped the team to visualize the end product early, but it also served as a communication tool between the different stakeholders in the project.

There should be some evidence of work in progress.

Stage Specification Modules
Project Management Minutes Meeting Minutes
Iteration Reports

The iteration reports covers the bug ratios and schedule ratios for each iteration.

Change Management Change Log on Google Docs
Issue Tracking Issue Tracking on Google Docs
Project Schedule Project Schedule on Google Docs
Requirements Prototyping Process Prototyping
Analysis Use case Use Case Diagram
Business Process Diagram Process Diagrams
Design ERD Diagrams V1,V2,V3,V4,V5
Testing User Testing 1 Test Plans Test Plans used
Heuristic Evaluation User Scenarios User Scenarios used
Integration Testings Integration Testings

System Architecture diagram

Instructions on how to access the system

  1. Go to Empact's VOMA
  2. Log in with the provided credentials (Will be shown only during the presentation)
  3. Have fun!

Heuristics Evaluation 1

Heuristics Evaluation 1

We conducted our 1st Heuristic Evaluation where we get our SIS experts, that is those who have taken or are currently taking Interaction Design and Prototyping (IS306) to critique and evaluate the usability issues of our web application.

User's feedback

  1. "Log in was easy"
  2. "More confirmation message needed"
  3. "Question UI is good"
  4. "It can be even more intuitive"

For Further Actions

  1. No actions taken yet!
  2. Actions will be taken after our mid terms presentation

Check out our Heuristics Evaluation 1 wiki

Heuristics Evaluation User Scenarios

User Testing 1

User Test 1

We conducted our 1st user testing to try out the new features and at the same time to also test how would the users respond to the system. Until then, there was no information about how would the different users react to the system.

Interesting Findings

  1. Questions module was not intuitive enough
  2. Task matching results could displayed in a more interactive way

Actions Taken

  1. Touched up Question module
  2. Finalized a user interface template
  3. Revamped the entire structure of how the Task module was being managed.

Check out our User Testing 1 wiki

Upcoming User Testings
  1. User Testing 2: 26 February 2013
  2. User Testing 3: 19 March 2013

Team Reflection:

Managing Change

  • Change Management - A documented and ordered Change Management process to ensure that the interests of both parties are being captured.
  • Issue Tracking - Tracking the many issues that are being raised by different stakeholders during the meetings
  • Business Process diagram - Using these diagrams were effective in ensuring that every stakeholder is on the same page and have the same understanding
  • Prototyping Process - Challenged the assumptions of all stakeholders about how the end system would look like and reduced the cost of changing the system at the start

Managing People

  • Integrate with one another - Because we came from 2 very diverse groups with very different way of working and understanding of the project, there were much conflicts that had to be resolved at the start of the FYP.
  • Optimizing the strengths and weakness of members - Made a change of role during the middle of the project because we realized that some roles could be better played by one person and other roles better played by another person.
  • Communication - This is the foremost important team that the team always seek to improve with the client

Individual Reflection

Kevin-Reflection.jpg Sherrie-Reflection.jpg BK-Reflection.jpg Jenzus-Reflection.jpg Waimun-Reflection.jpg Jervenne-Reflection.jpg