HeaderSIS.jpg

IS480 Team wiki: 2017T1 Team Kinetic Midterm Wiki

From IS480
Revision as of 19:13, 1 October 2017 by Sandeepi.2014 (talk | contribs)
Jump to navigation Jump to search
Kinetic.png

Project Progress Summary


Kinetic Snapshot.png
Midterm Slides Deployed Site
Kinetic PresentationIcon.jpg KineticLoans Logo.png

Project Highlights:


Kinetic ProjectHighlights.png

Project Management

Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.

Project Status:

Kinetic ProjectStatus.png
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):

Compare the project plan during acceptance with the actual work done at this point. Briefly describe a summary here. Everything went as plan, everything has changed and the team is working on a new project with new sponsors or the supervisor is missing. A good source for this section comes from the project weekly report.

Provide a comparison of the plan and actual schedule. Has the project scope expanded or reduced? You can use the table below or your own gantt charts.

Planned Project Schedule

Kinetic TimelineV4.jpg


Actual Project Schedule

Kinetic Timeline V6.png


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.