IS480 Team wiki: 2017T1 Team Kinetic Midterm Wiki
- 1 Project Progress Summary
- 2 Project Management
- 3 Quality of product
- 4 Reflection
Project Progress Summary
|Midterm Slides||Deployed Site|
|Iteration||Scope||Module||Task||Planned/New feature?||Status||Confidence Level (0-1)||Comments|
|2||Core||Account Module||Login/Logout||Planned||Fully deployed and tested 100%||1||Reviewed and accepted by sponsor|
|2||Core||Account Module||Signup||Planned||Fully deployed and tested 100%||1||Reviewed and accepted by sponsor|
|2||Core||Account Module||User Account Settings||Planned||Fully deployed and tested 100%||1||Reviewed and accepted by sponsor|
|3||Core||Loan Initiation Module||Request New Loan||Planned||Fully deployed and tested 100%||1||Reviewed and accepted by sponsor|
|4||Core||Loan Initiation Module||Re-List loan||Planned||Fully deployed and tested 100%||1||Reviewed and accepted by sponsor|
|4||Core||Loan Search Module||Search loan with filters||Planned||Fully deployed and tested 100%||1||Reviewed and accepted by sponsor|
|5||Core||Portfolio Module||Create/Manage loan portfolio||Planned||Fully deployed and tested 100%||1||Reviewed and accepted by sponsor|
|5||Core||Fund Loan Module||Fund listed loan||Planned||Fully deployed and tested 100%||1||Reviewed and accepted by sponsor|
|6||Core||Admin Module||Default tracker||Planned||Fully deployed and tested 100%||1||Reviewed and accepted by sponsor|
|6||Core||Admin Module||Check user/loan eligibility||Planned||Fully deployed and tested 100%||1||Reviewed and accepted by sponsor|
|6||Core||Admin Module||Check available loans||Planned||Fully deployed and tested 100%||1||Reviewed and accepted by sponsor|
|7||Secondary||Funding and Repayments Module||Process Usage Fees||Planned||Fully deployed and tested 100%||1||Reviewed and accepted by sponsor|
|7||Secondary||Funding and Repayments Module||Update Collection Amount||Planned||Fully deployed and tested 100%||1||Reviewed and accepted by sponsor|
|8||Secondary||Learning Module||Hover Icon Questions||Planned||Tested and pending deployment||1||Reviewed by sponsor|
|8||Secondary||Learning Module||Pre/Post Lab Quiz||New||Tested and pending deployment||1||Reviewed by sponsor|
Project Schedule (Plan Vs Actual):
Planned Project Schedule
Actual Project Schedule
Changes In Schedule
|Iteration||Date of Schedule Revision||Change in Schedule||Reason||Mitigation|
|6||3 Sept 2017||Switched iteration 7 features (Learning Module) and iteration 8 (Payments Module)||Payments module had the higher technology risk (sponsor given payments API integration) and hence required by team to tackle earlier.||All preparation (API given by sponsor, understanding of payments API by development team) was done and team is ready to implement payments in iteration 7.|
|7||17 Sept 2017||Added new feature (pre/post lab quiz) in learning module||Sponsor request to add pre/post lab quiz to improve value proposition of KineticLoans as a learning platform. Team reviewed and accepted addition of feature||Analytics module features were pushed to iteration 9. PM and Backend team re-estimated their efforts for iteration and assigned tasks accordingly.|
|7||17 Sept 2017||AWS Deployment date was shifted from 18 Sept to 21st Sept.||Effort required for Funding and Repayments module exceeded expectations.||Team postponed AWS deployment date to 21st Sept (iteration 8) to allow completion of module|
|7||18 Sept 2017||UAT 2 date was shifted from 21 Sept to 29 Sept||Delay in deployment of application due to effort required for Funding and Repayments module||Postpone UAT to 29 Sept to allow for deployment and sufficient preparation|
Figuring out a Payments mechanism that effectively distributes respective dollar amounts to platform users (borrowers/investors) based on their active loans. In order to solve this, we need to take care of 3 components:
1. Direct Debit Authorisation
2. Loan Funding
3. Loan Repayment
1) DIRECT DEBIT AUTHORIZATION
a)What we need:
Platform must be authorised to directly debit money from borrowers and investors.
Obtain direct debit authorization from each user to allow automatic deductions during loan funding and loan repayment.
Screenshots from Kinetic Loans Application
1: Borrower/Investor enters his/her tBank details.
2: Borrower/Investor enters his/her OTP: If verification is successful, user is re-directed to the app.
2) LOAN FUNDING
a)What we need:
i) Platform must initiate a transfer from multiple investors to single borrower as soon as a loan is fully funded.
ii) Platform should deduct some transaction fees.
iii) Platform’s journal should store all future pending repayment amounts and timings.
The direct debit authorization, once completed, allows the platform to access the user’s account to make a transfer from the user’s account to the platform’s account. This authorization becomes useful when a loan is fully funded, and money needs to be passed on from the various Investor accounts, to the borrower’s account. The logic for the same is represented below:
3) LOAN REPAYMENT
a)What we need:
Automatic task scheduler should execute repayments at the correct time.
After a borrower’s loan request has been approved, and the borrower receives the amount he/she needed, the repayment process is triggered. Every day, the task scheduler checks the journal for any repayments which are due. These are automatically triggered and a repayment servlet calculates the correct proportion of the repayment amount which must be transferred to each investor.
Quality of product
|Project Overview||Project Description|
We have completed 2 user tests. Please access the details here
Over the duration of the project, the team has improved its performance in the areas of project management and application development to ensure we meet our sponsor's expectations for the KineticLoans application. We have overcome major hurdles (completion of major technology risk, delays in timeline, additional features, etc.) to ensure project success and we aim to carry forward this momentum till our finals!
Sandeep: "As PM, I realized the importance of my role in maintaining oversight of the entire team's progress in face of risks such as requirements inflation, delays in timeline, etc. I also understood that maintaining regular communication with other stakeholders (sponsor and supervisor) reduced instances of such key risks occurring in our project”
Isha: "The learning curve for front-end was a lot steeper than I expected so I had to apply what I had learnt in classes and learn fast. After overcoming the obstacle I found a beauty in being able to alter the focus of the user by the use of space and colours. I have also learned to separate my personal taste and professional opinion in order to work on designing in a team- as multiple people would have differences in opinion on aesthetic.”
Vani: "These past weeks have taught me to learn to think from a users perspective as well as a designer. Additionally, working within a time frame and around limitations caused by APIs were using. ”
Aditya: "I learnt a lot about the challenges of integrating with an external application and designing features in a way which makes it easy to maintain and deploy on different servers.”
Meher: "As Quality Assurance manager, I have learnt more about keeping track of various metrics, and the benefits of maintaining these lists. I also learnt more about different software quality assurance practices. ”