Difference between revisions of "IS480 Team wiki: 2015T2 Marreo/FinalWiki"
(Created page with "300px|center|link= <!-- START OF NAVBAR --> <div style="width:20%; float: left;">80px|center|link=</div> <div style="width:20...") |
|||
Line 37: | Line 37: | ||
<div style="text-align: left; width:1080px; margin-left:auto; margin-right:auto; "> | <div style="text-align: left; width:1080px; margin-left:auto; margin-right:auto; "> | ||
− | [[File:Marreo | + | ==<div style="background: #a158a3; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:24px"><font color= #FFFFFF> Project Progress Summary </font></div> == |
+ | |||
+ | {| | ||
+ | |- | ||
+ | | [[File:Icon marreo presentation.png| 100px]] || <b>Final Slides</b> <br/> | ||
+ | Download: [[Media:_.pdf| Marreo Final Powerpoint Slides]] | ||
+ | |} | ||
+ | <!-- | ||
+ | {| | ||
+ | |- | ||
+ | | [[File:Icon marreo video.png| 100px]] || <b>Final Video</b> <br/> | ||
+ | Video Link: | ||
+ | |}--> | ||
+ | {| style="text-align:left; width:200px; background-color:#fff; " | ||
+ | |- | ||
+ | | [[File:globe.png|30px|center|link=]] | ||
+ | | https://www.marry.sg | ||
+ | |- | ||
+ | | [[File:Facebook icon.png|30px|center|link=]] | ||
+ | | https://www.facebook.com/MarrySGOfficial | ||
+ | |} | ||
+ | <span style="font-size:150%">Development progress: <br> | ||
+ | Current Status: <b> 80% </b></span><br/><br/> | ||
+ | |||
+ | <b> Current Iteration</b> <br> | ||
+ | Iteration 11 <br> | ||
+ | Midterm Presentation <br> | ||
+ | START: 9 February 2015 <br> | ||
+ | END: 27 February 2015<br> | ||
+ | |||
+ | |||
+ | [[File:Iteration progress.PNG|500px|link=]] | ||
+ | [[File:Card progress.PNG|500px|link=]] | ||
+ | |||
+ | 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.<br/><br/> | ||
+ | |||
+ | ===Project Highlights:=== | ||
+ | <span style="font-size:150%">Mr & Mrs (SG) has been renamed to Marry.SG</span><br/> | ||
+ | {| | ||
+ | |- | ||
+ | | [[File:Mr&mrs logo black.png|100px|link=]] <br> <b><center> Mr & Mrs (SG) </center></b> | ||
+ | | | ||
+ | | <br> change to | ||
+ | | | ||
+ | | [[File:MARRYSG.PNG|100px|link=]] <br> <b><center> Marry.SG</center> </b> | ||
+ | |} | ||
+ | |||
+ | <br/> | ||
+ | |||
+ | *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 | ||
+ | <br/> | ||
+ | |||
+ | ==<div style="background: #a158a3; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:24px"><font color= #FFFFFF> Project Management</font></div> == | ||
+ | |||
+ | ===Development Progress and Status=== | ||
+ | |||
+ | [[File:Development progress table.PNG|1000px|center|link=]] | ||
+ | |||
+ | ===Project Schedule (Plan Vs Actual):=== | ||
+ | |||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | ! Planned!! Actual | ||
+ | |- | ||
+ | | | ||
+ | [[File:Marreo timeline v1.jpg|500px]] | ||
+ | || | ||
+ | [[File:Timeline_v2_18-2-15.png|500px]] | ||
+ | |} | ||
+ | |||
+ | <p>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.</p><br/><br/> | ||
+ | ===Project Scope (Plan Vs Actual):=== | ||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | ! Planned!! Actual | ||
+ | |- | ||
+ | | | ||
+ | [[File:Old scope circle.png|500px]] | ||
+ | || | ||
+ | [[File:New scope circle.png|500px]] | ||
+ | |} | ||
+ | |||
+ | |||
+ | ===Project Metrics:=== | ||
+ | <span style="font-size:150%">Delays in Schedule</span><br/><br/> | ||
+ | [[File:Iteration 6 delay chart.png|500px|link=]] | ||
+ | [[File:Iteration 6 delay.png|500px|link=]]<br/><br/> | ||
+ | |||
+ | [[File:Iteration 7 delay chart.png|500px|link=]] | ||
+ | [[File:Iteration 7 delay.png|500px|link=]]<br/><br/> | ||
+ | |||
+ | [[File:Iteration 9 delay chart.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:=== | ||
+ | |||
+ | {| class="wikitable" width="100%" | ||
+ | |- | ||
+ | ! 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. <br/> 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. <br/> 2. Have enough buffer time allocated to accommodate unplanned debugging tasks.<br/> 3. Have a set of robust test cases to ensure all possible errors and bugs can be identified.<br/> 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 <br/> 2. Project delays | ||
+ | | Mid | ||
+ | | High | ||
+ | | 1. Review tasks and plans and make changes where possible. <br/> 2. Schedule tasks in buffer period if it is not possible to reschedule tasks to accommodate the delay. <br/> 3. Alert client if some functions cannot ready by planned time. <br/> 4. Last resort: Alert client if some functions need to be dropped. | ||
+ | |} | ||
+ | |||
+ | ===Technical Complexity:=== | ||
+ | |||
+ | {| class="wikitable" width="100%" | ||
+ | |- | ||
+ | ! 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 | ||
+ | |} | ||
+ | |||
+ | ==<div style="background: #a158a3; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:24px"><font color= #FFFFFF> Quality of product </font></div> == | ||
+ | |||
+ | ===Intermediate Deliverables:=== | ||
+ | |||
+ | There should be some evidence of work in progress. | ||
+ | |||
+ | {| class="wikitable" border="1" | ||
+ | |- style="background:purple; color:white" | ||
+ | |align="center"| Stage | ||
+ | |align="center"| Specification | ||
+ | |- | ||
+ | |rowspan="4"| Project Management | ||
+ | |||
+ | || [[IS480 Team wiki: 2015T2 Marreo/Project Management|Project timeline]] | ||
+ | |- | ||
+ | |||
+ | || [[IS480 Team wiki: 2015T2 Marreo Metrics|Schedule Metrics]] | ||
+ | |- | ||
+ | |||
+ | || [[IS480 Team wiki: 2015T2 Marreo Project Scope|Project Scope]] | ||
+ | |- | ||
+ | |||
+ | || [[IS480 Team wiki: 2015T2 Marreo Project Risk|Risk & Mitigation]] | ||
+ | |- | ||
+ | |||
+ | |rowspan="3"| Project Overview | ||
+ | || [[IS480 Team wiki: 2015T2 Marreo/Project Overview|Description & X-Factor]] | ||
+ | |- | ||
+ | |||
+ | || [[IS480 Team wiki: 2015T2 Marreo Motivation|Market Research]] | ||
+ | |- | ||
+ | |||
+ | || [[IS480 Team wiki: 2015T2 Marreo Design & Prototype|Design & Prototype]] | ||
+ | |- | ||
+ | |||
+ | |rowspan="1"| Testing | ||
+ | |||
+ | || [[IS480 Team wiki: 2015T2 Marreo User Tests|User Testing]] | ||
+ | |- | ||
+ | |||
+ | |rowspan="3"| Documentation | ||
+ | |||
+ | || [[IS480 Team wiki: 2015T2 Marreo/Project Documentation|Meeting Minutes]] | ||
+ | |- | ||
+ | |||
+ | || [[IS480 Team wiki: 2015T2 Marreo Diagrams|Diagram]] | ||
+ | |- | ||
+ | |||
+ | || [[IS480 Team wiki: 2015T2 Marreo Technologies|Technologies]] | ||
+ | |- | ||
+ | |} | ||
+ | |||
+ | <h2>User Testing</h2> | ||
+ | We conducted two User Testing sessions thus far.<br/> | ||
+ | '''<h3>User Testing 1</h3>''' | ||
+ | '''Date:''' 30 Jan 2015<br/> | ||
+ | 10 SMU Students<br/> | ||
+ | <b> Goals </b> | ||
+ | *Usability | ||
+ | **All users should be able to achieve all tasks described without asking for help | ||
+ | **90% of users will be able to perform a similar task on a card in a shorter time after their first attempt | ||
+ | *Look and Feel | ||
+ | **90% of users are satisfied with the layout of the cards on the canvas i.e. cards are not too big or not too small | ||
+ | **90% of users feel that this application looks presentable and aesthetically pleasing | ||
+ | |||
+ | '''<h3>User Testing 2</h3>''' | ||
+ | '''Date:''' Early February<br/> | ||
+ | 2 married individuals<br/> | ||
+ | <b> Goals </b> | ||
+ | *Usability & Functions | ||
+ | **All users should agree that the components used are relevant and important to wedding planning | ||
+ | **All users will be able to use the tools without help from the facilitator | ||
+ | |||
+ | Find out more below:<br/> | ||
+ | [[IS480 Team wiki: 2015T2 Marreo User Tests|User Testing]] | ||
+ | |||
+ | ==<div style="background: #a158a3; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:24px"><font color= #FFFFFF> Reflection </font></div> == | ||
+ | |||
+ | |||
+ | [[File:Marreo Team Reflection (1).JPG|500px]] | ||
+ | [[File:Marreo Team Reflection (2).JPG|500px]] | ||
+ | <br> | ||
+ | [[File:Marreo Team Reflection (3).JPG|500px]] | ||
+ | [[File:Marreo Team Reflection (4).JPG|500px]] | ||
+ | <br> | ||
+ | [[File:Marreo Team Reflection (5).JPG|500px]] | ||
+ | [[File:Marreo Team Reflection (6).JPG|500px]] | ||
+ | |||
</div> | </div> |
Revision as of 14:30, 9 April 2015
Acceptance | Midterm | Final |
Contents
Project Progress Summary
Final Slides Download: Marreo Final Powerpoint Slides |
https://www.marry.sg | |
https://www.facebook.com/MarrySGOfficial |
Development progress:
Current Status: 80%
Current Iteration
Iteration 11
Midterm Presentation
START: 9 February 2015
END: 27 February 2015
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
|
change to |
|
- 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
Project Schedule (Plan Vs Actual):
Planned | Actual |
---|---|
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.
Project Scope (Plan Vs Actual):
Planned | Actual |
---|---|
Project Metrics:
Delays in Schedule
Bug Metrics
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 |
Project Management | Project timeline |
Schedule Metrics | |
Project Scope | |
Risk & Mitigation | |
Project Overview | Description & X-Factor |
Market Research | |
Design & Prototype | |
Testing | User Testing |
Documentation | Meeting Minutes |
Diagram | |
Technologies |
User Testing
We conducted two User Testing sessions thus far.
User Testing 1
Date: 30 Jan 2015
10 SMU Students
Goals
- Usability
- All users should be able to achieve all tasks described without asking for help
- 90% of users will be able to perform a similar task on a card in a shorter time after their first attempt
- Look and Feel
- 90% of users are satisfied with the layout of the cards on the canvas i.e. cards are not too big or not too small
- 90% of users feel that this application looks presentable and aesthetically pleasing
User Testing 2
Date: Early February
2 married individuals
Goals
- Usability & Functions
- All users should agree that the components used are relevant and important to wedding planning
- All users will be able to use the tools without help from the facilitator
Find out more below:
User Testing