Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Glossary

MOA, MOE, AMOA: definition of the three roles in an IT project

Domain

Project management and PMO

In brief

MOA, MOE and AMOA name three roles in an information system project: the maîtrise d'ouvrage (project owner), on whose behalf the system is built, the maîtrise d'œuvre (project contractor), which designs and builds it, and the assistance à maîtrise d'ouvrage (business-side project support), which supports the first without deciding for it. The first two come from construction; their use in IT is a matter of custom.

Page contents

Definition of MOA, MOE and AMOA

Three acronyms, three roles in an information system project. MOA stands for maîtrise d’ouvrage (project owner): the entity on whose behalf the system is built, which expresses the need and accepts the result. MOE stands for maîtrise d’œuvre (project contractor): the entity that designs and builds the solution. AMOA stands for assistance à maîtrise d’ouvrage (business-side project support): support provided to the first, with no power to decide in its place.

Each acronym names a role held in a project; usage extends it to the department that holds it.

A vocabulary borrowed from construction

Maître d’ouvrage and maître d’œuvre belong to the vocabulary of construction. The Trésor de la langue française informatisé (entry “maître”, consulted on cnrtl.fr on 12 November 2026) files them under the label “Dans le domaine industr.” (in the industrial field), with construction examples, and defines the first as the “natural or legal person who orders the execution of a work and finances it”, and the second as the “natural or legal person, agent of the maître d’ouvrage and responsible for carrying out the works” (our translation).

French public procurement uses these terms. The website of the Mission interministérielle pour la qualité des constructions publiques (miqcp.gouv.fr) lists, under the heading “Loi MOP et textes apparentés”, Book IV of Part Two of the French public procurement code among the texts in force, and Law No. 85-704 of 12 July 1985, known as the loi MOP, among the former texts.

Who holds what in an IT project

In IT projects, the use of the three acronyms and the split that follows are a matter of custom, not a rule: each organisation adjusts them.

  • The MOA falls to a business department: expression of the need, budget, scope decisions, acceptance testing, preparation of users.
  • The MOE falls to the IT department, a service provider or both: technical design, build, testing, go-live. When entrusted to a service provider, it goes through a contract, and our article fixed fee or time and materials compares the two models; after go-live, maintenance can pass to third-party application maintenance.
  • AMOA strengthens the MOA: help with drafting the specifications, monitoring the project, preparing acceptance testing.

The downside of a useful separation

The separation names one person responsible for the need and one responsible for the solution. Its possible downside: a need frozen in a specification document, then judged inadequate at acceptance. An AMOA placed as a screen between users and builders lengthens this circuit.

MOA, MOE, AMOA and agile roles: not to be confused

The Scrum Guide (scrumguides.org, November 2020 version) defines three accountabilities within a single team, the Scrum Team: Product Owner, Developers, Scrum Master. The correspondence with MOA and MOE remains approximate.

  • Like the MOA, the product owner is responsible for the value of the product and the order of requests. The product owner is a person, a member of the team, and not an entity that commissions another.
  • The Developers build, like the MOE. The Guide provides for neither sub-teams nor hierarchy in the Scrum Team.
  • AMOA has no equivalent there. The Product Owner can delegate management of the Product Backlog, while remaining accountable for it.

Nor should AMOA be confused with a PMO: the PMO equips project management, while AMOA works on the content of the need.

A typical case: weighing members’ deliveries at a cooperative

Imagine an agricultural cooperative replacing its software for weighing and paying for members’ deliveries. The member relations department holds the MOA: it describes the payment rules, decides on scope and will sign off acceptance. The MOE is shared between the IT department and a service provider, which configures the software package. An AMOA consultant runs the workshops and writes the acceptance test cases.

The service provider proposes simplifying a bonus rule. The consultant investigates the consequences; the member relations director decides.

When several projects, each with its own MOA and MOE, contribute to the same outcome, their overall governance is covered on our programme management page.

Insights

Further reading

All insights
The signs of poorly prepared change management, spotted at the stages of an IT project

Change management in an IT project brings together the actions that prepare the users of an information system to work with it, from scoping to the aftermath of go-live. Management Square shows here how to spot, document by document, poorly prepared change (users absent from scoping, impacts discovered in testing, unnamed change agents, go-live without support), and what remains to be done.

Read the analysis
Why do IT projects fail? A reading through the signs of drift

An IT project fails, under the convention adopted here, when it misses its deadline, its cost, its scope or the expected benefit beyond the variance its sponsor had accepted. Rather than a list of causes, Management Square offers a reading method here: the observable signs of drift at each stage of the project, what each one can reveal and the response it calls for.

Read the analysis
Running a steering committee that delivers decisions

A steering committee is the body where the people with authority over a project take, at regular dates, the decisions that exceed the project manager's delegation. Management Square proposes here a method for running a steering committee, in order: purpose and members, pack sent before the meeting, a running order centred on decisions, a record written during the meeting, follow-up until the next meeting.

Read the analysis

FAQ

Frequently asked questions

Another question? Ask us

What is the difference between MOA and MOE?

The MOA, maîtrise d'ouvrage (project owner), is the entity on whose behalf an information system is built: it expresses the need, decides on scope and accepts the result. The MOE, maîtrise d'œuvre (project contractor), is the entity that designs and builds the solution, in-house or at a service provider. This split between MOA and MOE is a matter of custom, and each organisation adjusts the detail.

What does the acronym AMOA stand for?

AMOA stands for assistance à maîtrise d'ouvrage, or business-side project support. AMOA refers to support provided to the project owner, by an internal team or a service provider: help with expressing the need, monitoring the project and preparing acceptance testing. AMOA advises and investigates, while the decision remains with the project owner.

Where do the terms maîtrise d'ouvrage and maîtrise d'œuvre come from?

Maître d'ouvrage and maître d'œuvre come from the vocabulary of construction. The Trésor de la langue française informatisé, which illustrates them with construction examples, defines the maître d'ouvrage as the person who orders the execution of a work and finances it, and the maître d'œuvre as the agent of the maître d'ouvrage, responsible for carrying out the works. IT projects adopted these two terms through usage.

Is the product owner the MOA of an agile project?

The comparison between product owner and MOA is approximate. Like the project owner, the product owner is responsible for the value of the product and the order of requests, but the Scrum Guide makes this role a person, a member of the Scrum Team, and not an entity separate from the one that builds. The Scrum Guide provides for neither sub-teams nor hierarchy within the Scrum Team.

Can the same team hold both the MOA and the MOE?

The same team can hold both the MOA and the MOE, for example for an internal tool that it specifies and builds itself. The two roles are still worth distinguishing: deciding what is expected and deciding how to build it are two responsibilities. When the MOE is entrusted to a service provider, the distinction between MOA and MOE can be read in the contract.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.