GenSHYFT Mid Term Wiki
Home | Project Overview | Project Management | Documentation | The Team |
Project Progress Summary
Place your Final slides link and deployed site link here
For proposal, please see Requrements at the Project Deliverables. This will help us understand your scope. Note wiki policy here.
This page should NOT be too long. It should link to other pages in the IS480 team wiki. Do not repeat the proposal, midterm or other wiki information here. Highlight changes since midterm.
Describe the project progress briefly here. Is the project completed? Link to the final presentation slides and videos.
Project Highlights:
What unexpected events occurred and how were they handled?
- A team member left the project and dropped the course
- List of requirement changes
- CRUD items replaced with CU/Sync/Archive items
- Business analytics replaced with iPad client
- Took 8 weeks to learn Ruby on Rails
- etc.
Be brief. A couple of sentences on the event and another couple on what was done is sufficient. Do not repeat the next sub sections. If there are no highlights, remove this section
- Change in Requirements
Below is a compiled list of changes in the requirements:
Feature Affected | Previously | Currently | Change Management Action |
Mastery-based Coaching |
Users would be able to resolve questions that they solved below their average performance in the past |
User should redo any question that they have attempted before on the Practice page |
This change was implemented as it was still early in the development process. |
Mastery-based Coaching |
Client will provide audio files and text captions for the Coaches |
Client requested team to do up the audio files and text captions for the Coaches either personally or engage in professional services. |
Team decided to do the files up personally instead as it would take longer time if it was done by professionals. This change was implemented as client did not have materials ready yet. |
Mastery-based Coaching |
This option did not exist when signing off prototype |
Client wants an admin page for Mastery-based coaching |
This feature was not taken into consideration as team tried to develop it and realise feature is too complex to implement. |
Mastery-based Coaching |
When user starts the Mastery coaching session, user will be starting a new session |
New game will not be loaded,instead it will load a new game +++(edit). This causes a change in the data structure |
This feature will be taken into consideration after mid-terms as this requirement is recent (9/2) and team has yet to finish up the minimum requirements |
Purpose Driven Development | No Admin page was discussed during the paper prototype sign off | Client wants an Admin page where he can manage the videos to upload on the Purpose page. He wants to be able to copy and paste the link, description of the video, survey question for each video and thumbnail image of the video. | Initially, client wanted admin page for both purpose driven development and mastery-based coaching. Team member, Yousof in charge of both functionalities attempted the Admin page to estimate the level of difficulty in implementing this change in requirement. Team member decided that it would be easier to implement Admin page for Purpose driven than Mastery-based coaching. |
Create Tournament | Team discussed with client regarding the UI of this page using paper prototypes. | Client wants team to follow the page layout of an older version of SingPath | Team first attempted Client's suggestion and realised it was possible to implement this change as it focused more on UI |
Events | SingPath users would be able to request for an event by SingPath, Sponsorship Collaboration or Donate to SingPath. (Initially secondary feature) | Client wants Events to be where users would be able to sign up for a tournament. | This was a feature that was added by client right before acceptance presentation, hence it is not included in the Acceptance proposal. It was discussed with client that this would be a secondary feature as it was not as critical as the other features he wanted. In January, client talked with some schools to request their students sign up for tournaments @ SMU. Since there is no platform for students to sign up for these tournaments, client wanted Events page to include the ability to sign for a tournament. As this |
Project Challenges:
Describe areas of the project that were particularly difficult and how they were dealt with, whether successfully or not. Again, a few sentences are enough. If there are no challenges, remove this section.
Project Achievements:
Methods, technologies, processes, teamwork, etc. which were particularly successful – highlight things which worked very well towards completing the project. A bulleted list of one to two sentences each will do. If there are no achievement, remove this section.
Project Management
Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.
Project Schedule (Plan Vs Actual):
Compare the project plan during midterm 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.
Iterations | Planned | Actual | Comments | ||
3 | Purpose Driven - First Half | 7th Nov - 11th Nov | Gathering New Requirements | 5th Dec - 12th Dec |
|
Mastery Coaching - First Half | 7th Nov - 11th Nov | Creation of all paper prototypes | 5th Dec - 12th Dec | Client sign off prototypes | |
| |||||
4 | Purpose Driven - Second Half | 22nd Dec | Purpose Driven | 31st Dec |
|
Mastery Coaching- Second Half | 22nd Dec | Mastery Based Coaching | 31st Dec |
| |
Group Based Tournament | 31st Dec |
| |||
| |||||
5 | Co-Organized event Hour of Code |
23 Dec | Purpose Driven | 15 Jan |
|
Recruit Participants for Singpath tournaments | 23 Dec | Mastery Based Coaching | 15 Jan |
| |
Group based tournament. | 15 Jan |
| |||
Easy Web Prototyping. | 15 Jan |
| |||
| |||||
6 | Predictive Analytics - ETL | 10th Jan | Group based tournament - Create Tournament | 9th Feb |
|
Predictive Analytics - Statistical Application | 10 Jan | Group based tournament - Join Tournament | 9th Feb |
| |
Predict User's School | 10 Jan | Group based tournament - Live Ranking | 9th Feb |
| |
Register for Event | 9th Feb |
| |||
Mastery Based Coaching | 9th Feb |
| |||
Purpose Driven | 9th Feb |
| |||
Developer's Documentation | 9th Feb |
| |||
| |||||
1 | |||||
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.