Group Meeting Monday 18 May, 2015

Group Meeting Monday 18 May, 2015

Aim: Go through our deliverable items, documents, make sure everyone is on task
Attendance: Eric, Stuart, Teng, Bo, Cindy.
Minute Taker: Stuart

Minutes

Items of discussion:

1. Name of Transport Meow
2. Client Liaison
3. Incorporating feedback
• Justification as to why we did or did not accept certain feedback.
• Justification to be presented in presentation
• Justification to be documented in final document
4. Project Management
• Still using Trello?
• Who is responsible for which tasks?
5. Functional Testing
6. User Testing
7. Short Update Presentation
8. Coding
9. Final Presentation
10. Final Document
11. Things to complete by Friday.

1. Client is happy with App name.

2. It is not necessary to liaise with the client anymore. However, it is a good idea to meet with the client first, before final presentation. This will ensure that there are no surprise questions. - Unassigned.
3.  Most feedback is about driver incentive. We also asked for feedback on what extra functions we could add, but we did not show the prototype in the demo, so it was difficult to get feedback on this.

• Stuart to collate feedback and tally incentive options.
• Stuart to discuss with Crystal and finalise incentive.
• Decision should be based on user feedback, and justified.

4.  We still use Trello.

• The work breakdown is in Google Drive.

5. Functional Testing

This is a huge task. Teng volunteered to do functional testing, but maybe it is better and easier for Crystal to do it, as she is the primary coder.

We also need to seriously test the core functions. - Unassigned

6. User Testing

It is decided that we need to do user testing. We can put the test results into our document and presentation. This will also give us justification on our changes.

We need a usable prototype for Friday. Everyone needs to be able to access this, ready for user testing next week. - Crystal

Cindy has uploaded a User Testing script into Google Docs. http://bit.ly/1FrKKBy

Short Update Presentation

Stuart to liaise with Crystal for short presentation on Friday.

Everyone is to fill out the "Week 11 Presentation Content" on Google Drive. Any problems, please ask.

Talk about incentive in the presentation, justify.

Coding

Teng needs to upload his Function.

Teng is to work with Crystal in uploading his function.

Eric needs access to the prototype for assisting Cindy with breaking down the coding structure for tabulation.

Final Presentation

We need to figure out the problem statement, and how TransportMe solves it - Unassigned

Architectural Design showing the coding architecture needs to be completed. - Stuart

We need to make sure every piece of criteria is addressed in the presentation - Stuart

Make sure we talk about any good outcomes that came from user testing. - Unassigned

Talk about incentive in the presentation, justify. - Unassigned

Organise meet up with the client before the final presentation, so there is no surprises. - Unassigned.

Final Document

Everybody's contribution to the final document should be sent to the tutor Jason for review, before submitting into the actual document.

System architecture can include Database layer, View layer, Control layer, Front-End view layer, UI layer. Stuart to liaise with Crystal about System Architecture.

(TLDR) Action Points. Complete by Friday.                                                                           

Everyone: 

• Fill out "Week 11 Presentation Content" on Google Drive. http://bit.ly/1c2HyR1
• Send your completed final sections to Jason for review.

Teng:

• Discuss with Crystal about doing functional testing and testing core functions.
• Discuss with Crystal about uploading your function.

Stuart: 

• Collate feedback, find incentive option. 
• Discuss with Crystal - Finalise incentive, justify.
• Discuss with Crystal - Architectural Design
• Discuss with Crystal - Short Presentation.

Crystal:

• Discuss with Teng about functional testing, core testing and uploading his functions.
• Make prototype publicly available for user testing next week.
• Discuss with Stuart about incentive, architecture & short presentation on Friday.
• Give Eric access to the prototype so he can assist Cindy.

Bo:

• Work with Stuart on Detailed Designs
• Discuss with Stuart about the Solutions in Detail

Cindy: 

• Continue to work with Eric in Tabulating the work breakdown.
• Discuss with Eric about breaking down the hours for coding, login functions, 
• Get information from Crystal about various miscellaneous API keys, Database & passwords, Other resources to go into document.

Eric:

• Work with Cindy to tabulate the work breakdown.