Team Meeting - Date Fri Sept 20

Meeting minutes:

We are currently having difficulty agreeing upon an approach for input and outputs of the problem. We have agreed to put both perspectives of system and user inputs/outputs.
We are revising goals and whether they align with the examples provided in class. We believe that it is not necessary to refine the goals because they fit the description of what a "goal" is. However, we are refining our goals to avoid ambiguity.
We clarified how we want to use custom labels for organizing issues.

Action Items:

Revise the design thinking section of "extras" in Problem Statement deliverable after Monday Sept 23rd's tutorial discussion
Organize action items into individual issues
Ask about input/output and environment in the Problem Statement deliverable on Monday
We are going to split the goals and explain two things: why is the goal there in the first place, and how are these goals measurable?
Change the project name to not awesome bus
We want to collect the items to be completed individually (including importing Google Doc into TeX) Steps to be done:
4,
6 (what could be new roles?),
8 (needs to be flushed out, require a high level schedule on when things were due and a buffer date before actual date),
9 (write out large paragraphs, consequences of a bad PoC),
7 (describe all labels),
10,
11 (look into if any additional coding best practices are necessary)
individual dev plan reflection

nguyes44 / McMasterTransit