A living collection of playbooks that define how we work at Gurzu — our principles, workflows, and standards across disciplines. Each playbook is a self-contained guide on a specific topic, maintained by the team and updated as our practices evolve.
Open for the community. We are publishing these playbooks publicly because we have learned a lot from open knowledge from other teams, and we want to give back. Use them, adapt them, fork them, and please do let us know what works (and what doesn't) for you.
Playbooks exist so that:
- New team members can ramp up quickly with shared context.
- Teams make consistent decisions without reinventing the wheel.
- Our standards stay explicit, reviewable, and improvable.
- Clients and partners can understand how we operate.
- AI-Augmented Engineering — How we work with AI tools across engineering, design, and QA: principles, workflows, role-specific guidance, and governance.
- Sales — How we run our sales process end to end: from lead to qualification, proposal, contract, and repeat business.
- Product Design — How we approach product design at Gurzu: framing problems, shaping requirements, and running design inside an agile cadence.
- DevOps & SRE — How we ship and run software reliably: source control, CI/CD, containers, hybrid cloud, infrastructure-as-code, monitoring, backups, scalability, and security.
- QA & Automated Testing — How we run QA at Gurzu: STLC, test plans, defect tracking, code freeze, design QA, and automation across web, mobile, non-functional, and cross-platform testing.
- Mobile Development — How we build and run mobile apps end to end: requirement gathering, planning, design, sprint-based development, QA, App Store / Play Store deployment, handover, and long-term support and maintenance.
- Lean Project Execution — How we run projects with a lean approach: weekly cycles, small batches, single sources of truth in Basecamp and GitHub, and the discipline that keeps teams shipping value every week.
More playbooks will be added here as they are authored.
Each playbook lives in its own folder under this repository and contains:
- A
README.mdwith the overview and table of contents. - Numbered or named chapter files covering the topic in depth.
- Any supporting appendices, references, or assets.
Anyone — inside or outside Gurzu — is welcome to read, share, and adapt these playbooks. A few notes on how to use them well:
- They are opinions, not commandments. What works for us may not work for your team. Take what helps, leave the rest.
- They are living documents. What you read today may evolve next month as we learn more.
- They reflect Gurzu's context. A small, distributed product engineering company. Calibrate accordingly if your context is different.
- No warranty. These materials are shared as-is, with no guarantees of correctness, completeness, or fitness for any particular purpose.
If you adapt a playbook for your own organization, attribution back to Gurzu is appreciated but not required.
Playbooks are meant to evolve. If something is outdated, unclear, or missing:
- For Gurzu team members: open a pull request with the proposed change. Keep edits focused — one topic or chapter per PR when possible. Prefer concrete examples and lived experience over abstract rules.
- For people outside Gurzu: issues, suggestions, and pull requests are welcome. We may not accept every change (these playbooks reflect how we work), but we genuinely value feedback, corrections, and ideas — they make the next revision better for everyone.
When proposing changes, please:
- Be specific about what you would change and why.
- Reference your own experience or sources where relevant.
- Keep tone and structure consistent with the rest of the playbook you are editing.
These playbooks are the intellectual property of Gurzu Inc.
- Within Gurzu: playbooks are owned collectively by the teams that practice them. When in doubt, ask in the relevant team channel before making substantial structural changes.
- For the public: unless an individual playbook states otherwise, the content is shared for reading, learning, and adaptation within your own organization. The Gurzu name, logo, and trademarks remain the property of Gurzu and are not licensed for reuse.
- Commercial reuse, repackaging, or republication of substantial portions of these playbooks requires prior written permission from Gurzu.
If you are unsure whether your intended use is okay, please reach out via gurzu.com — we are usually happy to say yes.
- Website: gurzu.com
- For questions, collaborations, or permissions related to these playbooks, please use the contact channels listed on our website.