To ensure smooth collaboration and accountability throughout the project, our team has established a clear set of ground rules. These rules guide how we communicate, manage tasks, and work together across our rotating roles. They help us stay aligned, respectful, and focused on delivering a successful game within the Agile framework.
Meeting Protocol
• Meeting will begin and end as scheduled to respect everyone’s time. It is expected that every team member will arrive for the meeting on time.
• Each team member will contribute updates based on their assigned role for the sprint (Maze Designer, Era-Themed Artist, Coder, Sound Curator, or QA + Storyliner).
• Discussions will follow a round-table format, ensuring everyone has equal opportunity to share ideas and progress.
• Action items will be clarified before the end of each meeting, and any blockers will be acknowledged early.
Communication Channels
• WhatsApp will serve as the main day-to-day communication platform for sharing updates, quick questions, and reminders.
• Email will be used for submitting formal documents or files when necessary.
• Members are expected to respond to messages within 24 hours unless otherwise communicated.
• The team will maintain a shared calendar or task board (via Trello or Microsoft Planner), which must be kept updated with key deadlines and dependencies.
Task Ownership
• Tasks are assigned during meetings and each member has ownership and is accountable for their completion.
• Members are expected to take full ownership of their weekly responsibilities, including communication of progress or delays.
• If tasks are interconnected (e.g., sound depends on visuals), members will proactively communicate to prevent bottlenecks.
Confidentiality and Respect
• All creative materials—art, storylines, sound assets, and code—must be treated as team intellectual property and kept confidential.
• Respectful collaboration is a must. Constructive feedback, active listening, and support for one another’s work is always encouraged.
• Every member is expected to contribute ideas and help solve problems beyond just their weekly role when needed.
Continuous Improvement
• After every sprint, the team will conduct a retrospective to reflect on what went well, what didn’t, and how to improve next week.
• Feedback will be gathered across all roles, especially from the QA + Storyliner, to track issues in flow, logic, or engagement.
• Team members are encouraged to reflect on their individual performance and team collaboration, with the goal of growing together creatively and professionally.
By following these shared expectations, we aim to build a positive team dynamic where creativity, ownership, and continuous learning thrive. These ground rules will not only keep us on track but also foster a sense of trust and shared responsibility as we work toward a common goal.