Schedule and Journal
Regular meetings and project touchpoints.
Team E Project Journal
Most recent entries appear first. Each team, client, and professor/manager meeting is recorded with a concise summary of discussions, problems, decisions, and action items when provided.
Weekly progress reports follow the TA's Progress, Plans, and Problems format. The TA notes call for an update by 11:59 p.m. the day before the regular meeting slot, including weeks without a meeting, and an email confirmation with the website link.
Progress: The client emailed responses to ten topics of requirements questions to the team. The D1 draft is also updated to reflect the client's responses. This is a progress update, not a meeting record.
Plans: Another client meeting has been proposed for the week of September 28, but a new time has not been confirmed.
Problems: N/A. The client has responded to the emailed questions as of September 21.
Progress: The team emailed ten topics of requirements questions to the client on September 18 after the planned client meetings could not take place. The website and D1 draft now record the meeting status and questions. This is a progress update, not a meeting record.
Plans: The team proposed meeting the following week in the September 18 email; a new time has not been confirmed. The specifications can be revised once the client's answers arrive. Additional team assignments and weekly commitments have not been recorded.
Problems: Technical difficulties prevented both planned client meetings, and no response to the emailed questions has been received as of September 20. Requirements, priorities, and acceptance criteria remain unconfirmed.
Purpose: Determine specifications and requirements with Nick Dokich.
Problem and outcome: Technical difficulties on the client's side prevented the meeting. No discussion, requirements decisions, or meeting action items were recorded.
Follow-up: The team emailed requirements questions on September 18 and proposed meeting the following week. No response has been received as of September 20.
Discussion: Reviewed expectations and the TA material. The supplied notes cover time management, early communication about contribution imbalances, weekly Progress/Plans/Problems reports, deliverable and demo status, version control practices, and project tracking.
Guidance reviewed: Keep the website current for manager review. The notes encourage AI assistance while requiring significant human revision and oversight of written deliverables.
Decisions and action items: No additional project-specific decisions, named assignments, or deadlines from this meeting have been supplied. The team-reported TA schedule is Tuesdays, 10:30-11:00 a.m.
Purpose: Determine specifications and requirements with Nick Dokich.
Problem and outcome: Technical difficulties on the client's side prevented the meeting. No requirements were confirmed and no meeting action items were recorded.
Updated the project page to align with course website expectations, including roles, contact information, meeting schedule, team rules, journal, related links, and deliverables.
Captured the product objective, target users, workflow, input and output formats, and proposed open-source technology stack.
Defined the problem space around color-separated logos, closed vector paths, local Windows execution, and CAD export needs.