This is the way
- Fully Remote
- Everyone works in the CET timezone +-2 hours
- You can go into other timezones temporarily (for a few months even), but we don’t like to hire outside of our timezone(s).
- Communicate mostly with Slack + Hangouts and Gmail when applicable.
- Project documentation in a git repo and Notion when applicable.
- Daily morning sync (5-10min) at 9 am
- Weekly chitter-chatter (~30min) on Fridays around noon.
- 3 to 4 yearly real-life meet-ups. Company pays for travel, hotels, and dinners.
Please do take vacations. For longer times off it’s good to give proper advance notice so we can plan our project staffing around it. For shorter times off, like for longer weekends etc a few days to a week in advance is enough.
To increase the visibility, we have a company-wide calendar (id: email@example.com to add the calendar). Please use it when your dates are settled.
- We stick to our Technology Radar guidance so we can move around and maintain any project more easily
- Anyone can challenge it, but it has to be reasoned.
- Test according to the quality needed.
- Move fast but don’t break stuff unnecessarily.
- On delivery projects, unless otherwise required by clients, we use a lightweight Kanban approach to project delivery.
- Projects always start with a Kickoff which everyone attends (client + stakeholders + makers)
- Weekly meeting w/ Client
- Developers demo what they have done
- We discuss open issues that need stakeholder feedback
- Client prioritizes work, and we enqueue enough work for the following week
- Beyond that communicate as needed. This depends on the project.
- On team amendment cases the process/ways of working is almost always defined by the client. However, most of our clients are young startups so their culture and ways of working are often very similar to ours.