HeaderSIS.jpg

Difference between revisions of "GenSHYFT Mid Term Wiki"

From IS480
Jump to navigation Jump to search
Line 55: Line 55:
 
|align="center"| Change Management Action  
 
|align="center"| Change Management Action  
 
|-
 
|-
 
  
 
|- style="background:white; color:black"
 
|- style="background:white; color:black"
 
|| Mastery-based Coaching
 
|| Mastery-based Coaching
||  
+
|| Users would be able to resolve questions that they solved below their average performance in the past
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.  
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.  
 
 
|-
 
|-
  
Line 96: Line 91:
  
 
|| Purpose Driven Development  
 
|| Purpose Driven Development  
||
+
|| UI discussed as such in prototype [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2013T2_GENShYFT_Documentation_proto#Purpose-Driven_Video View Paper Prototype]
UI discussed as such in prototype [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2013T2_GENShYFT_Documentation_proto#Purpose-Driven_Video View Paper Prototype]
 
 
||  
 
||  
 
UI changed after prototyping, clients changed position of video and feedback. The buttons for the options to answer the feedback has been changed from slider to radio button and as of recent (9/2) normal button.  
 
UI changed after prototyping, clients changed position of video and feedback. The buttons for the options to answer the feedback has been changed from slider to radio button and as of recent (9/2) normal button.  
||
+
||This change was implemented as it was mostly a UI issue.
This change was implemented as it was mostly a UI issue.
 
 
|-
 
|-
  
Line 112: Line 105:
 
This change is implemented because team assessed the requirement change and realised it would make sense for the video gallery to appear so that player knows the videos he has unlocked so far.  
 
This change is implemented because team assessed the requirement change and realised it would make sense for the video gallery to appear so that player knows the videos he has unlocked so far.  
 
|-
 
|-
 +
 
|| Purpose Driven Development  
 
|| Purpose Driven Development  
 
||  
 
||  

Revision as of 01:30, 13 February 2014

GENShYFT IS480 1314 Logo.jpg


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 View Paper 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 UI discussed as such in prototype View Paper Prototype

UI changed after prototyping, clients changed position of video and feedback. The buttons for the options to answer the feedback has been changed from slider to radio button and as of recent (9/2) normal button.

This change was implemented as it was mostly a UI issue.
Purpose Driven Development

This option did not exist when signing off prototype

Client wants a video gallery below (on the page that the user is viewing the video). It would indicate which videos are locked and unlocked. This translated into a change in the data structure.

This change is implemented because team assessed the requirement change and realised it would make sense for the video gallery to appear so that player knows the videos he has unlocked so far.

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.

This feature was taken into consideration as team tried to develop it and realise feature is not too complex to implement

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
  • Team discussed with clients new project scope from acceptance.
Mastery Coaching - First Half 7th Nov - 11th Nov Creation of all paper prototypes 5th Dec - 12th Dec Client sign off prototypes
  • Team delay iteration 3 as the team was struggling to code during Near-Exam time.Therefore, Iteration 3 starts After Exams ended.
4 Purpose Driven - Second Half 22nd Dec Purpose Driven 31st Dec
  • Assigned to Project Mananager : Yousof
  • Both Member originally assigned were away.(Notification only after acceptance).
  • Function was client top 3 priority.
Mastery Coaching- Second Half 22nd Dec Mastery Based Coaching 31st Dec
  • Assigned to Business Analyst: Shanaaz
  • Both Member originally assigned were away.(Notification only after acceptance).
  • Function was client top 3 priority.
Group Based Tournament 31st Dec
  • Assigned to Co - Lead Developer: Glen
  • Both Member originally assigned were away.(Notification only after acceptance).
  • Function was client top 3 priority.
  • Fariq , Wahchun and Eng Sen were away for December.
  • Each member had to adapt do 1 function each in parallel in order to meet client's priority.
  • Project Manager and Business Analyst had to code otherwise, team is only left with 1 developer,
5 Co-Organized event
Hour of Code
23 Dec Purpose Driven 15 Jan
  • Yousof was coding both Purpose Driven and Mastery Based Coaching.
  • Client made changes to UI on the features different from paper prototype.
Recruit Participants for Singpath tournaments 23 Dec Mastery Based Coaching 15 Jan
  • Yousof was reassigned to this as Shanaaz was struggling with Angular.
  • She is to take assist more on her Secondary role as Co-PM.
  • Client made changes to UI
  • Client changed on the requirement of playing Mastery Base Coaching. User must complete a question before to master that question.
Group based tournament. 15 Jan
  • Eng Sen was assigned 3rd week of December to assist, - requires some time to learn.
  • Competition was was organized start of February is now pushed to 15 Feb - Giving the Team additional time.
  • Glen believed function is going well, hence only Eng sen was assigned to assist
  • Client wanted a new Json data structure for tournament instead of re-using client's existing data structure model.
Easy Web Prototyping. 15 Jan
  • Fariq and Wah Chun joined on the 29th of Decembers.
  • Both of them were to use this function to explore Angular as much as possible.
  • Client changed Collaborative Mode to Sharing of Codes Mode.
  • Team has several changes in scope by client during this time. Namely Purpose Driven and Mastery Based Coaching.
  • Tournament group needed to create a brand new Json data structure to support tournament. Development can continue after data structure is complete.Codes needed to be re-adapted to new data structure.
6 Predictive Analytics - ETL 10th Jan Group based tournament - Create Tournament 9th Feb
  • Client changed the UI and logic flow of Create Tournament.
  • Eng Sen required to make changes to the UI
  • As competition is coming, this became top priority.
  • Client later postponed tournament to March which requires team to re-prioritize.
Predictive Analytics - Statistical Application 10 Jan Group based tournament - Join Tournament 9th Feb
  • Glen encountered complication during creation of Join.
  • As competition is coming, this became top priority.
  • Client later postponed tournament to March which requires team to re-prioritize.
Predict User's School 10 Jan Group based tournament - Live Ranking 9th Feb
  • As Tournament was behind, Fariq was removed from Web Development Prototyping and relocated to assist Tournament.
  • As competition is coming, this became top priority.
  • Client later postponed tournament to March which requires team to re-prioritize.
Register for Event 9th Feb
  • As date is nearing, our client has a new requirement. To create an Events page.
  • Client deemed this as high priority as currently, there is no means for people to register.
  • Client requirements were simple, Wah Chun was relocated to this to quickly developed this.
  • Client added an Event-Ranking table requirement to display who will get in or get cut off from a particular event.
  • Client added Facebook Share requirement .
  • Client wanted current user's status to be shown requirement .
  • Client later postponed tournament to March which requires team to re-prioritize.
Mastery Based Coaching 9th Feb
  • Republic polytechnic was interested on this function hence now became Client top priority after change in Tournament Competition date.
  • Client recommended a different Json data structure.
  • Client change scope. Mastery will now load 1 game. Mastery will not load new game. Mastery will determine the type of improvement user can make.
Purpose Driven 9th Feb
  • Republic polytechnic was interested on this function hence now became Client top priority after change in Tournament Competition date.
  • Client recommended a different Json data structure.
  • Client change scope. Client wanted a Video-Gallery at the bottom of the page to allow user to see video progress.
Developer's Documentation 9th Feb
  • Client wanted a technical documentation stating the API calls and explanation of codes.
  • Client wanted this ASAP.
  • Shanaaz, who was BA/Co-PM was assigned to do this documentation.
  • Client made several scope changes such as UI, Data structures and New Features. Almost all feature had a change.
  • Tournament Competition had changed of dates which requires the team to re-prioritize while Client has different priorities along the way.
  • The team decided to put Web Development prototype on hold.
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.

Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.