Sprint and Release Planning Guide
Our approach to sprint planning, release cycles, and hotfix management for agile development.
Berkay Demirbas
1 min read
At Hardal, we balance structure with flexibility in our development process. Here's our approach:
Sprint Planning
- Weekly sprints - One-week cycles for rapid iteration
- Clear goals - Specific, measurable objectives each week
- Realistic scope - Plan for what we can actually accomplish
Release Management
- Version releases - Every 4-6 weeks for major features
- Hotfixes - Immediate fixes for critical issues
- Semantic versioning - MAJOR.MINOR.PATCH (2.0.0, 1.3.0, 1.2.3)
Hotfix Process
- Create
hotfix/<issue-name>branch - Implement minimal solution
- Test and merge to main
- Update develop branch
Vibe Coding
We embrace "vibe coding" — that flow state where code feels natural between AI and human touch.
- Shared Cursor files - Start together, then split to preferred IDEs
- Clean, focused code - Clarity over perfection
- Flow over shipping - It's about thinking better with code
Quality is non-negotiable. All releases go through testing before production.