IS480 Team wiki: 2017T1 Team Kinetic Final Wiki
Project Progress Summary
Finals Slides | Deployed Site |
---|---|
Project Highlights:
Project Challenges:
Project Achievements:
Project Management
Project Status:
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 | Fully deployed and tested 100% | 1 | Reviewed by sponsor |
8 | Secondary | Learning Module | Pre/Post Lab Quiz | New | Fully deployed and tested 100% | 1 | Reviewed by sponsor |
9 | Secondary | Analytics Module | Borrower and Investor Dashboard | Planned | Fully deployed and tested 100% | 1 | Reviewed by sponsor |
9 | Secondary | Analytics Module | Timeline/Charts for borrower and investor | Planned | Fully deployed and tested 100% | 1 | Reviewed by sponsor |
10 | Secondary | Credit Score Module | Calculation of credit Score | Planned | Fully deployed and tested 100% | 1 | Reviewed by sponsor |
10 | Secondary | Credit Score Module | Calculation of loan risk grade | Planned | Fully deployed and tested 100% | 1 | Reviewed by sponsor |
11 | Secondary | Analytics Module | Simulation Settings | Planned | Tested | 1 | Reviewed by sponsor |
11 | Tertiary | Gamification Module | Timed Quizzes | New | Tested | 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 |
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.
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.
Project Deliverables:
List the artifacts produced for this project. The entire deliverable can be submitted in a separate thumb drive, web repository or place in the IS480 team wiki.
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 | ||
Screen Shots | CRUD Customer, Trend Analysis | |
Design | ER Diagram | 1, 2, 3 |
Class Diagram | 1, 2, 3 | |
Testing | Test plan | instructions |
Handover | Manuals | User tutorial, Developer manual, Setup manual |
Code | client server | |
Deployment Diagram | instructions |
Not all parts of the deliverables are necessary but the evidence should be convincing of the scope.
Quality:
Explain the quality attributes (non functional) of your project deliverables. Have you designed the architecture, use a design pattern, etc? Does your architecture address scalability, performance, reliability, availability, fault tolerance, usability, etc. Does your design address maintainability, flexibility, configurability, etc. Be brief here but you can link to diagrams or code detail pages. Do not repeat the technical complexity part, link to it if necessary.
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
Compile common lessons and reflection for the team and for each team member. Be brief.
Team Reflection:
Key lessons learned – indicating where the team improved, or would do things differently next time. You may refer to the learning outcome summary in your proposal. A very short checklist style will suffice. It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.
Individual Reflection:
Describe in a paragraph, the key areas of learning or improvement. These should be personal areas of growth or learning. Each individual should list his/her effort, responsibility, actual contributions and personal reflection. Do not repeat team project contributions or member roles. Link if necessary.
Sponsor Comment:
Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.