IS480 Team wiki: 2016T1 CLEBS Mid-Term
HOME |
Project Progress Summary
Midterm Slides: <LINK>
Deployed Site Link: http://ybcosg.herokuapp.com/
Project Highlights:
What was achieved from Acceptance?
- Completion of our most major iteration
- Project Creation Module (Iteration 5) was completed and users, after having their project proposal accepted, are able to create their projects
- Achieved X-Factor
- 20 Users Sign Up
- 20 Project Proposal Created
What unexpected events occurred?
- Changes to Project Scope and Timeline
- Sponsor experienced difficulty in setting up a BrainTree account and asked to push the Payment Gateway Module back
- Replaced Payment Gateway Module with Admin Dashboard Module
- Delay in Iteration 5
- Team had multiple other commitments to juggle
- Team were unfamiliar with the implementation of JQuery and JavaScript, and as a result, constantly
- Sponsor added changes they would like to see in the Project Creation page
Project Management
Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.
Project Status:
Planned Project Scope:
Actual Project Scope (With Changes):
Project Schedule (Plan Vs Actual):
Planned Schedule:
Actual Schedule:
Project Metrics:
Summary of analysis for the metrics collected. You may refer to another page for the details about the metrics and how it is collected.
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.