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

From IS480
Jump to navigation Jump to search
Line 88: Line 88:
[[File:Iteration 9 delay.png|500px|link=]]
[[File:Iteration 9 delay.png|500px|link=]]
<span style="font-size:150%">Bug Metrics</span><br/><br/>
[[File:Bug metrics marreo.PNG|500px|link=]]
[[File:Bug points.PNG|500px|link=]]<br/>
Did not face any critical bugs. Stayed within the safe zone (depicted by the red line) for all iterations.<br/>
===Project Risks:===
===Project Risks:===
Update the proposal assumptions and risks. Describe what you learn from the risk update and mitigation steps taken.
{| border="1"
{| border="1"

Revision as of 05:13, 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 Probability Impact Mitigation
Sponsor want to use Joomla instead of Drupal High High Team evaluating Joomla to write an impact analysis report
Sponsor deployment machine approval and support High Medium (now it is low) Use UPL machine

Be sure to prioritize the risks.

Technical Complexity:

Describe and list the technical complexity of your project in order of highest complexity first. For example, deploying on iPhone using Objective-C, customizing Drupal with own database, quick search for shortest flight path, database structure, etc.

Quality of product

Provide more details about the quality of your work. For example, you designed a flexible configurable system using XML.config files, uses Strategy Design Pattern to allow plugging in different strategy, implement a regular expression parser to map a flexible formula editor, etc.

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

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.


In an iterative approach, ready to use system should be available (deployed) for client and instructions to access the system described here (user name). If necessary, provide a deployment diagram link.


Describe the testing done on your system. For example, the number of user testing, tester profile, test cases, survey results, issue tracker, bug reports, etc.


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.