Engagement model
Dedicated Microsoft Dynamics 365 development teams
In short
MS Dynamics Guys builds dedicated Dynamics 365 teams around the work you need to deliver. Combine product-specific developers, consultants and technical leadership under an agreed plan. We define the team, allocation, working hours and responsibilities with you before onboarding. Your business retains control of priorities and acceptance.
What makes a Microsoft Dynamics 365 team dedicated
A dedicated team is an agreed group of specialists who spend their contracted hours only on your system. The team proposal states each role's allocation, including part-time roles. The group stays together across releases, so knowledge of your processes, data and code builds up inside it.
A dedicated developer is a different offer: one specialist who joins your team for the hours agreed in writing. For one person, start with the role chooser for Microsoft Dynamics 365 specialists.
The rules on this page apply to every product we staff. Only the roles change, as the team shapes further down show.
Three features separate a dedicated team from other ways to add capacity:
- Several roles that depend on each other. The roles share one backlog and one plan, because most items need more than one skill before they are done.
- One named lead for the whole team. Someone plans the work of all roles together, not only single tasks. The contract says who holds that role.
- Continuing capacity, not one fixed result. The team works through your backlog, the ranked list of waiting work, which changes month by month. MS Dynamics Guys answers for staffing the agreed roles, and for daily direction when the lead is ours. We do not answer for a fixed scope by a fixed date.
Proposals also use managed team for a supplier-led team, and managed service for support of a live system. In a dedicated team from MS Dynamics Guys, you agree the roles, interview each person and pay for the team's capacity. Our guide to engagement models maps these proposal terms to the model behind each one.
When a dedicated team from MS Dynamics Guys fits
A dedicated team pays off when work continues for months and needs several skills in one plan. For one or two separate roles, or one defined result, it costs more than you need.
Signs that a dedicated team fits
- A roadmap after go-live, not only fixes. New processes, integrations and small projects keep arriving, release after release.
- Work that crosses roles. Most items need configuration, code and testing together, so separate hires would wait for each other.
- Context that takes time to learn. Your processes, data model and integrations are complex, and each new person needs time before their changes are safe.
- A product owner, but no technical lead, and priorities that keep moving. Someone on your side can rank the work and accept it, but nobody can direct developers every day. The work changes from sprint to sprint, so a supplier-led team fits better than a fixed scope.
- A partner leaves in the middle of a roadmap. Your implementation partner is handing over while planned changes still wait, and you want one stable group to learn the system once.
- A Microsoft partner's long client program. Your firm keeps the client relationship, and the team works inside your delivery. Delivery capacity for Microsoft partners adds the subcontract steps: disclosure, client-contract clauses and access.
When another model fits better
- One or two roles are missing, each can take separate items, and your lead can direct them. Add specialists through staff augmentation.
- You can write down one result in advance, such as a new integration. Buy it as an outsourced work package with acceptance criteria.
- Your main need is to keep a live system running: incidents with agreed response targets, monitoring and small fixes. A support service fits that better than a team.
- The work ends within a few weeks. Forming a team, and handing over at the end, would take too large a share of the time.
- Nobody on your side can rank the work or accept it. A team without a product owner builds the wrong things faster.
- You want people on standby for work that may come later. We staff teams for defined work, not reserved capacity.
Does a dedicated team from MS Dynamics Guys work under your lead or ours?
Either. The contract states which model applies before the team starts. To choose, answer one question. Does someone on your side have the time and the product knowledge to plan each sprint, settle technical questions and review the team's work? A sprint is a short, fixed planning cycle of a few weeks.
- Client-led. Yes, you have that person. Your lead directs the team every day. MS Dynamics Guys provides the people, keeps the team staffed and manages any change of person. Unlike several separate specialists, a client-led team shares one capacity plan and one charter. MS Dynamics Guys also runs one continuity process for the whole team.
- Supplier-led. No, or that person has too little time. A team lead from MS Dynamics Guys plans and directs the daily work against the priorities your product owner sets.
- Split. A supplier-led variant. Your product owner and architect keep the final say on design. Our lead runs sprint planning, task assignment and code review. The contract lists which decisions sit on which side.
In every lead model, business priorities and acceptance stay with you. So does the decision to release to production, unless you delegate it in writing. How defects found after acceptance are handled is agreed in writing for each engagement.
| Responsibility | Client-led team | Supplier-led team |
|---|---|---|
| Business priorities and the order of the backlog | Your product owner | Your product owner |
| Sprint planning and daily task assignment | Your lead | The MS Dynamics Guys team lead, against your priorities |
| Design decisions inside one app | Your lead or architect | The MS Dynamics Guys team lead, with your approval for changes that affect other systems |
| Code review and the checks each item must pass | Your rules, applied by reviewers you name | Rules you approve, applied inside the team |
| User acceptance testing (UAT) and acceptance | Your key users and product owner | Your key users and product owner |
| Release to production | Your release approver | Your release approver, unless you delegate it in writing |
| Staffing, replacements and continuity | MS Dynamics Guys, under the notice and replacement terms in the contract | MS Dynamics Guys, under the same terms |
| Capacity reports and planned absences | MS Dynamics Guys reports them, and your lead plans around them | The MS Dynamics Guys team lead plans around them and reports them |
| Repository, work tracker and environments | Yours from the first day | Yours from the first day |
| Handover when someone leaves | A note from the person leaving, checked by your lead | A note from the person leaving, checked by the MS Dynamics Guys lead and accepted by you |
Microsoft's implementation guidance lists common problems in project leadership. One is the wrong role holding accountability or authority. For example, a technical role is accountable for business outcomes, or a business role has authority over technical decisions. The table above gives each decision to the role that fits it. Your product owner decides what the business needs, and the team lead decides how the team builds it.
What the team lead does in every sprint
The lead role is a set of duties, not a job title. Whoever holds it, on your side or ours, does this work:
- Turns the product owner's priorities into a sprint plan that fits the team's capacity.
- Gives each item to the right role, so code goes to developers and process changes go to consultants.
- Checks whether configuration, a standard feature or a Microsoft Marketplace app meets an item before anyone writes code.
- Keeps the definition of done: the checks every item passes before it counts as finished, such as review, tests and updated notes.
- Finds items that wait for a missing decision, and raises them early with the person who can decide.
- Tracks the capacity used and the planned absences, and warns before the plan slips.
- Keeps a decision log, so the reasons behind designs survive changes of people.
The lead does not set business priorities or accept work on your behalf.
In a small team, the lead also builds or configures part of the time. In a larger team, the lead role can take a full person's time. The contract records which applies and how much of the lead's time is included.
Team composition: which roles, and how much of each
Start from the work in your backlog, then choose the roles. Not every role needs a full person. The last two columns show when a role should grow or shrink.
| Role | Allocation to plan for | Add or increase it when | Reduce it when |
|---|---|---|---|
| Product owner (your side) | Part of a business lead's week, in every sprint | Every team needs one from the first day | Not reduced: it stays for the whole engagement |
| Team lead | Part of a senior member's time, or a full role in a larger team | Decisions start to slow the team down | The team shrinks to one or two people |
| Developer in your product's language | Full time while code items arrive in every sprint | Code items wait longer than one sprint | Code items drop to a few a month |
| Functional consultant | Full time while processes are designed or rolled out, part time afterwards | A new process, company or country is planned | Processes are stable and requests are small |
| Solution architect | Part time, for design reviews and decisions | Changes cross apps, integrations or security | The design is settled and changes stay inside one app |
| Quality assurance (QA) engineer | Part time, or full time before large releases and Microsoft updates | Regression testing takes more time than developers can give | Tests are automated and the team keeps them up to date |
| Release engineer | Part time | Pipelines, environments and deployments have no owner | Releases run from a documented pipeline that the team maintains |
| Integration engineer | For the length of an integration phase | A new or failing interface is in the plan | The interface is live, monitored and documented |
| Data migration engineer | For the length of a migration phase | Data must move from an old system | Your data owners sign off the reconciled data |
Write each part-time role, with a name and its share of time, into the team charter: the one-page agreement on how the team works. The demonstration charter further down this page shows the format.
Illustrative team shapes by product
These shapes show how the roles combine on different products. They are starting points for a discussion. They are not team sizes we promise, and they say nothing about who is available.
| Product track | Continuing work it suits | Illustrative shape | Lead model to consider |
|---|---|---|---|
| Customer relationship management (CRM): Microsoft Dynamics 365 Sales or Customer Service | Process changes, C# plug-ins and integrations released every month after go-live | A team lead who also designs, one or two CRM developers, a functional consultant, and testing time in every sprint | Client-led if your CRM owner can also lead technically; supplier-led if you have a product owner but no technical lead |
| Microsoft Dynamics 365 Business Central | Extensions in AL, the programming language of Business Central, plus reports, integrations and setup changes around the April and October updates | A team lead who also writes AL, one or two AL developers, a part-time functional consultant, and extension tests before each major update | Supplier-led while nobody on your side reviews AL code; client-led once you have a technical lead |
| Microsoft Power Platform around Microsoft Dynamics 365 | Apps, flows and tables that several departments request | A team lead who also builds, Power Platform developers, and part-time help with environments and governance | Client-led if a platform owner already runs governance; supplier-led otherwise |
| Microsoft Dynamics 365 Finance or Supply Chain Management | Extensions in X++, the programming language of finance and operations apps, and process changes between Microsoft's service updates | A team lead, X++ developers, a finance or supply chain functional consultant, and regression tests before each service update you take | Split: your process owners keep functional decisions, and the lead runs delivery |
The real size of a team depends on the work waiting, your release dates and how much of the work your own people keep. Before you plan around a shape, we tell you in writing which roles MS Dynamics Guys can staff.
How team capacity is planned and reviewed
Capacity is the time each role gives your work in a sprint, counted in person-days. We plan it with your product owner before the team starts, then review it as the work changes.
List the work for the next releases
Include backlog items, expected change requests, the support tickets the team will take and testing for Microsoft updates. Real items size a team better than a headcount target.
Turn the work into roles
Group the items by skill: code, configuration, design, testing and release work. Each group points to a role and a share of one person's time.
Reserve time for work that is easy to forget
Code review, notes, regression tests, onboarding of new members and planned holidays all take time. A plan without this reserve slips in the first busy month.
Compare the plan with the time used
Your product owner and the team lead review planned and used capacity at an interval you agree, such as each release. Then they keep, add or reduce roles.
Change the team through the contract
A new role goes through the same assessment and your interview as the first members. A reduced role follows the notice and the handover plan agreed in writing.
These reviews follow Microsoft's implementation guidance, which advises updating resource allocation as the project changes.
Microsoft Dynamics 365 Sales, Customer Service and Microsoft Power Platform. Microsoft plans new features in two release waves a year, starting in April and in October. In model-driven apps, such as Sales Hub, a release channel decides when users get those features. The monthly channel turns them on every month, and the semi-annual channel in April and October. Sales Hub and Customer Service workspace use the monthly channel unless your team changes it. Plan regression test time in a sandbox copy of production before each release on your channel.
Business Central online. Microsoft ships two major updates a year, in April and October, and minor updates in the other months. Preview sandboxes open about a month before each major update, but they contain demonstration data, not your production data. Plan two rounds of tests for each major update: on the preview, then on a sandbox copy of production when the update arrives. Microsoft also recommends testing critical business scenarios before each minor update reaches production. An extension that still blocks a major update after the update and grace periods can be uninstalled automatically, although its data is kept. Business Central on-premises gets the same changes in a later cumulative update.
Finance and operations apps. Microsoft releases four service updates a year, and you must take at least two of them. When Microsoft applies an update, your sandbox gets it seven days before production. Prepare the regression tests before that week starts.
How does MS Dynamics Guys keep a dedicated team stable when people change?
People change in every long engagement. They take holidays, fall ill or move on, and no supplier can promise a team without changes. In a dedicated team, MS Dynamics Guys answers for the team's agreed capacity, not only for single people, so the team itself holds the knowledge:
- No area depends on one person. Another engineer in the team reviews each code change, as in our delivery model, so two people know every app, extension and integration. Design notes, release steps and the decision log are updated with each item, in your repository or wiki.
- The capacity plan absorbs absences. Holidays and training enter the plan before the sprint starts. The lead moves work between team members, so a sprint carries less work instead of slipping.
- A successor joins a team that already knows the work. A change of person follows the notice and handover period in the team charter. The lead checks the handover note of the person who leaves. After an unplanned departure, the successor starts from the shared notes and the decision log, with team members to ask. Every successor passes the same assessment and your interview before joining.
- The lead role gets extra care. When the lead changes, the handover also covers the sprint plan, the decision log, open risks and agreements with your stakeholders.
Replacement times, and who pays for any overlap during a handover, are commercial terms. We agree them in writing for each engagement and do not quote them in advance.
How a dedicated team scales down or ends
Plan the end of a team when you plan its start. Code, notes and the decision log sit in your systems from the first commit, so scaling down moves knowledge, not files.
Agree the reason and the target
The roadmap is delivered, the backlog shrinks or your own hires are ready. Your product owner and the lead agree in writing what the smaller team, or your own team, will own.
Name the next owner of each area
List each app, extension, integration and pipeline. Then name who keeps it: your team, a smaller team or a support service.
Reduce the team in steps
Roles tied to a finished phase leave first. The lead and one person for each critical area stay until you accept the handover.
Transfer knowledge on real work
Your people make the next changes while team members review them. Then the roles swap: your people review, and leaving members only answer questions.
Hand over and close access
Each leaving member hands over notes, open items and known risks. Your administrator removes their accounts and changes any shared secrets they used.
Notice periods for reducing or ending a team are agreed in writing for each engagement.
For each person who leaves, the exit checklist on the staff augmentation page applies as well.
An illustrative Business Central team over one year
How a dedicated team starts, and what you can check
Each step gives you something to read or test before you commit further. We give no start date until the roles are confirmed.
- A written team proposal. It sets out the shape, each role's allocation, the lead model we suggest and the assumptions behind them. It also says which roles MS Dynamics Guys can staff.
- A role-specific assessment for each person. Team members pass the same assessment as individual specialists, before you meet them. Read how we assess specialists for the tasks and who reviews them.
- Your interviews. You interview each person, if possible on items from your own backlog, and you decide who joins.
- An agreement and a team charter. The agreement sets the commercial terms and who owns the code and documents the team produces. The charter records the lead model, decision rights, capacity reviews, the definition of done, changes of person and scale-down triggers. The demonstration below shows the format.
- Access and onboarding. Nobody gets access before the agreement is signed. Your administrator then gives each member a named account with only the roles the work needs, in development and test environments first. Your team or the team lead walks each new member through the system and its rules before their first work item.
- A first sprint you accept. Your product owner plans it with the lead, and your team accepts the results against criteria it writes.
Approved Microsoft Dynamics 365 projects are described in our case studies. The steps above let you check the arrangement itself.
| Charter item | What it records | Example entry |
|---|---|---|
| Lead model | Client-led, supplier-led or split, and who holds the lead role | Supplier-led. The MS Dynamics Guys team lead plans sprints, and the client's finance director owns priorities. |
| Decision rights | Who decides priorities, designs, acceptance and production releases | Priorities and acceptance: product owner. Designs inside one app: team lead. Changes that affect other systems: client architect. |
| Roles and allocation | Each role, the person in it and their share of time | Team lead, part time. Two developers, full time. The client's administrator, part time. |
| Capacity review | When planned and used capacity are compared, and by whom | At each release planning meeting, by the product owner and the team lead. |
| Definition of done | The checks every item passes before it counts as finished | Code reviewed, tests passing, design note and release note updated. |
| Change of person | Notice, handover, and how a successor is assessed and interviewed | As in the signed agreement, with a handover note from the person leaving. |
| Scale-down triggers | When the team shape is reviewed for reduction, and the first steps | Less than two sprints of planned work: review the shape and name the next owners. |
This charter is an original demonstration. It does not come from a client engagement. A real charter is drafted with your product owner and signed together with the agreement.
Questions about dedicated Microsoft Dynamics 365 teams
How many people should our first dedicated team have?
As few as the work allows. Size the team from the items planned for the next releases, not from a headcount target. Full-time roles cover work that arrives in every sprint. Part-time roles cover design reviews, testing peaks and releases. A team that outgrows its product owner waits for decisions, so add people only when decisions keep pace.
Can our own employees work in the same team?
Yes. A mixed team shares one backlog, one definition of done and one set of review rules. Your employees stay under your management. Our people work under the agreement between our companies. Decide who reviews whose code before the first sprint. A mixed team also makes the final handover easier, because your people already know the work.
Who in the team needs to share our working hours?
Shared hours are agreed in writing for each engagement. In a client-led team, each member needs overlap with your lead, who directs the work every day. In a supplier-led team, our lead needs the most overlap with your product owner: for sprint planning, the acceptance review and production releases. Other members then need shared hours mainly for work with your people, such as code reviews in a mixed team. Send your time zone and working hours with your first message.
Can a dedicated team also support our live system?
It can, if every sprint reserves time for incidents and the contract says who responds outside working hours. Frequent incidents then slow roadmap work, and the capacity review shows by how much. If you need agreed severity levels and response targets, a separate support service fits better. The team can then focus on changes.
How is a dedicated team priced?
The rate basis is agreed in writing for each engagement, and this page quotes no prices. The written team proposal lists each role and its share of time, so the price follows the shape and the term you agree. In a supplier-led team, the contract also states how much of the lead's time is included. How planned absences and a change of person affect the invoice is agreed in writing too. To change the cost, change the shape at a capacity review, through the contract. The guide to engagement models compares how each model shares the risk of work that takes longer.
Can the lead model change during the engagement?
Yes, through a written change to the agreement and the team charter. A common change is from supplier-led to client-led, once you hire your own technical lead. You can agree a period in which your new lead directs the sprints while our lead reviews the work. Then our lead hands over the sprint plan, the decision log and open risks. To take the work fully in-house, follow the scale-down steps on this page.
What the proposal should make explicit
- Product, environments and workstream.
- Proposed roles, assessment evidence and interviews.
- Named lead, reviewers and business acceptance owner.
- Allocation per role, working-hour overlap and confirmed start plan.
- Rate basis, included coordination and separate costs.
- How priorities, absence, replacement and exit are handled.
- Source access, documentation and handover responsibilities.
Use the team-and-budget planner to prepare a comparable brief. Example team structures are planning options, not preassembled teams or current availability claims.
Five specialists in a client-led AX migration
Beaumont Group’s five-person AX migration team comprised two X++ developers, Finance and Supply Chain consultants, and a migration engineer. The client signed trial reconciliation for three entities on 10 May 2024 and authorised cutover on 17 May.
Your next step
Plan your Microsoft Dynamics 365 team
Send the product and version, the work planned for the next releases and who on your side owns priorities. Tell us whether someone can lead the team technically. We reply with a proposed shape, the lead model we would suggest and the roles we can staff, before any introduction.
Product documentation referenced on this page
- Organize your Microsoft Dynamics 365 project team Microsoft Learn, checked October 4, 2026
- Microsoft Dynamics 365 release schedule Microsoft Learn, checked October 4, 2026
- Release channel for your model-driven app Microsoft Learn, checked October 4, 2026
- Change release channels for model-driven apps Microsoft Learn, checked October 4, 2026
- Supported customizations for Microsoft Dataverse Microsoft Learn, checked October 4, 2026
- Apply business logic using client scripting in model-driven apps Microsoft Learn, checked October 4, 2026
- Programming in AL Microsoft Learn, checked October 4, 2026
- Business Central update cycles Microsoft Learn, checked October 4, 2026
- Understanding the infrastructure of Business Central online Microsoft Learn, checked October 4, 2026
- X++ language reference Microsoft Learn, checked October 4, 2026
- Service update availability for finance and operations apps Microsoft Learn, checked October 4, 2026