Difference between revisions of "IS480 Team wiki: 2015T2 Marreo/MidtermWiki"

From IS480
Jump to navigation Jump to search
Line 200: Line 200:
|| [[IS480_Midterm_Wiki#Testing: | instructions]]
|| [[IS480_Midterm_Wiki#Testing: | instructions]]
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.
Line 207: Line 205:
We conducted two User Testing sessions thus far.<br/><br/>
We conducted two User Testing sessions thus far.<br/><br/>
User Testing 1<br/>
'''User Testing 1'''<br/>
Date: 30 Jan 2015<br/>
'''Date:''' 30 Jan 2015<br/>
10 SMU Students<br/><br/>
10 SMU Students<br/><br/>
User Testing 2<br/>
'''User Testing 2'''<br/>
Date: Early February<br/>
'''Date:''' Early February<br/>
2 married individuals<br/>
2 married individuals<br/><br/>
Find out more below:<br/>
Find out more below:<br/>

Revision as of 05:44, 25 February 2015

Marreo logo.png

Icon home.png
Icon aboutus.png
Icon projectoverview.png
Icon projectmgt.png
Icon documentation.png
About Us
Project Overview
Project Management

Banner midterm.png
Acceptance Midterm Final

Project Progress Summary

Deployed website:
Please login to the application via the link above.

Icon marreo presentation.png || Midterm Slides
Download: Marreo Midterm Powerpoint Slides

Development progress: 80%

Iteration progress.PNG Card progress.PNG

The project is going smoothly. We faced a few hiccups along the way, mainly delays in 3 iterations, and have dropped some features as a result. Details of these delays and dropping of functionalities can be found below.

Project Highlights:

Mr & Mrs (SG) has been renamed to Marry.SG

  • Need for a "Revamp" Iteration (Iteration 8) in order to tie in all coded features so far
  • Scope changes to include features for a RSVP Canvas. It is something that is analogous to a dedicated website for a couple to share with loved ones

Project Management

Development Progress and Status:

Development progress table.PNG

Project Schedule (Plan Vs Actual):

Marreo timeline v1.jpg

Timeline v2 18-2-15.png

The main changes occur from Iteration 7 onwards with a new requirement of packaging cards for an RSVP Canvas. The scope changes have been summarised below.

Old scope circle.png New scope circle.png

Project Metrics:

Delays in Schedule

Iteration 6 delay chart.png Iteration 6 delay.png

Iteration 7 delay chart.png Iteration 7 delay.png

Iteration 9 delay chart.png Iteration 9 delay.png

Bug Metrics

Bug metrics marreo.PNG Bug points.PNG

Did not face any critical bugs. Stayed within the safe zone (depicted by the red line) for all iterations.

Project Risks:

Risk Type Risk Statement Consequence Likelihood Impact Mitigation Strategy
Technical Risk Graph Paper is already live but undergoes frequent changes to the Graph Paper technology framework. These changes are made concurrently with the development of Marry.SG. 1. Functions in the Marry.SG application could become buggy.
2. Unplanned debugging time eating into tasks meant for other things during iterations. This may result in project delays.
High High 1. Communicate with client on fortnightly to keep coders updated on changes being made to Graph Paper. Alert client if time is tight and instability is causing too many setbacks. Try to work towards a solution together.
2. Have enough buffer time allocated to accommodate unplanned debugging tasks.
3. Have a set of robust test cases to ensure all possible errors and bugs can be identified.
4. Schedule stringent and frequent testing of systems during the end of all iterations to ensure that integration of new functions would not affect previously coded functions.
Operational Risk Unforeseen commitments or events of group members (E.g. Sickness, urgent family commitments, going on a holiday during term breaks, laptop not functioning) 1. Disruptions to progress
2. Project delays
Mid High 1. Review tasks and plans and make changes where possible.
2. Schedule tasks in buffer period if it is not possible to reschedule tasks to accommodate the delay.
3. Alert client if some functions cannot ready by planned time.
4. Last resort: Alert client if some functions need to be dropped.

Technical Complexity:

Card (Feature) Involved Description of Technical Complexity What is to be achieved as an end result
RSVP Card and Guest Manager Use of Web Hook to link data from two separate sources To link data from two separate canvases (data sources, one is a form and the other is a card on Graph Paper)
Wedding Day Itinerary and Contact List To export data from the two cards as a PDF document Data downloaded as a PDF
Admin Handling CSV file uploads to bootstrap data for three cards (Things to Do, Notes, Wedding Discover) via the Admin Card To bootstrap data from CSV files

Quality of product

Intermediate Deliverables:

There should be some evidence of work in progress.

Stage Specification Modules
Project Management Minutes Sponsor weeks -10 -5 3 7 Supervisor weeks -2 3 5 7
Metrics Bug metrics
Requirements Story cards CRUD Customer, Trend Analytic
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 test plan instructions


We conducted two User Testing sessions thus far.

User Testing 1
Date: 30 Jan 2015
10 SMU Students

User Testing 2
Date: Early February
2 married individuals

Find out more below:
User Testing


In this section, describe what have the team learn? Be brief. Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.

Team Reflection:

Any training and lesson learn? What are the take-away so far? It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.

Benjamin Gan Reflection:

You may include individual reflection if that make sense at this point. The team is uncooperative and did not follow my instructions.