Qatium Team Handbook

Here is where our Team keeps its collective memory. As within our brains, memories may not be an exact representation of reality but we try hard to keep it as close to it as possible.

DISCLAIMER: This handbook is expected to be created collaboratively by our whole team. Feel free to make or propose changes. See Contributing.

Index

General

• Auto-organization framework
• Ceremonies
• Tools

People

• Hiring
  • Hiring Guide for Tech roles
  • Hiring Guide for Non Tech Roles
• Onboarding
  • Buddy
• Progression framework
• Absences
• Legal Procedures

Culture

• Mission, vision & values
• Communication
• Learning Budget
• Mentoring
• Teamwork

Product

• Concerns
• Feature flags
• Kanban workflow
• Pillars
• Best Practices
• Product cards
• Story Map
• Technical debt
• Support

Product > Development

• Automated Testing
• Code Reviews
• Development Environments
• Development > Windows
• No Flaky Tests
• Operation
• Pair programming
• Source Code
• Storing secrets locally

Contributing

This handbook is open for everyone in our team to contribute, so feel free to make any changes to it.

If you want to get feedback about your changes or make a proposal, open a Pull Request and share it on a Slack channel on which you think the audience can provide feedback. For example, you could be very formal and call out for feedback on #people-and-culture saying:

[HANDBOOK] Hey, I’ve made this Pull Request on the handbook to explain Openness in the Communication section https://github.com/qatium/handbook/pull/1. If any of you could please review it and provide some feedback I’d very much appreciate it.

As long as you are confident about the PR, merge it.