Way of Working
Communication
We use Artsgoz Tech discord channel for internal communication.
- Access: If you have not yet joined the server or are missing access to specific channels, please reach out to your Project Manager (PM) to receive an invite and the appropriate roles.
- Guidelines: Use public channels for project-related discussions to maintain transparency, and keep threads organized for specific technical topics.
Process/Workflow
We follow an Agile methodology with a 2-week sprint cycle to ensure our development remains iterative, transparent, and adaptable. Our standard sprint routine includes:
Maple, please check and update this krub.
- Sprint Planning: Held at the start of the sprint week to define our goals, discuss priorities, and assign tasks.
- Standup Updates: Conducted mid-sprint to share progress, identify any blockers, and ensure the team is aligned.
- Sprint Review: Held at the end of the sprint (Friday or Saturday) to review completed work and discuss what we can improve for the next cycle.
Branch/Pull Request Lifecycle
This section is for developers, please see Branch and PR pattern
Task Tracking
We use GitHub Projects as our single source of truth for task management, bug tracking, and sprint planning.
- Project Board: Artsgoz GitHub Project
- Ticket Lifecycle: All team members are expected to keep their assigned tickets updated. When picking up a task, assign yourself and move the ticket through the appropriate columns (e.g., To Do → In Progress → In Review → Done).
Please see วิธีใช้ Github Issue