Capstone-Psychology

This repository is used to keep track of meeting minutes for the CSCI 4308 CU Boulder Psychology department project team

Spring Semester

  • 1-14 meeting Setting up environments, determining best host for backend
  • 1-30 meeting Structural and process decisions, start code for front end
  • 2-4 meeting Sponsor meeting. Showed first stages of tasks, got feedback to implement.
  • 2-6 meeting Determining structure for backend, continuing work on front end tasks
  • 2-13 meeting Continuing work on front and back end.
  • 2-20 meeting Continuing work on front and back end.
  • 2-27 meeting Discussing back end progress, next steps for front end and sponsor questions
  • 3-2 meeting Sponsor meeting. Covered current progress, scoring, levels, implementation details, etc.
  • 3-5 meeting Covered current progress, made plan for back end meeting.
  • 3-6 meeting Sponsor meeting, covering name + face task, general implementation.
  • 3-8 meeting Backend meeting. Made plan for implementation going forward, synced team.
  • 3-12 meeting First remote meeting due to COVID. Planning demo app for sponsors. Backend - Front end connection info.
  • 3-19 meeting Looking at additional front end features, planning needed features for backend and additional meeting.

Fall Semester

  • 9-13 meeting Initial meeting
  • 9-18 meeting First full team meeting, contacted sponsor and established Slack
  • 9-25 meeting Contacted sponsor, scheduled meeting, collected questions for meeting
  • 9-26 meeting Met with mentor, set up tools
  • 10-4 meeting Met with sponsor, answered questions, established tasks to implement in app, created plan for project charter
  • 10-9 meeting Created project charter
  • 10-10 meeting Updated project charter, assigned sections of requirements definitions
  • 10-17 meeting Reviewed presentation, submitted charter, consolidated slack channels, created Trello
  • 10-24 meeting Reviewed usage of Ionic, Trello, confirmed time with sponsor
  • 10-27 meeting Sponsor meeting. Covered existing server structure, face morphing, licensing, details behind CRD and what is known, and priorities for app
  • 10-31 meeting Contacted psych department about existing servers, assigned sections to update requirements document
  • 11-7 meeting Reviewed contents of requirements document, created sponsor slack server, created high level plan
  • 11-14 meeting Signed up for presentation time, sent requirements document to sponsor
  • 11-21 meeting Assigned presentation sections and system design sections, sent questions to sponsor
  • 12-2 meeting Sponsor meeting. Refined understanding and definitions of tasks, focus for development, server plan, high level ideas. Contains most in depth definitions of tasks
  • 12-4 meeting Team assignments, system design document assignments
  • 12-12 meeting Times for next semester, plan for system design, role assignment