**UniTicket Project - Collaborative Working Session Minutes** **Date:** Wednesday, 11th February 2026 **Time:** 11:00 – 14:00 (3 Hours) **Location:** Collaborative Working Session **Attendees:** * Dom (Project Lead) * Frank (Lead Developer - CLI) * Olly (System Architect) * Sam (QA & Documentation) * Yousif (Frontend Lead - GUI) ### **1. Agenda Overview** * Review of Project Roadmap and Provisional Timeline. * Definition of Development Methodology (Sprints & "Baton Pass"). * Technical Stack Finalisation (Python & SQL). * Infrastructure Setup (GitHub & Communication). * Architecture Planning (Spider Diagram). * Role Confirmation & New Member Integration. ### **2. Key Discussions & Decisions** #### **2.1 Development Methodology & Workflow ("The Baton Pass")** * **Discussion:** Dom opened the session by reviewing the roadmap. Sam recommended adopting short sprints to maintain momentum. Dom proposed a rotational coding strategy to ensure all members gain hands-on experience and to facilitate continuous peer review. * **Decision:** The team agreed to a "Baton Pass" workflow. * **Workflow:** Instead of simultaneous coding on the same file, ownership of the active codebase will rotate between members at each designated meeting. * **Cycle:** * **Wednesday to Sunday:** Member A leads coding (supported by Lead Dev Frank). * **Sunday Meeting:** Code review, merge, and handover to Member B. * **Sunday to Wednesday:** Member B leads coding. * **Wednesday Meeting:** Review, strategy discussion, and handover to Member C. * **Immediate Action:** Olly will take the "baton" first, coding the CLI skeleton from now until the Sunday meeting. #### **2.2 Technical Stack Decisions** * **Programming Language:** Sam formally recommended **Python** for the project due to its suitability for rapid CLI development and strong library support. This was unanimously agreed upon. * **Database:** Frank (Lead Developer) led the discussion on data persistence. * **Decision:** The team opted for **SQL** (specifically SQLite for the initial phase) rather than using `.json` files. * **Rationale:** Frank argued that SQL offers superior scalability, makes adding users/assets easier, aligns better with industry standards, and allows for more complex queries if the project expands. #### **2.3 Infrastructure & Architecture** * **Version Control:** Olly (System Architect) successfully initialized the central **GitHub Repository**. * He distributed repository details to the team. * Permissions issues were resolved, ensuring all members have write access. * **System Design:** Olly presented an **Architecture Overview (Spider Diagram)**. * This diagram visualizes the required classes, their relationships, and the core functionality expected from the UniTicket system. * The team reviewed and approved this as the blueprint for the initial coding phase. #### **2.4 Team Integration & Roles** * **Yousif (Frontend Lead):** * Yousif confirmed his understanding of the roles and responsibilities. * He has joined the WhatsApp group chat for daily communication. * He set up his personal GitHub account and successfully collaborated with the team repository. * **Role Focus:** Yousif will oversee the GUI (Graphical User Interface) development, which is scheduled for a later phase. For now, he will shadow the CLI development to understand the underlying logic. * **Frank (Lead Dev):** * Frank re-confirmed his role as the technical lead for the CLI. * He will not hold the "baton" exclusively but will instead oversee the coding process and be available to collaborate with whoever is the designated coder for the current sprint. ### **3. Action Items (Sprint 1)** * **Develop Initial CLI Codebase** (Based on Architecture Diagram) - Assignee: Olly - Deadline: Sunday 15/02 (20:00) * **Support SQL Integration & Oversight** - Assignee: Frank - Deadline: Sunday 15/02 (20:00) * **Review Progress & Prepare for Handover** - Assignee: All Team - Deadline: Sunday 15/02 (20:00) ### **4. Next Meeting** * **Date:** Sunday, 15th February 2026 * **Time:** 20:00 GMT * **Focus:** Review of Olly's progress, code review, strategy discussion, and handover of the coding baton to the next team member.

[UPDATE] UPDATE (Feb 10th): Great news! Yousif has joined the team, bringing us to the required 5 members. **Action Taken:** - Final team details submitted to Blackboard. - UniTicket confirmed as chosen project. - Yousif assigned to Phase 3 (GUI/Web) research.

MINUTES (Feb 8th 2026) **Meeting commenced:** 20:00 GMT via Discord. **Attendees:** Dom, Sam, Frank, Olly. **1. Project Selection:** The team reviewed the 10 available options. After a vote, **UniTicket** was selected unanimously. Rationale: It simulates real-world enterprise software, allows for a clear separation of concerns (Backend vs Frontend vs DB), and fits the "Simulated Work Environment" criteria. We agreed to adopt a "CLI First" approach to ensure the core logic and database schema are robust before attempting a GUI, minimizing risk of submission failure. **2. Role Allocation:** - **Dom (100519399)** appointed as Project Lead. Responsibility: Overall architecture, scheduling, and final report compilation. - **Frank (100720007)** appointed Lead Developer. Responsibility: Core Python CLI logic and CRUD operations. - **Olly (100697329)** appointed System Architect. Responsibility: Database schema (SQL) and integration. - **Sam (100716530)** appointed QA & Documentation. Responsibility: Testing, bug tracking, and minute taking. **3. Schedule:** Agreed to a "Core Working Block" on **Wednesdays 11:00 - 15:00**. This is a mandatory synchronous session. **Sunday 20:00** is reserved for Retrospectives and Sprint Planning (1 hour max). **4. Tooling:** GitHub selected for Version Control. We will use the "Feature Branch" workflow to prevent conflicts on the main branch. **Action Items:** - Dom: Create GitHub Repo and invite team. - Frank: Write "Hello World" CLI skeleton. - All: Submit Uni Numbers to Blackboard. **Meeting adjourned:** 21:00.