Software & AI · From strategy to production

Your project

Software development collaboration model: structured from day one

Tools, access and rituals are defined with your project team.

A sprint review with the client on a video call and the task board

Three cornerstones of our collaboration.

01

Priorities & decisions

Define the scope, the points of contact and the validation rules so everyone shares the same view of the project.

02

Tools & access

Code repositories, tracking tools and environments are chosen and organized to fit your context.

03

Tracking & continuity

Rituals, reviews and regular exchanges provide visibility on progress and ensure knowledge transfer.

Who does what

Explicit roles from the start.

You

You set the priorities, make the business trade-offs and approve releases. Your key people bring the context, the rules and the access needed.

Etixio technical oversight

Our tech leads and CTO oversee the architecture and technical choices, set the code review standards and ensure continuity. In a dedicated team or staff augmentation, our developers work within your team, overseen by our leads; in a time and materials or fixed-price project, an Etixio lead runs the delivery.

The delivery team

Our engineers design, develop, test and document according to our engineering standard.

The details are in our organization and our method.

Getting started

How a software project gets started with Etixio.

Share your context

You tell us what you want to build or improve, the users involved and your technical environment. A first 30-minute conversation with our CTO helps identify the right collaboration format. For a dedicated team, we then present profiles for you to interview and approve.

You bring the need and the constraints. We propose a first scope to explore.

Set roles and decision rules

We clarify who makes the decisions, how much availability is expected from your team and how change requests are handled. Open assumptions are kept separate from decisions already made.

You name your key people. We tell you who is involved on Etixio’s side.

Open the tools and access

Our teams work inside your environment: your Git repositories, your ticketing tool, your environments and your security rules. Access is named and limited to what each person needs.

You grant access. We use it within the agreed framework and hand it back at the end of the engagement.

Start the tracking rhythm

Regular check-ins, demos and backlog reviews start with the first deliveries. Every change goes through code review and continuous integration before it is merged.

You approve the releases. We keep progress and decisions visible.

Day to day

How our software development collaboration model works week after week.

  • A tracking rhythm set from the start (regular check-ins, demos, backlog reviews)
  • Important decisions written down and shared
  • Any change of scope presented with its impact before it is committed
  • Work done in your tools, your repositories and your environments
  • Named access, limited to what each person needs and removed at the end of the engagement
  • Documentation and knowledge transfer as the work progresses, not only at the end

Depending on the format

Offshore project tracking that fits your collaboration format.

A dedicated team that evolves your product

Our developers join your team over time; they keep business and technical knowledge from one release to the next and follow the pace of your backlog. See dedicated teams.

Staff augmentation for your team

A short engagement: our engineers join your team for a given period, in your tools and following your methods, overseen by our tech leads. See offshore IT staffing.

A time and materials project

An Etixio lead drives the project toward its goal; time spent is tracked and billed, and the scope can evolve with your priorities. See the time and materials project.

A fixed-price project

We commit to deliverables, milestones and acceptance criteria defined together. An identified point of contact runs the delivery with you, milestone after milestone. See fixed-price projects.

An application in production

Fixes, enhancements, version upgrades and security follow the same method, including on software taken over from another provider. See application maintenance.

Frequently asked questions

Your questions.

Who runs the project?

We run it with you. You set the priorities and make the trade-offs; Etixio is accountable for the quality of what is delivered, under the oversight of our tech leads and CTO.

What is the time difference with your teams?

Madagascar is on UTC+3 (one to two hours ahead of Paris depending on the season) and Mauritius on UTC+4 (two to three hours ahead). Working days overlap widely with Europe. See Madagascar and Mauritius.

Which language do you work in?

Our teams in Madagascar and Mauritius are French-speaking. We also work in English, especially from Mauritius.

What happens if a team member changes?

The replacement is organized and the handover is supervised by our tech leads. Documentation kept up to date as the work progresses keeps the knowledge within the project. See our commitments.

Can we take back control of the project?

At any time. Code, repositories, access, tools, data and documentation remain yours.

Which tracking tools do you use?

Your organization’s tools when they exist: your ticketing tool, your repositories and your environments. Otherwise, tools are chosen with you to fit your context. Our guide to IT project tools can help with that choice.

Already working with Etixio?

Contact your point of contact for access to your project’s tools. This site does not include an authenticated client portal.

Talk to our CTO for 30 min

Preparing a collaboration

Find best practices for project management, quality and tool selection in the Etixio guides.

Explore the guides ›

What are you looking for?