How we work
Order you can see in the code
We run every add-on and every project by the same rules. This way we know about every change in the code and can take care of the highest quality of what we deliver to our clients.
In plain words: the kitchen of a good restaurant
In a good restaurant nothing happens by chance. There are recipes, an order board, a record of every change to the menu and a head chef who tastes each dish before it reaches the guest. Our work looks exactly the same.
Before we start, we write down the assumptions, features and tools of the project.
Every idea, task and reported bug goes on the board.
Every code change is recorded and can be traced back.
A change joins the project only after a second person checks it.
How an add-on or project is built
Assumptions
We describe the assumptions, required features and tools so the project runs smoothly.
Tasks
Every idea, task and bug goes into a system connected with Bitbucket and is discussed.
Sprints
We work in carefully planned sprints that follow the project roadmap.
Code review
Before merging, every change is checked for functionality and code quality.
Retrospective
After each sprint we discuss what to improve so the next work goes better.
Warranty on our add-ons
We make sure our add-ons stay up to date and secure. We want our code to be clear, functional and well commented, because that is what decides how long an add-on will serve your store.
Tools we use
Logos used for information purposes only.
Want to work with a well organised team?
Tell us about your project. We will start by writing down the assumptions.