Dynamics 365 Project Operations - Simply Explained
Key Takeaways
- Mirko Peters explains how Microsoft Dynamics 365 Project Operations connects sales, project management, resource planning, time tracking, expenses, billing, and financials into a single platform.
- Disconnected systems often lead to communication gaps between departments, resulting in uncoordinated project scopes, mismanaged staff availability, and inaccurate customer invoicing.
- The complete lifecycle of a customer project is tracked seamlessly—from initial quotes and project contracts to work breakdown structures, resource bookings, and final delivery.
- Project operations bridges the gap between operational success and financial profitability by helping organizations monitor actual costs, resource expenses, and billable hours.
- Advanced capabilities like Copilot and AI agents assist with drafting project status reports, preparing time entries, and managing expense reporting within Dynamics 365 Project Operations.
Customer projects can become complicated quickly. Sales has the customer relationship and quote. Project managers have schedules and tasks. Resource managers need to know who is available. Consultants record hours and expenses. Finance needs to understand costs, revenue, and what can actually be invoiced.In this episode of Microsoft Knowledge Nuggets on M365 FM, Mirko Peters explains Microsoft Dynamics 365 Project Operations and how Microsoft connects project sales, project management, resource planning, time tracking, expenses, billing, and financial processes within one project-focused platform.The episode follows the complete lifecycle of a customer project—from the first sales conversation and project quote through planning, staffing, delivery, time and expense management, financial tracking, and finally customer invoicing.
WHAT IS DYNAMICS 365 PROJECT OPERATIONS?
Microsoft Dynamics 365 Project Operations is designed for organizations that sell project-based services. These businesses are not simply selling products. They are selling expertise, professional services, consulting hours, engineering work, implementation projects, design services, development work, or other customer engagements where people, time, costs, contracts, and billing need to remain connected.Without a connected system, different departments often create their own version of a project. Sales knows what was promised. Delivery creates another project plan. Employees record hours somewhere else. Finance receives approved hours and expenses later and then tries to determine what should appear on the customer's invoice.Dynamics 365 Project Operations connects these areas around shared project information.The objective is not to make every department use exactly the same interface. Salespeople, consultants, project managers, resource managers, and finance professionals have different responsibilities. What matters is that the underlying project information remains connected.
FROM SALES OPPORTUNITY TO PROJECT DELIVERY
A customer project begins before the first task is created.During the sales process, someone needs to determine what the customer actually needs, which roles will be required, how many hours may be necessary, when work could start, what the project should cost, and how the customer will be charged.Dynamics 365 Project Operations helps organizations capture this information while the opportunity is still being developed.This creates an important connection between what sales promises and what the delivery organization eventually needs to provide.Instead of project managers receiving an email saying that sales has apparently sold several weeks of consulting, the approved scope, roles, estimated effort, pricing, dates, and billing conditions can become part of the connected project record.
PROJECT QUOTES AND CONTRACTS
Quotes and project contracts establish the commercial foundation of a customer engagement.A quote represents what the organization proposes to sell. It can include planned work, estimated effort, project roles, pricing, expected dates, and billing conditions.Once the customer accepts the proposal, the project contract records what the customer actually agreed to purchase.This distinction is important because delivery teams should work against the accepted customer commitment rather than an earlier version of the proposal that may have changed during negotiations.Contracts can also establish whether customers are charged according to time worked, a fixed project price, milestones, or other agreed billing arrangements.
PROJECT PLANNING AND WORK BREAKDOWN STRUCTURES
After the customer accepts the project, the promise needs to become an executable plan.Project managers break large outcomes into smaller pieces of work. This structure is commonly called a Work Breakdown Structure, or WBS.For example, a cloud migration project might contain discovery, design, implementation, testing, customer review, deployment, and closure phases.Each part can then contain individual tasks with planned dates, expected effort, responsibilities, and dependencies.Dependencies are particularly important because project activities rarely happen completely independently. Design may depend on discovery. Testing depends on implementation. Customer approval may depend on testing.When one activity changes, project managers need visibility into what that change could mean for the rest of the schedule.
PROJECT MILESTONES
Milestones provide recognizable checkpoints during a project.A milestone might represent design approval, completion of testing, delivery of a major project component, customer acceptance, or another significant event.Unlike normal tasks, milestones typically represent a point in the project rather than a block of working hours.They are useful for communicating progress and can also have commercial importance. In milestone-based engagements, reaching an agreed milestone may trigger part of the customer's billing schedule.This connects project delivery directly with the commercial agreement.
PROJECT TIME TRACKING
Time entries are more than administrative timesheets.When employees record time against specific projects and tasks, the organization gains information about how much effort the work actually requires.Project managers can compare planned effort with actual effort. If discovery was expected to require 40 hours but has already consumed 60 hours, that difference becomes visible while the project is still active.That does not automatically mean the project is failing. The customer environment may simply have been more complicated than expected.The important point is that the organization now has information it can act on rather than discovering the problem after the project has finished.Approved time can also become an important input into project costs and customer billing.
PROJECT EXPENSE MANAGEMENT
Customer projects frequently involve costs beyond employee time.Consultants may travel to customer locations, purchase approved services, or incur other project-related expenses.Dynamics 365 Project Operations can associate these expenses with the relevant customer project instead of allowing them to disappear into disconnected receipts, emails, or financial records.This creates better visibility for project managers and provides finance with clearer information when reviewing project profitability and customer billing.
RESOURCE MANAGEMENT AND STAFFING
A perfect project plan is useless if the required people are unavailable.Resource management connects project requirements with employees and contractors who have the appropriate skills and availability.A project manager may know that a security specialist is required for two weeks without initially knowing which individual will perform the work.Resource management allows organizations to consider both requirements.Someone may have exactly the right technical skills but already be assigned to another customer. Another person might have the necessary expertise and sufficient capacity during the required period.This helps organizations reduce overbooking and make project commitments based on actual resource availability.
RESOURCE BOOKINGS AND CAPACITY
A resource booking reserves part of someone's working capacity for project work.Employees do not necessarily need to be assigned full-time. A consultant might spend three days each week on one customer project while using the remaining capacity for another engagement, training, internal work, or leave.Connecting resource bookings with availability gives organizations a clearer picture of their delivery capacity.This is particularly valuable for consulting organizations and professional services firms where people represent both the primary delivery resource and a significant part of project cost.
SKILLS, ROLES AND PROJECT COSTS
Staffing is not simply about finding someone with an empty calendar.Projects often require specific roles and competencies such as project managers, business analysts, developers, architects, engineers, consultants, or security specialists.The financial impact also matters.A senior specialist may have a different internal cost than a junior consultant. The organization therefore needs to balance skills, availability, delivery quality, and financial performance when staffing projects.Dynamics 365 Project Operations connects these staffing decisions more closely with the overall project plan and financial picture.
PROJECT COSTS AND PROFITABILITY
A project can finish on time and still lose money.Customer revenue represents only one side of the financial equation. Organizations also need to consider employee costs, contractors, travel, software, materials, and other expenses required to deliver the engagement.Dynamics 365 Project Operations helps connect planned and actual project costs with customer pricing.This makes it easier to understand whether the project is consuming more expensive resources or more working hours than originally anticipated.A project can therefore appear successful operationally while becoming less profitable financially.Connecting project delivery and project financial information helps organizations identify this situation earlier.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.
🚀 Want to be part of m365.fm?
Then stop just listening… and start showing up.
👉 Connect with me on LinkedIn and let’s make something happen:
- 🎙️ Be a podcast guest and share your story
- 🎧 Host your own episode (yes, seriously)
- 💡 Pitch topics the community actually wants to hear
- 🌍 Build your personal brand in the Microsoft 365 space
This isn’t just a podcast — it’s a platform for people who take action.
🔥 Most people wait. The best ones don’t.
👉 Connect with me on LinkedIn and send me a message:
"I want in"
Let’s build something awesome 👊
Frequently Asked Questions
What is Microsoft Dynamics 365 Project Operations?
Microsoft Dynamics 365 Project Operations is a business application designed for project-based services that connects project sales, delivery, staffing, time, expenses, billing, and financials into one unified platform.
How does Dynamics 365 Project Operations help with resource management?
It allows resource managers to match project requirements with employee and contractor skills and availability, preventing overbooking and ensuring the right people are assigned to the right tasks.
What is the difference between a project quote and a project contract?
A quote represents the proposed work, estimated effort, and pricing that the company hopes to sell, while a contract records the final agreement and commercial commitments accepted by the customer.
Why is connecting project delivery and project financials important?
A project can finish on time yet still lose money if internal costs, employee hours, and expenses exceed the customer's agreed price; connecting these areas helps organizations identify profitability issues early.
00:00:00,000 --> 00:00:02,500
Imagine this. A customer signs a project with your company.
2
00:00:02,500 --> 00:00:04,260
Sales has the deal in one system.
3
00:00:04,260 --> 00:00:06,740
The project manager has the plan in a spreadsheet.
4
00:00:06,740 --> 00:00:08,680
People enter hours somewhere else.
5
00:00:08,680 --> 00:00:10,880
Finance is still asking what can be invoiced.
6
00:00:10,880 --> 00:00:13,840
Sound familiar? Dynamics 365 project operations
7
00:00:13,840 --> 00:00:15,080
connects those pieces.
8
00:00:15,080 --> 00:00:17,320
It gives project-based businesses a single place
9
00:00:17,320 --> 00:00:20,520
to sell, plan, staff, track time, and costs,
10
00:00:20,520 --> 00:00:22,080
and then build the customer.
11
00:00:22,080 --> 00:00:24,280
Welcome to another episode of Microsoft Knowledge Nuggets
12
00:00:24,280 --> 00:00:27,320
on M365 FMER, TMM, Mercopedas.
13
00:00:27,320 --> 00:00:28,680
Think of this as an office building.
14
00:00:28,680 --> 00:00:30,880
We would more follow one project from the first customer
15
00:00:30,880 --> 00:00:32,720
conversation to the final invoice.
16
00:00:32,720 --> 00:00:35,400
Grab your coffee and let's dive in.
17
00:00:35,400 --> 00:00:38,360
Why project businesses need it? 500 words.
18
00:00:38,360 --> 00:00:40,960
Imagine a consulting company wins a new customer project.
19
00:00:40,960 --> 00:00:42,800
This could be a design agency, a law firm,
20
00:00:42,800 --> 00:00:44,320
or a software development company.
21
00:00:44,320 --> 00:00:46,320
The salesperson promises a team of specialists
22
00:00:46,320 --> 00:00:47,320
for several weeks.
23
00:00:47,320 --> 00:00:49,000
A project manager needs a schedule.
24
00:00:49,000 --> 00:00:51,360
Team members need somewhere to enter hours.
25
00:00:51,360 --> 00:00:54,280
Finance needs to know which hours are billable,
26
00:00:54,280 --> 00:00:56,280
what expenses belong to the project,
27
00:00:56,280 --> 00:00:58,040
and when to send the invoice.
28
00:00:58,040 --> 00:00:59,840
Each person asks a valid question.
29
00:00:59,840 --> 00:01:01,000
Who is available next month?
30
00:01:01,000 --> 00:01:02,800
What exactly did the customer agree to buy?
31
00:01:02,800 --> 00:01:03,800
Are we still on budget?
32
00:01:03,800 --> 00:01:06,480
Has the customer already received an invoice for this work?
33
00:01:06,480 --> 00:01:08,720
Without a connected system, people chase those answers
34
00:01:08,720 --> 00:01:11,520
through email, spreadsheets, meetings, and separate apps.
35
00:01:11,520 --> 00:01:13,600
Sales keeps one version of the deal, delivery
36
00:01:13,600 --> 00:01:15,080
creates another version of the plan.
37
00:01:15,080 --> 00:01:17,720
Finance gets a list of approved hours at month end
38
00:01:17,720 --> 00:01:19,920
and tries to turn it into a correct invoice.
39
00:01:19,920 --> 00:01:21,160
That creates gaps.
40
00:01:21,160 --> 00:01:25,040
A salesperson promises a senior consultant who is already booked.
41
00:01:25,040 --> 00:01:26,720
A project manager plans 80 hours
42
00:01:26,720 --> 00:01:28,440
when the quote only allows 60.
43
00:01:28,440 --> 00:01:30,000
Someone forgets travel costs.
44
00:01:30,000 --> 00:01:31,360
The customer then receives an invoice
45
00:01:31,360 --> 00:01:33,000
that doesn't match what they expected.
46
00:01:33,000 --> 00:01:34,560
Nobody meant to cause confusion.
47
00:01:34,560 --> 00:01:36,440
The information just lives in too many places.
48
00:01:36,440 --> 00:01:38,120
These companies sell project work.
49
00:01:38,120 --> 00:01:39,440
They sell time and skills.
50
00:01:39,440 --> 00:01:42,560
Consulting, design, legal, software setup, engineering,
51
00:01:42,560 --> 00:01:44,720
they can charge a fixed amount for an agreed result
52
00:01:44,720 --> 00:01:46,680
or bill for each hour and expense.
53
00:01:46,680 --> 00:01:48,640
Either way, the business needs to connect the promise
54
00:01:48,640 --> 00:01:49,400
with the work.
55
00:01:49,400 --> 00:01:50,920
Project operations is how they do that.
56
00:01:50,920 --> 00:01:53,600
That's what Dynamics 365 project operations does.
57
00:01:53,600 --> 00:01:55,240
In plain English, it's a Microsoft app
58
00:01:55,240 --> 00:01:57,600
for running the business side of customer projects.
59
00:01:57,600 --> 00:01:59,960
It connects project sales, delivery, staffing, time,
60
00:01:59,960 --> 00:02:01,840
expenses, billing and financials.
61
00:02:01,840 --> 00:02:03,360
Here's what I want you to remember.
62
00:02:03,360 --> 00:02:05,560
Project operations is not just another app.
63
00:02:05,560 --> 00:02:08,280
It's the central nervous system for project-based businesses.
64
00:02:08,280 --> 00:02:10,440
Every team gets the same information at the same time.
65
00:02:10,440 --> 00:02:12,040
This building has different floors
66
00:02:12,040 --> 00:02:14,240
and each department works on a different level.
67
00:02:14,240 --> 00:02:15,840
Sales works on the ground floor.
68
00:02:15,840 --> 00:02:17,640
That's where the customer relationship starts.
69
00:02:17,640 --> 00:02:19,200
Project management is on the second floor
70
00:02:19,200 --> 00:02:20,720
turning promises into plans.
71
00:02:20,720 --> 00:02:23,000
Finance is on the top floor, keeping track of costs
72
00:02:23,000 --> 00:02:23,880
and invoices.
73
00:02:23,880 --> 00:02:25,120
They all share the same foundation.
74
00:02:25,120 --> 00:02:27,120
The project data, project operations
75
00:02:27,120 --> 00:02:28,720
is that shared foundation.
76
00:02:28,720 --> 00:02:31,600
It connects everyone through one central record.
77
00:02:31,600 --> 00:02:33,560
Think of it as the elevator between floors.
78
00:02:33,560 --> 00:02:35,360
Every department uses the same elevator
79
00:02:35,360 --> 00:02:37,520
so nothing gets lost along the way.
80
00:02:37,520 --> 00:02:40,200
Notice I didn't call project operations a task app.
81
00:02:40,200 --> 00:02:42,200
You can plan tasks in many tools.
82
00:02:42,200 --> 00:02:45,480
A small team might use a checklist, planner or a shared document
83
00:02:45,480 --> 00:02:47,400
and that works fine for internal work.
84
00:02:47,400 --> 00:02:50,400
Project operations comes in when the project touches customers,
85
00:02:50,400 --> 00:02:54,040
staff schedules, costs, contracts and invoices at the same time.
86
00:02:54,040 --> 00:02:57,000
Think about a company that helps customers move systems to the cloud.
87
00:02:57,000 --> 00:03:00,240
Before work begins, it needs to estimate effort and price.
88
00:03:00,240 --> 00:03:02,120
During work, it needs the right technical people
89
00:03:02,120 --> 00:03:03,320
at the right time.
90
00:03:03,320 --> 00:03:04,520
As the project moves forward,
91
00:03:04,520 --> 00:03:08,240
it needs a clear record of hours, costs, progress and customer billing.
92
00:03:08,240 --> 00:03:09,720
One project touches many teams.
93
00:03:09,720 --> 00:03:11,560
Project operations gives them a shared record
94
00:03:11,560 --> 00:03:14,720
instead of asking them to rebuild the same information repeatedly.
95
00:03:14,720 --> 00:03:15,840
Sales sees the deal.
96
00:03:15,840 --> 00:03:18,480
Delivery sees the agreed work, resource managers check
97
00:03:18,480 --> 00:03:21,080
who has the right skills and availability.
98
00:03:21,080 --> 00:03:23,160
Finance works from approved project activity
99
00:03:23,160 --> 00:03:25,400
rather than chasing people for missing details.
100
00:03:25,400 --> 00:03:28,400
The point isn't that every person uses the same screen all day.
101
00:03:28,400 --> 00:03:30,640
Sales people work differently from project managers
102
00:03:30,640 --> 00:03:32,360
and finance teams work differently.
103
00:03:32,360 --> 00:03:35,520
What connects them is the project information behind the scenes.
104
00:03:35,520 --> 00:03:36,640
When details change,
105
00:03:36,640 --> 00:03:38,040
everyone works from the same picture
106
00:03:38,040 --> 00:03:40,440
instead of discovering a surprise after the work is done.
107
00:03:40,440 --> 00:03:41,800
This prevents a common problem.
108
00:03:41,800 --> 00:03:44,080
A project looks busy and successful from the outside
109
00:03:44,080 --> 00:03:46,560
while the company quietly loses money out.
110
00:03:46,560 --> 00:03:49,280
Using more time, more expensive staff or more travel
111
00:03:49,280 --> 00:03:50,960
than the customer price allowed.
112
00:03:50,960 --> 00:03:53,360
Project operations puts the plan, the people and the money
113
00:03:53,360 --> 00:03:54,640
in the same conversation.
114
00:03:54,640 --> 00:03:55,760
So let's enter the building
115
00:03:55,760 --> 00:03:57,880
where every customer project really begins
116
00:03:57,880 --> 00:03:59,600
before a project manager opens a plan
117
00:03:59,600 --> 00:04:01,480
or a consultant logs a single hour.
118
00:04:01,480 --> 00:04:06,880
The front door, sales, quotes and project contracts.
119
00:04:06,880 --> 00:04:11,720
A customer project starts long before the delivery team sees a single task.
120
00:04:11,720 --> 00:04:14,080
It begins when someone asks, can you help us?
121
00:04:14,080 --> 00:04:15,960
Maybe they need a new finance system.
122
00:04:15,960 --> 00:04:18,960
Cloud advice, training, design work.
123
00:04:18,960 --> 00:04:20,640
Or a team to build something specific.
124
00:04:20,640 --> 00:04:23,280
Sales has to turn that conversation into a clear offer,
125
00:04:23,280 --> 00:04:24,720
but here's the thing.
126
00:04:24,720 --> 00:04:27,600
Our estimating the work before the work exists takes real thought.
127
00:04:27,600 --> 00:04:29,760
Someone needs to figure out the roles required,
128
00:04:29,760 --> 00:04:32,160
the hours involved, what the customer will be charged,
129
00:04:32,160 --> 00:04:34,760
internal costs, planned dates,
130
00:04:34,760 --> 00:04:37,720
and the points where the customer expects to see a result.
131
00:04:37,720 --> 00:04:39,360
Those points are called milestones.
132
00:04:39,360 --> 00:04:41,600
A milestone might mark the end of a discovery phase,
133
00:04:41,600 --> 00:04:43,120
the delivery of a design,
134
00:04:43,120 --> 00:04:45,600
or when the customer approves a finished piece of work.
135
00:04:45,600 --> 00:04:48,680
It gives both sides a clean moment to pause, check progress,
136
00:04:48,680 --> 00:04:51,040
approve the next step, or trigger a payment.
137
00:04:51,040 --> 00:04:53,560
Project operations help sales capture those details
138
00:04:53,560 --> 00:04:55,360
while the deal is still taking shape.
139
00:04:55,360 --> 00:04:59,200
That way, the customer conversation doesn't live only in email threads,
140
00:04:59,200 --> 00:05:01,320
meeting notes, or someone's memory alone.
141
00:05:01,320 --> 00:05:04,680
Imagine a customer wants help moving part of its business to the cloud.
142
00:05:04,680 --> 00:05:06,920
The salesperson estimates a 10 week project.
143
00:05:06,920 --> 00:05:09,760
It needs one project manager, two technical consultants,
144
00:05:09,760 --> 00:05:12,440
and a specialist for a short security review near the end.
145
00:05:12,440 --> 00:05:14,720
The customer agrees to a set number of hours,
146
00:05:14,720 --> 00:05:16,920
a price for the work, and a billing plan.
147
00:05:16,920 --> 00:05:19,520
That information becomes more than just a sales note.
148
00:05:19,520 --> 00:05:21,600
A quote puts the proposed work into writing
149
00:05:21,600 --> 00:05:23,160
or the work the company plans to do.
150
00:05:23,160 --> 00:05:25,960
The estimated effort, the price, the plans start and end dates,
151
00:05:25,960 --> 00:05:28,080
and the rules for charging the customer.
152
00:05:28,080 --> 00:05:31,000
When the customer accepts a project contract records the agreement,
153
00:05:31,000 --> 00:05:33,560
think of the contract as a written boundary around the project.
154
00:05:33,560 --> 00:05:35,800
It answers basic questions that become very awkward
155
00:05:35,800 --> 00:05:37,480
when nobody can answer them later.
156
00:05:37,480 --> 00:05:38,560
What did the customer buy?
157
00:05:38,560 --> 00:05:39,880
How much will they pay?
158
00:05:39,880 --> 00:05:42,240
Are they paying for hours worked, a fixed amount,
159
00:05:42,240 --> 00:05:45,400
or work completed at certain stages can travel costs be charged back?
160
00:05:45,400 --> 00:05:48,600
Clear answers prevent a lot of hard conversations later.
161
00:05:48,600 --> 00:05:49,720
Here's a simple distinction.
162
00:05:49,720 --> 00:05:51,840
A quote says what the company hopes to sell,
163
00:05:51,840 --> 00:05:54,360
a contract records what the customer agreed to buy.
164
00:05:54,360 --> 00:05:57,000
That difference matters because delivery teams need to work
165
00:05:57,000 --> 00:05:59,520
from the accepted promise, not from an early idea
166
00:05:59,520 --> 00:06:01,920
that changed during negotiation.
167
00:06:01,920 --> 00:06:04,680
Project operations keeps those details close to the project record.
168
00:06:04,680 --> 00:06:06,720
Instead of a project manager receiving a forwarded email
169
00:06:06,720 --> 00:06:09,360
that says, "I think we sold 10 weeks of consulting."
170
00:06:09,360 --> 00:06:11,120
The manager can see the approved scope,
171
00:06:11,120 --> 00:06:13,440
planned roles, estimated hours, pricing,
172
00:06:13,440 --> 00:06:16,120
and billing terms all connected to the customer project.
173
00:06:16,120 --> 00:06:18,520
That gives delivery a much firmer starting point.
174
00:06:18,520 --> 00:06:21,520
It also helps sales stay realistic before the customer signs.
175
00:06:21,520 --> 00:06:24,400
If a quote needs a senior expert for three full weeks,
176
00:06:24,400 --> 00:06:27,880
the business can check whether that person can support the planned dates.
177
00:06:27,880 --> 00:06:29,720
A customer may want work to start Monday,
178
00:06:29,720 --> 00:06:32,440
but a promised specialist might already be committed elsewhere,
179
00:06:32,440 --> 00:06:35,680
better to spot that during the quote than after the contract is signed.
180
00:06:35,680 --> 00:06:38,680
For businesses already using Dynamics 365 sales,
181
00:06:38,680 --> 00:06:41,080
project operations can connect with the customer records
182
00:06:41,080 --> 00:06:43,240
and sales activity that already live there.
183
00:06:43,240 --> 00:06:45,080
Sales doesn't need to treat a project deal
184
00:06:45,080 --> 00:06:47,400
as a completely separate kind of conversation.
185
00:06:47,400 --> 00:06:49,440
The customer, the opportunity, the estimate,
186
00:06:49,440 --> 00:06:51,920
and the contract can all follow the same path.
187
00:06:51,920 --> 00:06:54,560
Now that doesn't mean every sales deal becomes a project.
188
00:06:54,560 --> 00:06:57,600
A simple product sale may not need project planning at all.
189
00:06:57,600 --> 00:06:59,120
Project operations comes into play
190
00:06:59,120 --> 00:07:01,120
when the deal creates planned customer work
191
00:07:01,120 --> 00:07:04,240
that needs people, time, costs, and billing rules behind it.
192
00:07:04,240 --> 00:07:07,640
Once the customer signs, the promise needs to become a real plan.
193
00:07:08,640 --> 00:07:13,040
The project room, plans, tasks, and day-to-day delivery.
194
00:07:13,040 --> 00:07:15,240
With the agreement in place,
195
00:07:15,240 --> 00:07:17,440
the project manager needs to turn that promise into work
196
00:07:17,440 --> 00:07:18,640
that people can actually follow.
197
00:07:18,640 --> 00:07:19,640
This is the project room.
198
00:07:19,640 --> 00:07:23,240
Project operations uses a Microsoft project workspace for the schedule.
199
00:07:23,240 --> 00:07:25,840
That's where the team maps out the work, sees dates,
200
00:07:25,840 --> 00:07:28,240
and tracks progress as the project moves forward.
201
00:07:28,240 --> 00:07:30,040
A project plan can feel overwhelming
202
00:07:30,040 --> 00:07:32,840
when it only says, move the customer to the cloud.
203
00:07:32,840 --> 00:07:35,040
So the manager breaks it into smaller pieces.
204
00:07:35,040 --> 00:07:37,440
That structure is called a work breakdown structure.
205
00:07:37,440 --> 00:07:38,640
Or WBS.
206
00:07:38,640 --> 00:07:41,640
The name sounds technical, but it simply means taking a large piece of work
207
00:07:41,640 --> 00:07:45,640
and splitting it into tasks that a person can understand, own, and complete.
208
00:07:45,640 --> 00:07:48,840
For our cloud migration project, the first task might be discovery.
209
00:07:48,840 --> 00:07:51,440
The team needs to learn what systems the customer uses,
210
00:07:51,440 --> 00:07:53,840
what data they hold, who depends on them,
211
00:07:53,840 --> 00:07:55,640
and what could go wrong during the move.
212
00:07:55,640 --> 00:07:57,640
Design comes next.
213
00:07:57,640 --> 00:08:00,640
You can't build a good solution until you know what you need to build.
214
00:08:00,640 --> 00:08:04,240
After design comes the build work, then testing, then the customer review.
215
00:08:04,240 --> 00:08:07,840
Finally, the team moves the work into use and closes the project.
216
00:08:07,840 --> 00:08:10,240
Each task can carry details like a planned start date,
217
00:08:10,240 --> 00:08:13,040
finished date, expected effort, the person responsible,
218
00:08:13,040 --> 00:08:14,840
and its place in the wider schedule.
219
00:08:14,840 --> 00:08:16,840
Some tasks also depend on others.
220
00:08:16,840 --> 00:08:20,440
Design can't properly begin until discovery gives the team enough information.
221
00:08:20,440 --> 00:08:23,640
Customer review can't happen until the build work reaches a point
222
00:08:23,640 --> 00:08:25,840
the customer can review those links matter
223
00:08:25,840 --> 00:08:28,840
because the delay near the beginning can affect work later in the project.
224
00:08:28,840 --> 00:08:32,440
When a task moves, the plan can show where pressure may appear next.
225
00:08:32,440 --> 00:08:34,440
It doesn't predict the future perfectly.
226
00:08:34,440 --> 00:08:38,640
Projects involve people, customers, changing needs, and the occasional surprise.
227
00:08:38,640 --> 00:08:42,240
But a connected schedule helps the project manager see the effect of a change
228
00:08:42,240 --> 00:08:46,040
instead of finding out too late that three later tasks quietly slipped as well.
229
00:08:46,040 --> 00:08:48,040
Milestones also appear in the plan.
230
00:08:48,040 --> 00:08:50,440
Think of them as checkpoints with no work hours of their own.
231
00:08:50,440 --> 00:08:53,040
A milestone might show that the design received approval,
232
00:08:53,040 --> 00:08:56,040
the first test completed, or the customer accepted a delivery.
233
00:08:56,040 --> 00:08:59,040
They give the project team and the customer clear moments to stop,
234
00:08:59,040 --> 00:09:01,040
check the work, and decide what comes next.
235
00:09:01,040 --> 00:09:03,840
The plan isn't meant to sit untouched after the first meeting.
236
00:09:03,840 --> 00:09:06,040
A project manager updates it as work happens.
237
00:09:06,040 --> 00:09:10,640
Team members complete tasks, dates change, a customer may ask for a different approach.
238
00:09:10,640 --> 00:09:12,640
Someone may need more time than expected.
239
00:09:12,640 --> 00:09:15,640
Project operations gives the manager a place to compare the original plan
240
00:09:15,640 --> 00:09:17,240
with the work completed so far.
241
00:09:17,240 --> 00:09:19,240
That comparison answers a simple question,
242
00:09:19,240 --> 00:09:21,040
are we where we expect it to be?
243
00:09:21,040 --> 00:09:25,440
If the team planned 40 hours for discovery but record 60 hours before discovery finishes,
244
00:09:25,440 --> 00:09:28,640
the manager can see that the project has used more effort than planned.
245
00:09:28,640 --> 00:09:31,240
That doesn't automatically mean the project failed out.
246
00:09:31,240 --> 00:09:35,240
Maybe the customer environment turned out to be more complicated than anyone knew.
247
00:09:35,240 --> 00:09:37,440
Either way, the team now has a fact to discuss.
248
00:09:37,440 --> 00:09:39,240
Day to day work also needs a record.
249
00:09:39,240 --> 00:09:42,040
A consultant can enter time against the task they worked on,
250
00:09:42,040 --> 00:09:43,840
rather than write project work.
251
00:09:43,840 --> 00:09:45,640
As a vague line at the end of the week,
252
00:09:45,640 --> 00:09:48,040
the entry shows what they worked on and how long it took,
253
00:09:48,040 --> 00:09:51,640
giving the project manager a clearer view of effort used across the plan.
254
00:09:51,640 --> 00:09:54,040
Time records do more than fill out a time sheet.
255
00:09:54,040 --> 00:09:55,640
They connect actual work to the plan.
256
00:09:55,640 --> 00:09:57,040
They help the manager see progress.
257
00:09:57,040 --> 00:10:01,240
They create information that the business can later use for project costs and customer billing,
258
00:10:01,240 --> 00:10:02,840
depending on the contract terms.
259
00:10:02,840 --> 00:10:04,840
Expenses belong in the project record too.
260
00:10:04,840 --> 00:10:08,840
A consultant might travel to a customer site, pay for an approved service,
261
00:10:08,840 --> 00:10:10,840
or buy something needed for the work.
262
00:10:10,840 --> 00:10:13,640
Project operations can connect those costs to the project
263
00:10:13,640 --> 00:10:17,840
so they don't disappear into a separate paper trail with no clear link to the customer work.
264
00:10:17,840 --> 00:10:22,440
Some organizations also see co-pilot help in project operations, where available.
265
00:10:22,440 --> 00:10:25,840
Co-pilot can assist with tasks like drafting a project status report,
266
00:10:25,840 --> 00:10:29,640
surfacing possible risks from project information or helping with time entry.
267
00:10:29,640 --> 00:10:31,440
It reduces some of the blank page work,
268
00:10:31,440 --> 00:10:34,440
but it doesn't replace a project manager who understands the customer,
269
00:10:34,440 --> 00:10:36,440
the team, and the reasons behind the delay.
270
00:10:36,440 --> 00:10:38,240
The person still checks the result.
271
00:10:38,240 --> 00:10:41,240
Project operations suits customer projects with plans, contracts,
272
00:10:41,240 --> 00:10:42,840
people, hours, and money attached.
273
00:10:42,840 --> 00:10:45,640
If your team only needs a simple board for internal tasks,
274
00:10:45,640 --> 00:10:47,240
planter may be the better fitter,
275
00:10:47,240 --> 00:10:48,840
it keeps the work light and focused.
276
00:10:48,840 --> 00:10:52,840
A schedule only becomes real when the right people have time to do it.
277
00:10:52,840 --> 00:10:56,040
The staffing desk, skills availability time and expenses.
278
00:10:56,040 --> 00:11:00,240
Hello everyone, and welcome back to another knowledge nugget here on M365, FM.
279
00:11:00,240 --> 00:11:01,840
I'm your host, Mirko Peters,
280
00:11:01,840 --> 00:11:05,040
and today we're talking about what happens when a plan meets the real world.
281
00:11:05,040 --> 00:11:06,640
A plan can look perfect on screen,
282
00:11:06,640 --> 00:11:09,640
but it falls apart if the people named in it aren't free.
283
00:11:09,640 --> 00:11:14,040
Here's the thing, think of resource management as the staffing desk in our office building.
284
00:11:14,040 --> 00:11:16,240
It's where the business checks who can do the work,
285
00:11:16,240 --> 00:11:18,240
when they can do it, what skills they bring,
286
00:11:18,240 --> 00:11:19,840
and what their time costs the project.
287
00:11:19,840 --> 00:11:22,040
A resource can be an employee or a contractor.
288
00:11:22,040 --> 00:11:25,840
It can also mean a role like project manager, business analyst, developer,
289
00:11:25,840 --> 00:11:28,240
or security specialist, and that matters early
290
00:11:28,240 --> 00:11:31,840
because a project manager may know they need a security expert for two weeks
291
00:11:31,840 --> 00:11:34,040
without knowing which person will fill that role.
292
00:11:34,040 --> 00:11:37,040
Skills matter, but availability matters just as much.
293
00:11:37,040 --> 00:11:41,040
Imagine your cloud project needs someone who understands security reviews during week eight.
294
00:11:41,040 --> 00:11:43,640
Your staffing team may find three people with that skill,
295
00:11:43,640 --> 00:11:46,240
but one is on leave, one is assigned to another customer,
296
00:11:46,240 --> 00:11:48,040
and one has time available.
297
00:11:49,040 --> 00:11:53,040
The project operations helps your team find the person who fits both parts of the need.
298
00:11:53,040 --> 00:11:54,240
The skill alone isn't enough.
299
00:11:54,240 --> 00:11:59,440
Without that visibility, a company can accidentally promise the same person to two full-time projects in the same week.
300
00:11:59,440 --> 00:12:01,440
On paper, both projects look staffed.
301
00:12:01,440 --> 00:12:04,240
In real life, that person has two calendars, two sets of deadlines,
302
00:12:04,240 --> 00:12:06,040
and no way to work twice as many hours.
303
00:12:06,040 --> 00:12:07,640
That problem starts before delivery.
304
00:12:07,640 --> 00:12:09,840
Resource managers can book people against project work
305
00:12:09,840 --> 00:12:12,640
and compare those planned bookings with their real availability.
306
00:12:12,640 --> 00:12:16,840
A booking means the business has set aside part of a person's working time for a project.
307
00:12:16,840 --> 00:12:18,840
It turns a hopeful plan into a clearer commitment.
308
00:12:18,840 --> 00:12:22,640
Maybe the project needs a consultant for three days each week, rather than full-time.
309
00:12:22,640 --> 00:12:25,240
That can be planned too, and the business can see what time remains
310
00:12:25,240 --> 00:12:28,640
for other customer work, internal tasks, training, or leave.
311
00:12:28,640 --> 00:12:31,440
It gives you a better chance of spotting clashes before a customer asks
312
00:12:31,440 --> 00:12:32,840
why nobody joined the meeting.
313
00:12:32,840 --> 00:12:34,840
Cost belongs in this conversation as well.
314
00:12:34,840 --> 00:12:37,240
A senior consultant may have deep experience,
315
00:12:37,240 --> 00:12:40,440
but their internal cost may differ from a junior consultant's cost.
316
00:12:40,440 --> 00:12:43,040
The project team needs the right person for the work,
317
00:12:43,040 --> 00:12:47,240
while the business also needs to understand what that staffing choice does to the project budget.
318
00:12:47,240 --> 00:12:48,840
People aren't just names on a schedule.
319
00:12:48,840 --> 00:12:50,840
Their time becomes real project activity
320
00:12:50,840 --> 00:12:53,040
when they enter hours against the work they completed,
321
00:12:53,040 --> 00:12:56,040
and those entries show whether planned effort matches actual effort
322
00:12:56,040 --> 00:12:59,240
while supporting customer billing when the contract charges for time worked.
323
00:12:59,240 --> 00:13:00,840
Now, what about a late time sheet?
324
00:13:00,840 --> 00:13:04,440
A late or unclear time sheet creates trouble for more than the person who needs to approve it.
325
00:13:04,440 --> 00:13:06,640
The project manager loses sight of work used,
326
00:13:06,640 --> 00:13:08,840
finance may lack the details needed for an invoice,
327
00:13:08,840 --> 00:13:11,440
and the customer may receive a bill later than expected.
328
00:13:11,440 --> 00:13:14,240
One small missing record can travel through the whole project.
329
00:13:14,240 --> 00:13:15,640
Expenses follow a similar path.
330
00:13:15,640 --> 00:13:17,440
If someone travels to the customer side,
331
00:13:17,440 --> 00:13:19,440
or pays for an approved project cost,
332
00:13:19,440 --> 00:13:21,840
they can submit that expense against the project.
333
00:13:21,840 --> 00:13:25,040
The company can review and approve it in the same connected area,
334
00:13:25,040 --> 00:13:29,040
rather than hunt through email attachments and receipts with no clear project link.
335
00:13:29,040 --> 00:13:31,840
Microsoft is also introducing agents for some of this admin work.
336
00:13:31,840 --> 00:13:34,840
The time entry agent can help prepare time entry drafts and reminders.
337
00:13:34,840 --> 00:13:37,240
The expense agent can help with expense reporting.
338
00:13:37,240 --> 00:13:41,640
The activity approvals agent can help people focus on approvals that need attention.
339
00:13:41,640 --> 00:13:43,640
These are listed as preview capabilities,
340
00:13:43,640 --> 00:13:47,840
so don't assume every project operations customer already has them in daily use.
341
00:13:47,840 --> 00:13:50,240
The person remains responsible for checking the details.
342
00:13:50,240 --> 00:13:52,440
Once the right people record their work and costs,
343
00:13:52,440 --> 00:13:57,040
the project reaches the part of the building where delivery meets the money.
344
00:13:57,040 --> 00:13:58,240
The finance office.
345
00:13:58,240 --> 00:14:01,640
Costs, billing, revenue, and global work.
346
00:14:01,640 --> 00:14:04,440
A customer project can finish on time and still lose money.
347
00:14:04,440 --> 00:14:05,640
That sounds audit first,
348
00:14:05,640 --> 00:14:08,440
but look at what sits behind a customer price.
349
00:14:08,440 --> 00:14:10,440
The company pays the people doing the work,
350
00:14:10,440 --> 00:14:14,240
plus contractors, travel costs, software charges, or materials,
351
00:14:14,240 --> 00:14:18,040
and then it needs to compare those costs with what the customer agreed to pay.
352
00:14:18,040 --> 00:14:19,640
That is where project financials come in.
353
00:14:19,640 --> 00:14:22,840
Project operations helps the business track the money connected to a project
354
00:14:22,840 --> 00:14:26,040
from the estimate through the work completed and into customer billing.
355
00:14:26,040 --> 00:14:30,040
It gives finance and project teams a clearer way to answer one question.
356
00:14:30,040 --> 00:14:32,440
After paying for the work, did this project earn enough?
357
00:14:32,440 --> 00:14:35,240
The customer price and the internal cost aren't the same number.
358
00:14:35,240 --> 00:14:38,840
Imagine a consultant builds the customer at one hourly rate
359
00:14:38,840 --> 00:14:42,040
while the company has its own cost for that consultant's time
360
00:14:42,040 --> 00:14:43,840
based on pay and other business costs.
361
00:14:43,840 --> 00:14:47,640
If the project needs far more of that consultant's time than planned,
362
00:14:47,640 --> 00:14:49,640
the customer invoice may still look correct
363
00:14:49,640 --> 00:14:51,840
while the project earns less than expected.
364
00:14:51,840 --> 00:14:54,440
That is why planned costs matter before work starts,
365
00:14:54,440 --> 00:14:57,040
and actual costs matter while work continues.
366
00:14:57,040 --> 00:14:59,840
Project operations can track pricing and costing by role,
367
00:14:59,840 --> 00:15:03,040
so a business can see the financial side of staffing choices.
368
00:15:03,040 --> 00:15:06,440
A senior consultant may solve a problem faster but also cost more.
369
00:15:06,440 --> 00:15:08,240
And sometimes that is the right choice.
370
00:15:08,240 --> 00:15:11,640
The point is that the project manager and finance team can see the effect
371
00:15:11,640 --> 00:15:14,040
instead of guessing after the project closes.
372
00:15:14,040 --> 00:15:15,840
Customers also pay in different ways.
373
00:15:15,840 --> 00:15:19,240
With time and materials billing, the customer pays for their hours worked
374
00:15:19,240 --> 00:15:22,040
and approved expenses, so if the team works more hours,
375
00:15:22,040 --> 00:15:24,240
the bill can increase under the agreed rules.
376
00:15:24,240 --> 00:15:25,640
With a fixed price project,
377
00:15:25,640 --> 00:15:28,440
the customer agrees to pay a set amount for a defined piece of work
378
00:15:28,440 --> 00:15:31,640
and the invoice doesn't rise simply because the team spent more time than planned.
379
00:15:31,640 --> 00:15:35,040
That puts more pressure on the company to control its own costs.
380
00:15:35,040 --> 00:15:37,440
Milestone billing follows agreed checkpoints.
381
00:15:37,440 --> 00:15:41,440
For example, a customer may pay part of the project price after approving the design,
382
00:15:41,440 --> 00:15:43,040
another part after testing,
383
00:15:43,040 --> 00:15:45,240
and the remaining amount when the work goes live
384
00:15:45,240 --> 00:15:49,240
with the billing schedule following work that both sides agreed to recognize.
385
00:15:49,240 --> 00:15:51,240
These rules belong in the project contract,
386
00:15:51,240 --> 00:15:52,840
then guide the invoice process.
387
00:15:52,840 --> 00:15:56,440
Approved time entries, approved expenses, contract terms, and billing rules
388
00:15:56,440 --> 00:15:58,640
give finance the information it needs to prepare
389
00:15:58,640 --> 00:16:00,840
what is often called a pro-former invoice.
390
00:16:00,840 --> 00:16:05,040
Think of that as a draft customer bill for review before it becomes the final invoice.
391
00:16:05,040 --> 00:16:06,240
That review matters.
392
00:16:06,240 --> 00:16:09,240
A finance team can check whether the charges match the agreement,
393
00:16:09,240 --> 00:16:11,440
whether the right time and expenses appear,
394
00:16:11,440 --> 00:16:14,440
and whether anything needs correcting before the customer sees it.
395
00:16:14,440 --> 00:16:16,840
A clean invoice protects the customer relationship
396
00:16:16,840 --> 00:16:20,240
and means the company doesn't need to spend the next month untangling a bill
397
00:16:20,240 --> 00:16:22,040
that should never have gone out.
398
00:16:22,040 --> 00:16:24,040
Project accounting takes the view further.
399
00:16:24,040 --> 00:16:26,640
It tracks what the project costs, what the customer owes,
400
00:16:26,640 --> 00:16:29,640
and when the company should record revenue in its financial books.
401
00:16:29,640 --> 00:16:33,040
Billing a customer and recording revenue aren't always the same event
402
00:16:33,040 --> 00:16:36,240
because the right timing depends on the contract, the work completed,
403
00:16:36,240 --> 00:16:38,640
and the accounting rules the company follows.
404
00:16:38,640 --> 00:16:41,640
That is a finance decision, not a project manager's guess.
405
00:16:41,640 --> 00:16:43,640
For companies working across countries,
406
00:16:43,640 --> 00:16:45,840
the money picture can become more involved.
407
00:16:45,840 --> 00:16:48,640
A customer may receive an invoice in one currency
408
00:16:48,640 --> 00:16:50,640
while the project team works somewhere else.
409
00:16:50,640 --> 00:16:55,640
Tax rules can differ, and financial reports may need to follow local requirements.
410
00:16:55,640 --> 00:16:58,640
Project operations supports areas such as multi-currency billing,
411
00:16:58,640 --> 00:17:02,040
tax handling, and localized financial reporting for global project work.
412
00:17:02,040 --> 00:17:05,440
Companies still need their finance people and advisors to set up the right rules,
413
00:17:05,440 --> 00:17:09,840
but the project data can feed the same financial process instead of being rebuilt by hand.
414
00:17:09,840 --> 00:17:15,040
Some organizations need deeper finance processes than project operations handles on its own.
415
00:17:15,040 --> 00:17:18,640
That is where Dynamics 365 Finance can connect with project operations.
416
00:17:18,640 --> 00:17:21,440
Finance teams can use it for broader financial work,
417
00:17:21,440 --> 00:17:25,040
while project operations keeps the customer project details close to sales,
418
00:17:25,040 --> 00:17:27,040
delivery, staffing, and billing.
419
00:17:27,040 --> 00:17:30,440
Before choosing the software, a company needs an honest look at its own work.
420
00:17:30,440 --> 00:17:34,040
Project operations can require careful setup, especially when contracts,
421
00:17:34,040 --> 00:17:38,240
billing rules, currencies, and finance processes differ across the business.
422
00:17:38,240 --> 00:17:42,040
Large schedules with many tasks also need testing with real project data,
423
00:17:42,040 --> 00:17:43,440
not just a tidy demo plan.
424
00:17:43,440 --> 00:17:47,040
Microsoft provides different setup paths for different kinds of project work.
425
00:17:47,040 --> 00:17:49,040
One path suits lighter service delivery,
426
00:17:49,040 --> 00:17:51,440
where a company sells people's time and project work,
427
00:17:51,440 --> 00:17:53,840
another connects more deeply with financial processes,
428
00:17:53,840 --> 00:17:57,840
and a further path supports projects involving stock materials or production work.
429
00:17:57,840 --> 00:18:01,040
Those paths don't simply switch on the same features in a different menu,
430
00:18:01,040 --> 00:18:04,040
they affect where people work and which functions they use.
431
00:18:04,040 --> 00:18:08,440
A company should choose based on how it sells, delivers, bills, and accounts for its projects,
432
00:18:08,440 --> 00:18:11,640
rather than choose the option with the most impressive name.
433
00:18:11,640 --> 00:18:15,440
When those choices fit the business, the full flow becomes easier to see.
434
00:18:15,440 --> 00:18:18,640
Every part of the project can pass the right information to the next part.
435
00:18:18,640 --> 00:18:22,640
Thanks for joining me on this knowledge nugget, and I'll see you in the next episode.
436
00:18:22,640 --> 00:18:25,440
How the connected platform works together.
437
00:18:25,440 --> 00:18:27,640
Imagine a cloud migration project.
438
00:18:27,640 --> 00:18:30,040
From that first customer question to the final review,
439
00:18:30,040 --> 00:18:32,840
information flows between teams without anyone retyping it,
440
00:18:32,840 --> 00:18:35,840
sales records the opportunity and builds a quote.
441
00:18:35,840 --> 00:18:39,240
Once approved, the project manager turns that agreed work into a plan,
442
00:18:39,240 --> 00:18:43,040
staff book the right people, specialist log their time and expenses.
443
00:18:43,040 --> 00:18:45,440
Finance prepares the bill from the project activity.
444
00:18:45,440 --> 00:18:50,040
The key is that each piece of data moves forward or not re-entered in every department.
445
00:18:50,040 --> 00:18:52,040
Different teams stick with their own tools.
446
00:18:52,040 --> 00:18:54,040
Teams handles conversations and meetings.
447
00:18:54,040 --> 00:18:56,440
Project operations keeps the project business record,
448
00:18:56,440 --> 00:18:59,040
SharePoint stores control documents with version history.
449
00:18:59,040 --> 00:19:03,440
Power BI turns project data into reports on staffing, budgets, billing, and project health.
450
00:19:03,440 --> 00:19:07,040
Customer voice collects feedback at milestones or afterwork finishes.
451
00:19:07,040 --> 00:19:10,040
Project operations doesn't replace every app with one screen.
452
00:19:10,040 --> 00:19:12,440
Each team still uses what fits their job.
453
00:19:12,440 --> 00:19:14,640
The connection comes from shared project information.
454
00:19:14,640 --> 00:19:19,240
Some businesses still move data between Dynamics 365 sales and Dynamics 365 finance.
455
00:19:19,240 --> 00:19:21,840
Before you set this up, map your project types,
456
00:19:21,840 --> 00:19:26,840
billing rules, staffing process, finance needs, reports, and existing systems.
457
00:19:26,840 --> 00:19:29,840
Who it fits and what to remember.
458
00:19:29,840 --> 00:19:32,840
Project operations fits service firms that sell customer work,
459
00:19:32,840 --> 00:19:35,840
assign people, track effort, and invoice for delivery.
460
00:19:35,840 --> 00:19:38,040
If you're just managing a small internal task list,
461
00:19:38,040 --> 00:19:41,240
you probably don't need contracts, project costs, and billing rules.
462
00:19:41,240 --> 00:19:44,840
This is connected project business management, oh, not just a gant chart.
463
00:19:44,840 --> 00:19:48,240
If promises, people, hours, and invoices keep falling out of sync,
464
00:19:48,240 --> 00:19:51,040
this is the gap it aims to close by certain conclusion.
465
00:19:51,040 --> 00:19:52,240
Continue the learning.
466
00:19:52,240 --> 00:19:53,240
So there you have it.
467
00:19:53,240 --> 00:19:56,240
Project operations ties the customer promise to the actual work,
468
00:19:56,240 --> 00:19:58,440
people, costs, and invoices behind it.
469
00:19:58,440 --> 00:20:01,240
Subscribe to Microsoft Knowledge Nuggets on M365,
470
00:20:01,240 --> 00:20:06,240
FM, then continue with the next episode on the Dynamics 365 building block your team uses every day.
