IS480 Team wiki: 2015T1 Hexa Midterm Wiki
Project Progress Summary
View our deployed I-Wealth Web Application here
View our midterms presentation slides here!
Project Proposal
To understand more about our scope of, click here to read about our project description!
Current Iteration 9: 21 Sept 2015 to 9 Oct 2015
- Till date 2 Oct 2015, we have completed 90% of our project
- Next iteration starts on 12 Oct 2015
- Completed all core modules to be available for Web Beta Release
- All core modules except Social Module to be available for Mobile Beta Release
Project Highlights:
- Steep learning curve
- More use-cases identified during development phase.
- Team members too busy with other work
- List of requirement changes
- Change in data visualization libraries after acceptance for some functions. i.e Chart.js to d3.js to display stacked graphs for loan calculator comparisons.
- Financial Education Module added
- Retirement Planning Calculator added under Manage Personal Finance Module
- Completed 3 UT tests with a total of 50 users.
Milestones Completed
- Proposal Submission
- User Test 1
- User Test 2
- Web Release 1
- Mobile Release 1
- Sponsor Seminar event
Milestones Remaining
- Midterms
- Web Release 2
- Mobile Release 2
- User Test 4
- Final Web and Mobile Release
- Final Presentation
- Poster day
Project Management
Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.
Project Status:
Project Schedule (Plan Vs Actual):
Summary of Planned vs Actual Schedule
Schedule Changes
- Change 1:
- Change 2:
- Change 3:
- Change 4:
- Change 5:
Scope Changes
Project Metrics:
Schedule Metrics
Click here for details on how we calculate our schedule metrics and what are the respective plans of action to take when necessary.
Task Metrics
Click here for details on how we calculate our task metrics and what are the respective plans of action to take when necessary.
Bug Metrics
Click here for details on how we calculate our bug metrics and what are the respective plans of action to take when necessary.
Iteration 5
- Only 1 high severity bug for Milestones Module
- The rest were 10 low severity bugs that was fixed during buffer period
Iteration 8
- 3 high severity bugs – new users were not able to update database when they navigate from the homepage
- Due to changes made to the database
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.
Individual Reflection:
You may include individual reflection if that make sense at this point. The team is uncooperative and did not follow my instructions.