IS480 Team wiki: 2015T1 Hexa Final Wiki
- 1 Project Progress Summary
- 2 Project Management
- 2.1 Project Status:
- 2.2 Project Schedule (Plan Vs Actual):
- 2.3 Project Metrics:
- 2.4 Project Risks:
- 2.5 Technical Complexity:
- 3 Quality of product
- 4 Reflection
Project Progress Summary
To understand more about our scope of, click here to read about our project description!
Current Iteration 12: 23 Nov 2015 to 3 Dec 2015
- Till date 22 Nov 2015, we have completed 100% of our project
- Completed all modules to be available for Web Release and Mobile Release
- Steep learning curve
- More use-cases identified during development phase.
- Team members too busy with other work
- Attended Sponsor's seminar to market I-Wealth to public.
- 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 4 UT tests with a total of 70 users.
- Proposal Submission
- User Test 1
- User Test 2
- User Test 3
- User Test 4
- Web Release 1
- Mobile Release 1
- Sponsor Seminar event
- Web Release 2
- Mobile Release 2
- Poster day
Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.
Project Schedule (Plan Vs Actual):
Summary of Planned vs Actual Schedule
- Change 1: Admin Module (CRUD Users) shifted from Iteration 6 to Iteration 7 due to lack of time as we identified more use-cases than planned.
- Change 2: Manage Personal Finance Module (CRUD Insurances) shifted from Iteration 7 to Iteration 8 as there were too many tasks in Iteration 7.
- Change 3: Admin Module (Statistics of Community) and User Profile Module (Export PDF Report) shifted from Iteration 8 to Iteration 10. This was because of new additions of tasks in Iteration 8.
- Change 4: User Test 3 was pushed earlier to Iteration 9 from Iteration 10. This is to test our application once more before Mid-terms presentation.
- Change 5: Financial Health Module (Predictive Analysis of Credit Worthiness) shifted from Iteration 9 to Iteration 11. This is an Optional function. As new higher priority features were added, this optional task was pushed to a later iteration.
- Change 1: Added new tasks
- Change 2: Removed optional functions and modules tasks
Click here for details on how we calculate our schedule metrics and what are the respective plans of action to take when necessary.
Click here for details on how we calculate our task metrics and what are the respective plans of action to take when necessary.
Click here for details on how we calculate our bug metrics and what are the respective plans of action to take when necessary.
- 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
Click here to see how we identify risks, decide on the risk levels and action plans to take when necessary.
These are our top 3 risks:
|Risk Type||Risk Description||Impact||Likelihood||Impact||Category||Mitigation Plan||Status|
|Project Requirement Risk||Sponsor adding new functionality on ad-hoc basis||Project schedule will be affected and team has to brainstorm on solution to achieve end goal of Sponsor's request||High||Medium||A||Communicate and discuss with sponsor to negotiate scope, timeline and resources.||Mitigated|
|Project Development Risk||Mobile Development encounters unforeseeable issues due to Ionic Framework even though both Web and Mobile utilizes AngularJS.||Delay in development progress||Medium||High||A||Mobile Developer to communicate with Web Developers to highlight issues that are appearing on Mobile and not Web dev to prevent same issue from arising again.||Mitigated|
|Project Overall Risk||Members falling sick at the same time||Unable to complete tasks in time||Low||Medium||C||PM to re-assign tasks if members are completely incapable of completing tasks or activate buffer days.||Mitigated|
Linking Data Fields Across Modules
- Different modules have different functions but all functions manipulate the same data field.
- This leads to the next issue of having many use cases that we have to consider for.
Converting Web codes to Mobile Framework
- Due to the large number of functionalities, we used Ionic to develop a Mobile application
Tracking of friendships and requests in database
- In the social module, users are allowed to add friends, accept friend requests and be friends with other users.
- Multiple users' records and different data tables
- Below shows how data tables are updated for a friend request to be successfully accepted.
Quality of product
|Project Management||Minutes||Meeting Minutes for Internal, Sponsor, Supervisor Meetings|
|Requirements||Story cards||Project Motivation, Scenario Storyboard|
|Analysis||Use case||Use Case Diagram|
|Architecture Diagram||Architecture Diagram|
|Prototype Designs||Prototype Designs|
|Testing||Heuristic Evaluation Tests||HE1, HE2|
|User Tests||UT1, UT2, UT3, UT4|
|Internal Testing||Internal Test Documents|
|Project Closure Documents||Project Closure Agreement||Project Closure Agreement Document|
|User Guide Manual||User Manual Guide|
|User Test||Date of User Test||Objectives||No of Participants||Link|
|User Test 1
||13/08/2014 to 14/08/2014||
||10 (Age range 18 - 35)||User Test 1|
|User Test 2
||17/09/15 3:00 pm - 20/09/15 11:59 pm||
||20||User Test 2|
|User Test 3
||06/10/15 9:00 am - 08/10/15 01:00 am||
||20||User Test 3|
|User Test 4
||06/10/15 9:00 am - 08/10/15 01:00 am||
||22 (web) and 10 (mobile)||User Test 4|
During the development of I-Wealth, the team has been exposed to more financial knowledge such as Financial Ratios and the impact of managing one's wealth.
Not only that, we learned about each other's working styles and learned to maximise our potential through understanding and adjusting accordingly to one other's styles. For example, Mon and Izzuddin likes to work in the morning, while Winnie and Zu Cheng prefers working at night. So, knowing that we know when to expect a task to be completed.
As a team, during development we utilized a framework called Ionic Framework for our mobile application that is not found in the Wiki Knowledge base. Hence, our team has contributed to the knowledge base for Ionic Framework.