Difference between revisions of "IS480 Team wiki: 2015T2 Marreo/MidtermWiki"
Line 45: | Line 45: | ||
Download: [[Media:Marreo AcceptancePresentation.pdf| Marreo Midterm Powerpoint Slides]] | Download: [[Media:Marreo AcceptancePresentation.pdf| Marreo Midterm Powerpoint Slides]] | ||
− | <span style="font-size:150%">Development progress: | + | <span style="font-size:150%">Development progress: 80%</span><br/><br/> |
[[File:Iteration progress.PNG|500px|link=]] | [[File:Iteration progress.PNG|500px|link=]] | ||
Line 78: | Line 78: | ||
===Project Metrics:=== | ===Project Metrics:=== | ||
+ | <span style="font-size:150%">Delays in Schedule</span><br/><br/> | ||
+ | [[File:Iteration 6 delay chart.png|link=]] | ||
+ | [[File:Iteration 6 delay.png|700px|link=]]<br/><br/> | ||
+ | |||
+ | [[File:Iteration 7 delay chart.png|link=]] | ||
+ | [[File:Iteration 7 delay.png|700px|link=]]<br/><br/> | ||
+ | |||
+ | [[File:Iteration 9 delay chart.png|link=]] | ||
+ | [[File:Iteration 9 delay.png|700px|link=]]<br/><br/> | ||
− | |||
===Project Risks:=== | ===Project Risks:=== |
Revision as of 04:50, 25 February 2015
Acceptance | Midterm | Final |
Project Progress Summary
Deployed website:
http://www.marry.sg
Please login to the application via the link above.
|| Midterm Slides
Download: Marreo Midterm Powerpoint Slides
Development progress: 80%
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:
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 Metrics:
Delays in Schedule
Project Risks:
Update the proposal assumptions and risks. Describe what you learn from the risk update and mitigation steps taken.
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.
Deployment:
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.
Testing:
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.
Reflection
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.