Simplify your projects with the Agile (Scrum) methodology

Tired of complex and endless projects? Looking to work with a team that understands your needs and delivers results on time? Look no further! At Tinx, we are dedicated and passionate about creating reliable and challenging technical integrations between Microsoft Dynamics NAV/D365 Business Central and commonly used e-commerce platforms such as Magento, Adobe Commerce, Shopware, WooCommerce, Shopify, Amazon, ChannelEngine, CloudSuite, and MplusKASSA.

To achieve this, our consultants have experience and knowledge in the aforementioned e-commerce platforms, NAV/D365 Business Central, and their associated APIs. But this is just one part of a successful implementation. Equally important is customer engagement, planning, and ensuring that the project is delivered within the set deadline.

Last year, our consultancy team transitioned to a self-managed model. This means that Tinx consultants oversee projects from A to Z following the Agile methodology (Scrum).

Key agile benefits:

1. Flexibility: Our Tinx consultants can quickly adapt to changes and adjust priorities during the project.
2. Customer Engagement: Agile encourages close collaboration between the Tinx consultant team and you as the customer, ensuring that the final solution meets your expectations and needs.
3. Quality: Regular feedback and cyclical work (sprints) allow us to address issues promptly and make improvements, resulting in higher product quality.
4. Transparency: Agile provides a high level of transparency within our team and to stakeholders, ensuring everyone has a clear view of the work and expected outcomes.
5. Improved Communication: Agile promotes regular communication among team members, leading to a better understanding of requirements, expectations, and challenges we encounter.
6. Faster Time-to-Market: Thanks to Agile, we can deliver working software more quickly. Regular releases significantly shorten the time-to-market.
7. Risk Management: Agile helps identify and mitigate risks during the development process. Regular inspection and adaptation ensure that potential risks are well managed.

Once the necessary paperwork for your project is signed, we start immediately. We divide the lifespan of your project into 4 phases, which we will explain below using an example project for customer A.

Phase 1: Start 

Access to the right systems
We start by obtaining the necessary access to various systems. For this purpose, we have established a dedicated role within Tinx: the Gatekeeper; any member of our team can fulfil this role.

In the case of customer A, we have access to WordPress, Shopware, and D365 Business Central. Simultaneously, our internal IP addresses are whitelisted for their systems.

Downloading Tinx software and establishing connections
Customer A has downloaded the Tinx WooCommerce & Shopware Connectors from Microsoft AppSource and installed them in D365 Business Central. A test connection is set up to validate whether a successful API connection is possible between the different systems.

Official project scheduling
After successful validation, internal approval is granted to officially schedule the project. This is determined during our weekly team meetings. The project’s start (kick-off) can now be scheduled, allowing the next phase to begin!

Phase 2: Planning & implementation  

Kick-off meeting and communication agreements
During the kick-off meeting with customer A, we go through the agreed-upon scope documents (in collaboration with our sales department) in detail. Since the go-live deadline is quite soon, we agreed to meet digitally with the customer twice a week to discuss project progress and address any questions or concerns.

Depending on the customer’s preferences, various forms of communication are possible. When we start implementing, we ensure that the customer receives at least one weekly update on the project’s status.

Additional functionalities needed during the project
During implementation, both the Tinx Consultant and the customer realize that additional functionalities are required and must be achieved within the set deadline. Based on the evolving insights of customer A, we advise them to request additional hours for the desired functionalities. A Tinx Consultant assesses the estimation and impact on the project. Once the customer agrees, the project resumes, including the newly defined functionalities.

Ultimately, the project was delivered one month ahead of the deadline. Customer A receives a demo of the delivered project, allowing them to start testing.

Phase 3: User acceptance testing (UAT) and go-live  

Customer A reserves two weeks internally for independent testing. They can easily conduct independent testing using a set of test tasks we have prepared. This tool also allows them to ask questions and provide feedback on individual tasks.

From the test results, we receive feedback from the customer and address this feedback within one week. Customer A approves the current setup for the go-live!

Upon the customer’s request, we launched the project over the weekend to minimize the impact on business processes, especially for the logistics and finance departments.

Phase 4: Aftercare 

We begin with aftercare. The consultant who worked on the project remains on standby for two weeks after the go-live. If any issues or questions arise during these two weeks, the Tinx Consultant is available to address them promptly.

If these two weeks proceed smoothly, the project will be transferred to our support department. The support department assists the customer further in addressing any potential questions.

Interested in one of our solutions?

Or do you have questions about our projects? Please contact us; we’re happy to assist you.

You can also check our customer stories for practical examples!