Meeting Notes

Meeting #1:

• Standup meetings start next week: show progress, any blocks.

• Create UI mock-ups of your app.

• Storyboard Sequences: flow of your app (for more info, see project problem description).

• Create CRC cards for the most anticipated classes: list collaborators.

• All tools, UI mock-ups, storyboard sequences, meeting notes, and CRC cards should be added to GitHub Wiki.

Meeting #2:

• 3 questions from the TA for each team member (progress, blocks and plan).

• For user stories, assign risk level to the stories.

• Create CRC cards for part 2 (include the most important entities).

• Start as early as possible.

Meeting #3:

• Part 3: 10 deliverables; address feedback, codebase of prototype (half of user stories ~23), code documentation (java docs and commets for all functions, interface, class), test cases (for every function), intent tests (for UI)), object-oriented (UML), product backlog (tracking user stories), UI mockups (only if major changes are made), sprint planning (record weekly plan for each member and user stories a team member worked on), in lab demo, proper github use.

Meeting #4:

• From now on, the TA will check individual work for each team member.
• The TA will compute coefficients for each team member and team members with very low coeffcients will suffer grade losses.
• No need to test database functionalities.

Meeting #7:

Feedback:

• UI mockups screwed up

• Java docs missing (missing params, inconsistent)

• Test cases did not work.

• Failed unit tests.

• Bad UML.

• Product backlog.

• Sprint planning, undocumented meetings.

• Satisfactory demo

• Inconsistent use of GitHub issues.

PART 4 Expectations:

• Deliverables: Addressing feedback, final codebase, runnable test cases (testing flow of logic), OOD (UML with all important classes and relationships), UI mockups, sprint planning (note of work distribution).

Demo Date: April 9th.