IS480 Team wiki: 2016T1 CLEBS Mid-Term
Revision as of 00:13, 25 September 2016 by Luqmant.2014 (talk | contribs) (→Intermediate Deliverables)
HOME |
Project Progress Summary
Midterm Slides: <LINK>
Deployed Site Link:
Project Highlights
What was achieved from Acceptance?
- Completion of our most major iteration
- Project Creation Module (Iteration 5) was completed and users, after having their project proposal accepted, are able to create their projects
- En-route to achieving X-Factor:
- 20 Users Sign Up
- 20 Project Proposal Created
What unexpected events occurred?
- Changes to Project Scope and Timeline
- Sponsor experienced difficulty in setting up a BrainTree account and asked to push the Payment Gateway Module back
- Replaced Payment Gateway Module with Admin Dashboard Module
- Delay in Iteration 5
- Team had multiple other commitments to juggle
- Team were unfamiliar with the implementation of JQuery and JavaScript, and as a result, constantly
- Sponsor added changes they would like to see in the Project Creation page
Project Management
Project Status
This was our initial planned Project Scope, before the changes:
And this is our actual Project Scope (With Changes):
This chart below shows the changes to our Project Scope
Date | Scope Type | Module Name | Original Details | Changes | Final Details |
---|---|---|---|---|---|
14 Aug 2016 | Primary Scope | Project Creation Module | Create, View, Edit Project | Greater Definition of the Project Creation Module i.e. added more description for the scope | |
14 Aug 2016 | Good-To-Have Scope | UI/UX Improvement Module | Was not present before | UI/UX Improvement Module was added to the Good-To-Have Feature | "Good to have user interface and user experience improvements that can be made" |
19 Aug 2016 | Primary Scope | Admin Dashboard Module | Was not present before | Admin Dashboard Module was added to the Secondary Feature | Show the tasks required for admin dashboard module, mainly scaffolding and create layouts |
Project Schedule (Plan Vs Actual)
This was our initial Planned Schedule:
This is our Actual Schedule:
Listed below is our Schedule Progress Chart to show the tasks that are completed or incomplete:
Project Metrics
Listed below are our collated and updated Schedule Metrics and Bug Metrics.
Change Management
Change Request | Reason For Change | Team's Decision |
---|---|---|
Mobile-friendly (Responsive) UI | Most users now surf the web using their smart phones or tablets, and thus, the sponsors feel that we should make the YBCO platform responsive and mobile-friendly to cater to these group of people | Approved (to be completed in the last iteration) |
Move Payment Gateway Module Back | Sponsor experienced difficulty in setting up a BrainTree account and asked to push the Payment Gateway Module back to give them time to settle the administrative issues | Approved |
Make Project Creation Module Editable In-page | Sponsor asked for us to implement user-friendly and in-page editing for project creators (so that they won't be constantly redirected to other pages) when creating a project. This enhances the overall user experience for them | Approved |
Create intuitive "TypeForm-like" Forms in Project Proposal | Sponsor requested for us to consider enhancing the Project Proposal form, similar to that of TypeForm. | Rejected (Too complex) |
Project Risks
Number | Risk & Description | Impact | Mitigation Plan |
---|---|---|---|
1 | Taking on Ruby on Rails Development without prior knowledge | High | Team has to constantly work together and ask questions if there are any issues. In the event that a member(s) is/are unsure of how to code out a function, he or she should source for help, not just among the team, but other alternative options as well |
2 | Choice of servers (GoDaddy, AWS and Heroku) that are unfamiliar and complex | High | Team has to read online documentations as much as possible and look out for related online forums for help. Team should also look into asking YBCO CTO Uttam for help as he is familiar with such technologies |
3 | Additional project scope from the sponsors | Medium | As of now, most of the plans have been finalised. In the event that there are changes to the scope, Project Manager should evaluate and decide as a team whether to take up the change request and inform the sponsors of the team's decision. Team has to manage the expectations of the sponsors and ensure that we can deliver what we aim to |
Technical Complexity
ON WEB:
ON MOBILE:
System Architecture Diagram
Intermediate Deliverables
Stage | Specification | Module |
---|---|---|
Project Management | Minutes | Meeting Minutes |
Project Schedule | Project Schedule | |
Project Scope | Project Scope | |
Metrics | Schedule & Bug Metric | |
Risk Management | ||
Change Management | Change Management | |
X-Factor | X-Factor | |
Documentation & Design | Use Case | Use Case Diagram |
Designs | ER Diagram | |
LD Diagram | ||
User Story | ||
Tools & Architecture | Tools Used | |
Technologies Used | ||
Architecture Diagram | Architecture Diagram | |
Testing | Iteration Tests | Iteration Test Results |
User Tests | User Test 1 | |
User Test 2 |
Deployment 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.