Whether you want to build a new webshop, require a module, request maintenance, or implement a minor change, we utilize our project tracking system JIRA by Atlassian. Stay informed about your ongoing tasks and associated costs with just one click. We prioritize transparency and clear communication through our system.
Say goodbye to long color-coded email tables or bullet points with “My answers in blue.” Several years ago, we closed that chapter for good and adopted JIRA, the issue and project tracking software by Atlassian. This is not just a simple ticketing system; we actively collaborate on the project board to ensure seamless management of your software.
With the guidance of our project managers, we make it easy for you to navigate the system and give you full control over your project.
Voordat we aan een opdracht beginnen, omschrijven we deze eerst nauwkeurig in de ‘Backlog’. Hebben we de opdracht goed begrepen en alle wensen opgenomen in de omschrijving? Dan gaan onze ontwikkelaars aan de slag met een indicatie van de benodigde tijd en kosten, waarna we wachten op jouw akkoord. Pas na dit akkoord, dat je kunt geven binnen JIRA, starten we definitief met de uitvoering.
In de backlog bepalen we vooraf alle opdrachten. We werken gericht aan jouw wensen, of dit nu per maand in een sprint is of op aanvraag. De scrum-methodiek is ons niet onbekend, waardoor we flexibel en efficiënt kunnen schakelen.
Once we receive your approval, the task will be moved to ‘Ready for Development’. This marks the point where the developer can begin work. When the developer starts on the task, you will receive a notification indicating that the task is now ‘In Development’, ensuring you stay informed about the progress.
After the developer completes the task, it is submitted for ‘Review & Merge’ to their colleagues. They perform a quality check on the delivered work, verifying compliance with coding standards and identifying any necessary adjustments. Only after this step is it ready for testing.
Before the task is submitted for review, it first undergoes our ‘Q&A’ process. To ensure that incomplete or insufficiently tested work is not delivered, the Q&A team reads, understands, and tests the task. Only when the Q&A confirms that the task functions according to the description is it presented for further review.
When we reach the ‘Acceptance’ stage, it is your responsibility to test the task. The task has been tested for quality and compliance with the description, but does it meet your initial expectations? You can test it in a staging environment at your convenience. Only when you are satisfied, we proceed to the live webshop. If you find anything, we will return to ‘Feedback’ and repeat the testing and acceptance process based on your feedback.
Only after your approval and when you have moved the task to ‘Ready for Release’, we will push the task to the live webshop. We will schedule an appropriate time for this and update the webshop. Once the task is visible to the online world, it will be moved to ‘Live Production’.
After 7 days, the task will automatically be moved to ‘Done’ and archived. If a keen customer spots something, we will return to ‘Feedback’. If the task does not meet expectations, our smart deployment system allows us to roll back a version within 5 minutes.