June 17, 2026

From Project Online to AI-Powered Project Delivery: The Evolution of Dynamics 365 Project Operations with Joe Griffin [MVP]

From Project Online to AI-Powered Project Delivery: The Evolution of Dynamics 365 Project Operations with Joe Griffin [MVP]
From Project Online to AI-Powered Project Delivery: The Evolution of Dynamics 365 Project Operations with Joe Griffin [MVP]
M365 FM Podcast
From Project Online to AI-Powered Project Delivery: The Evolution of Dynamics 365 Project Operations with Joe Griffin [MVP]
Apple Podcasts podcast player iconSpotify podcast player iconYoutube Music podcast player iconSpreaker podcast player iconPodchaser podcast player iconAmazon Music podcast player icon

In this insightful episode of the M365 Podcast, host Mirko Peters welcomes Joe Griffin, Microsoft MVP, CEO of proMX UK, Microsoft Certified Trainer, and one of the most recognized experts in Dynamics 365 Project Operations. With more than 40 Microsoft certifications covering Dynamics 365, Power Platform, Azure, Artificial Intelligence, and the broader Microsoft Cloud ecosystem, Joe brings a unique blend of technical expertise, business leadership, and real-world implementation experience.The conversation explores one of the most important transitions currently happening in the Microsoft project management landscape: the retirement of Microsoft Project Online and the growing adoption of Dynamics 365 Project Operations. Joe explains why organizations should start preparing now, what migration paths are available, and how businesses can use this moment as an opportunity to modernize not only their technology stack but also their project delivery processes.

UNDERSTANDING DYNAMICS 365 PROJECT OPERATIONS

Joe provides a comprehensive overview of Dynamics 365 Project Operations and explains why it has become a strategic platform for project-based organizations. Unlike traditional project management tools that focus solely on task management and scheduling, Project Operations combines project planning, resource allocation, budgeting, financial management, time tracking, expense management, invoicing, and AI-driven insights into a single solution built on Microsoft Dataverse.The discussion highlights how organizations can gain end-to-end visibility across project lifecycles while improving resource utilization and financial performance. Joe also explains how Project Operations leverages familiar Microsoft technologies such as Planner, Power Platform, and Dataverse to create a connected and scalable project management environment.

KEY TAKEAWAYS:

  • What Dynamics 365 Project Operations actually does
  • Who should consider adopting the platform
  • How it differs from traditional project management tools
  • Why professional services organizations benefit the most
  • The role of Dataverse and Power Platform
PROJECT ONLINE RETIREMENT AND MIGRATION STRATEGIES

A major focus of the episode is Microsoft's planned retirement of Project Online. Joe explains what the announcement means for existing customers and outlines the options available for organizations currently relying on Project Online for project planning and portfolio management.Drawing from real-world migration projects, Joe shares practical advice on preparing data, simplifying project structures, and avoiding common migration pitfalls. He also discusses the importance of reviewing legacy processes and using the migration as an opportunity to modernize project management practices.The conversation dives into technical considerations such as Project Desktop files, Scheduler APIs, resource mapping, testing environments, and large-scale migration automation.

MIGRATION TOPICS COVERED:
  • Project Online retirement implications
  • Migration planning and assessment
  • Common data migration challenges
  • Managing complex project portfolios
  • Best practices for successful adoption
HOW AI IS CHANGING PROJECT MANAGEMENT

Artificial Intelligence is rapidly transforming business applications, and Dynamics 365 Project Operations is no exception. Joe explores how Microsoft is embedding AI across the platform and shares practical examples of AI-powered capabilities available today.One particularly interesting example is the Time Entry Agent, which can automatically generate draft timesheets based on calendars, resource assignments, and previous activities. Instead of chasing employees for timesheet submissions, organizations can leverage AI to automate much of the process while maintaining human oversight.The discussion also covers AI-generated project status reports, intelligent resource recommendations, project risk identification, and the future potential of autonomous project management capabilities.

AI IN PROJECT OPERATIONS:
  • Automated time entry generation
  • AI-powered status reporting
  • Intelligent resource recommendations
  • Risk detection and forecasting
  • Future project management agents
POWER PLATFORM AND AZURE INTEGRATION

Joe explains why the real power of Dynamics 365 Project Operations comes from its integration with the wider Microsoft ecosystem. Because the platform is built on Dataverse, organizations can extend functionality using Power Apps, Power Automate, Power BI, Power Pages, and Azure services.Listeners will learn how companies can create custom project experiences, automate business processes, build advanced reporting solutions, and integrate Project Operations with external ERP systems. Joe also discusses how Azure Service Bus, Azure Functions, and modern integration architectures help organizations scale complex project environments.The episode provides valuable guidance for solution architects and technical leaders looking to design enterprise-grade project management solutions that remain scalable and maintainable over time.

ARCHITECTURE AND EXTENSIBILITY TOPICS:
  • Power Apps customization strategies
  • Power Automate workflows
  • Power BI reporting and analytics
  • Azure integration patterns
  • Enterprise architecture best practices
THE ROLE OF MICROSOFT FABRIC AND AI FOUNDRY

Looking ahead, the conversation explores emerging technologies such as Microsoft Fabric and Azure AI Foundry. Joe explains how Fabric can serve as a centralized data foundation for AI initiatives by bringing together information from Dynamics 365, Power Platform, and other business systems.The discussion highlights how organizations that establish strong data foundations today will be better positioned to take advantage of future AI capabilities. Joe also shares his perspective on AI Foundry, model selection, fine-tuning opportunities, and the growing importance of enterprise-ready AI governance.

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 👊

1
00:00:00,000 --> 00:00:04,160
>> Yeah, welcome to another edition of the M665 podcast.

2
00:00:04,160 --> 00:00:09,040
Today's guest is someone who combines deep technical expertise with business leadership

3
00:00:09,040 --> 00:00:11,000
and also a famous singer.

4
00:00:11,000 --> 00:00:18,280
Joe Griffin is a sheet of Pro-MXUK and Microsoft inner circle partner and one of the most respected

5
00:00:18,280 --> 00:00:21,640
voices in the Microsoft Business Application community.

6
00:00:21,640 --> 00:00:27,960
Joe holds more than 40 certifications across dynamics, power platform, Azure, AI and the

7
00:00:27,960 --> 00:00:29,440
wider Microsoft Cloud.

8
00:00:29,440 --> 00:00:35,640
He has also become a Microsoft MVP since 2002 and regular share his knowledge at conferences,

9
00:00:35,640 --> 00:00:37,520
user groups around the world.

10
00:00:37,520 --> 00:00:44,600
His special area is Dynamics 365 project operations, particular technical implementation,

11
00:00:44,600 --> 00:00:46,880
solution architect and Azure integrations.

12
00:00:46,880 --> 00:00:53,520
Today we will explore the Challenging and Organizations faced with moving from project online,

13
00:00:53,520 --> 00:00:59,520
how modern project management is evolving and where AI fits into the future of project delivery.

14
00:00:59,520 --> 00:01:03,760
Yo, so I say, welcome to the show.

15
00:01:03,760 --> 00:01:05,440
>> Welcome, wow, what an intro.

16
00:01:05,440 --> 00:01:07,360
That's really great. Thank you so much.

17
00:01:07,360 --> 00:01:10,880
Have you ever been following me all the time to introduce me?

18
00:01:10,880 --> 00:01:12,480
That's great.

19
00:01:12,480 --> 00:01:20,360
>> Yeah. For listeners who may not know your background, can you tell us about your journey into

20
00:01:20,360 --> 00:01:28,280
the Microsoft ecosystem and a little bit about how you became the CEO of Pro and the XUK?

21
00:01:28,280 --> 00:01:35,920
>> Yeah, sure. I started my life as a humanities student.

22
00:01:35,920 --> 00:01:40,080
From fact about me, I've got a bachelor's in history and then a master's degree in

23
00:01:40,080 --> 00:01:41,600
ancient history.

24
00:01:41,600 --> 00:01:45,320
All that education, obviously, meant I was quite poor by the end of it.

25
00:01:45,320 --> 00:01:50,240
I used to find a job and I just fed into IT doing desktop support and stuff like that.

26
00:01:50,240 --> 00:01:54,360
Then I started to get more and more involved with the Microsoft side of things, things like

27
00:01:54,360 --> 00:01:57,840
SQL Server, .NET, C-Shop, all that sort of good stuff.

28
00:01:57,840 --> 00:02:02,200
Then for the end user that I was working with at the time, we implemented and rolled out

29
00:02:02,200 --> 00:02:03,840
Dynamics CRM 2015.

30
00:02:03,840 --> 00:02:07,360
It was service pack 2 or something like that.

31
00:02:07,360 --> 00:02:12,280
From there, I just fed in with Dynamics, started to work with that.

32
00:02:12,280 --> 00:02:16,080
Eventually, they moved across to the partner side.

33
00:02:16,080 --> 00:02:19,240
Today, yeah, I had a lead UK practice for Pro and X.

34
00:02:19,240 --> 00:02:23,120
We're a bigger partner, headquartered in Germany.

35
00:02:23,120 --> 00:02:30,800
Then around about 2017, 2016, I started to get involved in the community here in the UK,

36
00:02:30,800 --> 00:02:32,360
the Microsoft user groups.

37
00:02:32,360 --> 00:02:36,440
As a public speaker, did quite a bit of blogging and stuff like that.

38
00:02:36,440 --> 00:02:37,880
The rest is history.

39
00:02:37,880 --> 00:02:43,440
I think what's really great is that there is such a strong community on the Microsoft side,

40
00:02:43,440 --> 00:02:46,120
particularly on the business application side of things.

41
00:02:46,120 --> 00:02:52,600
There are really great people all looking to help out and get involved and to really ensure

42
00:02:52,600 --> 00:02:55,360
that people get the most out of these investments and stuff like that.

43
00:02:55,360 --> 00:02:59,480
It's been a real privilege to be involved for the blank for time that I have on making

44
00:02:59,480 --> 00:03:00,480
to new.

45
00:03:00,480 --> 00:03:02,000
Yeah.

46
00:03:02,000 --> 00:03:06,680
You heard all of the burning Microsoft's modifications, what drives your passion for

47
00:03:06,680 --> 00:03:08,800
continuous learning?

48
00:03:08,800 --> 00:03:14,320
I think it started off because I was trying to get more into doing Dynamics and things

49
00:03:14,320 --> 00:03:19,800
that were on a full time, so the basis after I implemented it for the end user.

50
00:03:19,800 --> 00:03:24,640
So, specifications for me became a really great way for me to learn about a topic, to give

51
00:03:24,640 --> 00:03:31,080
me a bit of a drive towards learning towards things and as well when it came to interviews

52
00:03:31,080 --> 00:03:33,640
at the time, when it came to potential job opportunities.

53
00:03:33,640 --> 00:03:35,960
It was a good topic that I could speak about.

54
00:03:35,960 --> 00:03:38,920
Oh, okay, I've been revising for these exams.

55
00:03:38,920 --> 00:03:42,040
I've been in my spare time.

56
00:03:42,040 --> 00:03:46,840
It's a nice conversation piece in those interviews scenarios.

57
00:03:46,840 --> 00:03:52,600
Today as well, I'm also a Microsoft certified trainer as well, so in order to be able to

58
00:03:52,600 --> 00:03:55,880
teach across, you need to have held the relevant certification.

59
00:03:55,880 --> 00:04:01,160
So for that reason, it's a good way to keep on top of what's happening, particularly

60
00:04:01,160 --> 00:04:02,880
AI, a lot of things change at the moment.

61
00:04:02,880 --> 00:04:06,200
So every week it feels like there's new things.

62
00:04:06,200 --> 00:04:08,120
Exams can be a good way of keeping it straight there.

63
00:04:08,120 --> 00:04:09,120
Yeah.

64
00:04:09,120 --> 00:04:16,320
How has being Microsoft MVP and MCD influence your career perspective on technology?

65
00:04:16,320 --> 00:04:19,680
It's really, in terms of moving my career forward, it's been quite sort of transformational

66
00:04:19,680 --> 00:04:21,120
from a technology standpoint.

67
00:04:21,120 --> 00:04:29,120
It's also been able to get a bit of a window in terms of, okay, what's happening with the

68
00:04:29,120 --> 00:04:30,920
technology.

69
00:04:30,920 --> 00:04:35,680
The most viable professionals are quite fortunate in that we're all kind of invited to an event

70
00:04:35,680 --> 00:04:39,480
every year called the MVP Summit, every in Redmond, and that gives a really good opportunity

71
00:04:39,480 --> 00:04:43,400
to get a window in terms of what Microsoft are kind of doing.

72
00:04:43,400 --> 00:04:47,480
A lot of it is under strict sort of NDA, so there's not something that we can talk about,

73
00:04:47,480 --> 00:04:51,960
but yeah, being able to have those conversations, being able to influence kind of the roadmap

74
00:04:51,960 --> 00:04:58,640
and kind of thinking there, I think is really sort of great and helps in terms of when

75
00:04:58,640 --> 00:05:02,320
we're sort of guiding and advising customers about where they need to be focused on next.

76
00:05:02,320 --> 00:05:15,280
Yeah, you are an expert on Microsoft Dynamics 365 project operations for those who aren't

77
00:05:15,280 --> 00:05:19,120
familiar with it, what exactly is it?

78
00:05:19,120 --> 00:05:21,920
So it's one of the Dynamics 365 modules.

79
00:05:21,920 --> 00:05:22,920
It's kind of a weird one.

80
00:05:22,920 --> 00:05:27,760
It's technically NERP on the ERP side of things when it comes to Dynamics, but it's actually

81
00:05:27,760 --> 00:05:34,480
mainly sort of provided through the customer engagements for the site and things as well.

82
00:05:34,480 --> 00:05:38,120
So it hosts on data verse, it's more driven app or this sort of good stuff.

83
00:05:38,120 --> 00:05:42,960
Basically, if you as an organisation are delivering or setting projects frequently, you need to

84
00:05:42,960 --> 00:05:46,240
be doing things like we're breakdown structure planning, if you need to be doing things

85
00:05:46,240 --> 00:05:53,000
like time entries, managing contracts, expenses, and drive through into sort of invoicing on

86
00:05:53,000 --> 00:05:56,800
either a pro-form or an actual sort of basis, then yeah, project operations is kind of

87
00:05:56,800 --> 00:06:00,120
the module for us for you, I would say.

88
00:06:00,120 --> 00:06:04,800
So typically we find project, professional services organisations, people who are delivering

89
00:06:04,800 --> 00:06:08,760
quite sort of big initiatives and projects, it's a really good fit there for the project

90
00:06:08,760 --> 00:06:10,640
operations kind of module.

91
00:06:10,640 --> 00:06:17,000
So yeah, as I said, it also is unique as well, because it brings in some capability from

92
00:06:17,000 --> 00:06:19,040
the Microsoft Planar side.

93
00:06:19,040 --> 00:06:23,840
So the whole planar board, task grade down board is sort of integrated very closely into

94
00:06:23,840 --> 00:06:24,920
sort of the project as well.

95
00:06:24,920 --> 00:06:30,160
So for those people who are maybe familiar working with project desktop, project operations

96
00:06:30,160 --> 00:06:34,680
for a nice way of being able to kind of, yeah, modernise what you're doing, have it stored

97
00:06:34,680 --> 00:06:38,160
in a nice sort of structured database and then benefit for a few of that, I've kind of

98
00:06:38,160 --> 00:06:39,880
just spoken about already.

99
00:06:39,880 --> 00:06:46,800
And what business problems do project operations all better than, yeah, say, traditional project

100
00:06:46,800 --> 00:06:51,160
management tools, the Microsoft earlier, a lot of tools.

101
00:06:51,160 --> 00:06:52,160
Yeah.

102
00:06:52,160 --> 00:06:57,120
So it's all about just helping deliver our projects on time and be able to manage our budgets.

103
00:06:57,120 --> 00:07:02,800
If it's quite a big initiative, you know, we can think of budgets within the application

104
00:07:02,800 --> 00:07:03,800
as well.

105
00:07:03,800 --> 00:07:10,040
The application will also support the ability to do things, to also tap into AI functionality.

106
00:07:10,040 --> 00:07:13,280
So for example, we have a few different co-pilot and agents now.

107
00:07:13,280 --> 00:07:15,480
We can generate status reports very easily.

108
00:07:15,480 --> 00:07:20,160
We've got a time entry agent that can go and automate the creation of all through a different

109
00:07:20,160 --> 00:07:25,040
sort of time entries and then manage those approval processes as well as also using co-pilot

110
00:07:25,040 --> 00:07:29,160
to go and generate work breakdown structures based on just a simple project title, description

111
00:07:29,160 --> 00:07:30,200
and all that sort of good stuff.

112
00:07:30,200 --> 00:07:34,720
So really addressing some of the common challenges that we need around managing projects,

113
00:07:34,720 --> 00:07:39,440
making sure they can be delivered well effectively, making sure that we can assign the right people

114
00:07:39,440 --> 00:07:44,680
onto the projects and have visibility around the utilization where they've been sort of

115
00:07:44,680 --> 00:07:51,720
used and averaged, because as well the application also uses the universe, the universe of resource

116
00:07:51,720 --> 00:07:56,080
scheduling, the urs functionality that you may be familiar with, things like customer service

117
00:07:56,080 --> 00:07:59,240
and field service and things like that.

118
00:07:59,240 --> 00:08:06,000
And what types of organization benefit most from implementation project operations?

119
00:08:06,000 --> 00:08:08,440
As mentioned, professional services is where we see a lot.

120
00:08:08,440 --> 00:08:13,520
So partners like us, for example, so we use project operations ourselves sort of internally.

121
00:08:13,520 --> 00:08:17,000
We also have clients as well, working in different sort of industries.

122
00:08:17,000 --> 00:08:29,080
So gas and oil, we also have other, we have examples of sort of a train organizations,

123
00:08:29,080 --> 00:08:31,560
infrastructure companies and things like that who also use it as well.

124
00:08:31,560 --> 00:08:37,480
So I think if you, as an organization, if you're delivering projects regularly, big projects

125
00:08:37,480 --> 00:08:41,040
almost to the point of maybe, you know, maybe, maybe more than thousands or maybe more

126
00:08:41,040 --> 00:08:45,120
than 40 millions of euros, then it's going to be a good fit, you'd say, to have project operations

127
00:08:45,120 --> 00:08:46,640
in the mix.

128
00:08:46,640 --> 00:08:55,680
And what, I say, some typical list conceptions organization have before, adapting the platform?

129
00:08:55,680 --> 00:09:01,840
I think that some misconceptions that they maybe have, it's kind of an interesting sort of module

130
00:09:01,840 --> 00:09:05,960
because it kind of sits between both the C and the ERP side of things.

131
00:09:05,960 --> 00:09:09,360
So maybe when they approach you for the first time, they'll say, oh, this is just one

132
00:09:09,360 --> 00:09:10,360
of the NERP apps.

133
00:09:10,360 --> 00:09:14,440
So therefore it's going to be clunky, it's going to be difficult to implement.

134
00:09:14,440 --> 00:09:17,800
It's not really for, you know, businesses of our sort of side.

135
00:09:17,800 --> 00:09:22,240
And in actual fact, you know, most of the functionality in project operations is driven

136
00:09:22,240 --> 00:09:25,040
by the customer engagements to have the platform.

137
00:09:25,040 --> 00:09:28,240
And this means that it's then leverage in all of the power platform functionality.

138
00:09:28,240 --> 00:09:32,960
So it becomes quite easy for us to go tailor, you know, create some flows, power to make

139
00:09:32,960 --> 00:09:38,640
flows, you know, modify data versus modify the data schema and to, and to extend things

140
00:09:38,640 --> 00:09:40,240
out very nicely and very easily.

141
00:09:40,240 --> 00:09:44,920
So, you know, definitely that's a big misconception around okay, how difficult it is to sort of

142
00:09:44,920 --> 00:09:50,200
roll this out in actual fact, you can deploy project operations in kind of the core mode,

143
00:09:50,200 --> 00:09:53,440
where you don't have any ERP sort of dependency.

144
00:09:53,440 --> 00:09:57,880
And then you can from there go and integrate if any ERP system that you choose or indeed

145
00:09:57,880 --> 00:10:01,160
just run it in complete isolation on the C platform.

146
00:10:01,160 --> 00:10:02,160
Yeah.

147
00:10:02,160 --> 00:10:08,680
And one of your areas of expertise is helping organizationally grade from project online,

148
00:10:08,680 --> 00:10:17,160
why are the companies are ever elevated to that to move today?

149
00:10:17,160 --> 00:10:20,000
So you may have seen the announcement you made, not a third of it.

150
00:10:20,000 --> 00:10:22,840
So hopefully it's not a huge surprise when I'm saying this, but yeah, project online is

151
00:10:22,840 --> 00:10:27,000
going to be kind of retired a little bit later on this year by the end of September is

152
00:10:27,000 --> 00:10:31,160
going to be a case that if you're still using project online and project online just

153
00:10:31,160 --> 00:10:34,680
to be clear, that's the one that's using SharePoint behind the scenes.

154
00:10:34,680 --> 00:10:38,640
There are a few different products that are quite similar, similar sort of names.

155
00:10:38,640 --> 00:10:45,240
So if you're using the project online, which is based on SharePoint, which also has a dependency

156
00:10:45,240 --> 00:10:50,960
and allows you to integrate with project desktop then after September that the solution

157
00:10:50,960 --> 00:10:56,040
will be retired and all of your data on there will then become kind of redone me.

158
00:10:56,040 --> 00:11:00,720
So if you're wanting to continue to have the same kind of functionality available, you're

159
00:11:00,720 --> 00:11:03,960
going to have to consider moving into a different sort of option.

160
00:11:03,960 --> 00:11:08,440
Microsoft have kind of got three routes that they provided or through three ways in which

161
00:11:08,440 --> 00:11:09,760
you can sort of do this.

162
00:11:09,760 --> 00:11:15,160
The first is that you can use Microsoft Planner as one solution.

163
00:11:15,160 --> 00:11:21,360
You can potentially go back on premise using project server, project server as an alternative

164
00:11:21,360 --> 00:11:26,120
or the third option and the one that's how I would recommend for obvious reasons based

165
00:11:26,120 --> 00:11:28,760
on what we described will be project operations.

166
00:11:28,760 --> 00:11:34,640
So yeah, if your organization currently relies on project online in a significant sort of

167
00:11:34,640 --> 00:11:39,160
way, then you very much need to be starting to have those conversations about how you can

168
00:11:39,160 --> 00:11:44,680
manage this transition and move across to an alternative solution.

169
00:11:44,680 --> 00:11:52,040
But they must have dynamics in the company to use project operations or...

170
00:11:52,040 --> 00:11:53,040
Cool edge, yeah.

171
00:11:53,040 --> 00:11:56,440
So for any of the options that you go down whether it's Planner, whether it's project server

172
00:11:56,440 --> 00:12:02,240
or project operations, then yeah, you need to have the licenses and all this sort of stuff.

173
00:12:02,240 --> 00:12:07,520
Going back on premise for all of this is probably not a route that I would kind of advise.

174
00:12:07,520 --> 00:12:12,680
Certainly if you're as an organization wanting to do, you start to leverage our fresh intelligence

175
00:12:12,680 --> 00:12:13,680
more.

176
00:12:13,680 --> 00:12:18,000
I think as well long term, the project server offering, I think will eventually be retired

177
00:12:18,000 --> 00:12:24,160
because there's not going to be two investments towards that sort of moving forward.

178
00:12:24,160 --> 00:12:26,400
Planner can do a pretty good job into what you sort of do.

179
00:12:26,400 --> 00:12:30,800
It does support the ability to integrate with Power Platform, but generally we find that

180
00:12:30,800 --> 00:12:35,080
for a lot of organizations who are using project online who are aligned on features like

181
00:12:35,080 --> 00:12:40,400
time entries and the more complex kind of work breakdown structure requirements, we

182
00:12:40,400 --> 00:12:45,200
tend to find that project operations provide a better long term sort of fit and means that

183
00:12:45,200 --> 00:12:49,520
you don't have to go and build a whole bunch of functionality from scratch.

184
00:12:49,520 --> 00:12:53,600
Project operations has that all sort of able for you.

185
00:12:53,600 --> 00:12:58,760
And what are the most common challenges, yeah, organization and counterburing the migration

186
00:12:58,760 --> 00:13:00,760
project?

187
00:13:00,760 --> 00:13:05,640
Data complexity, I don't know about you, I've seen pretty weird and wonderful project desktop

188
00:13:05,640 --> 00:13:11,280
MPP files in my time, you know, lots of different tasks, kind of many different sort of resource

189
00:13:11,280 --> 00:13:15,920
assignments, complex task dependencies, all of this sort of good stuff.

190
00:13:15,920 --> 00:13:20,640
So the challenge is that we tend to find usually is around the data, how can we sort of

191
00:13:20,640 --> 00:13:25,520
maybe use it as an opportunity to simplify things, it's something to be kind of aware of

192
00:13:25,520 --> 00:13:31,880
with project operations is that there are, you know, some sort of limits in terms of things

193
00:13:31,880 --> 00:13:35,840
like, okay, the number of tasks for a project, number of resource assignment support to

194
00:13:35,840 --> 00:13:38,400
task dependencies and things like that.

195
00:13:38,400 --> 00:13:43,560
So it does means that certain organizations will need to maybe look at how they're building

196
00:13:43,560 --> 00:13:47,680
their MPP files, how they're building their work breakdown structures and just see if

197
00:13:47,680 --> 00:13:52,600
there's an opportunity there to kind of simplify that because, and as well from a data migration

198
00:13:52,600 --> 00:13:57,760
standpoint, there are some considerations around that that we need to be kind of mindful

199
00:13:57,760 --> 00:14:00,280
of and again, can be another challenge here.

200
00:14:00,280 --> 00:14:05,640
So if you're wanting to, for example, take a project, take an MPP file and kind of import

201
00:14:05,640 --> 00:14:12,480
that in, you can do that in the tool that is possible to do on a project, per project desktop

202
00:14:12,480 --> 00:14:16,720
file sort of basis, but if you're wanting to migrate maybe hundreds or maybe thousands

203
00:14:16,720 --> 00:14:20,480
of different sort of projects, then you're going to have to go and automate that potentially

204
00:14:20,480 --> 00:14:25,440
and this is where we need to look at how we can leverage something known as the schedule

205
00:14:25,440 --> 00:14:26,960
API in the tool.

206
00:14:26,960 --> 00:14:33,480
Schedule API is basically will give us the ability to go and create the appropriate project

207
00:14:33,480 --> 00:14:39,000
operations like our projects, project tasks, our resource assignments and all that sort

208
00:14:39,000 --> 00:14:43,200
of good stuff because we're not allowed to in the application to go and directly write

209
00:14:43,200 --> 00:14:48,400
to those tables, we have to go through what's called the PSS sort of service, which then just

210
00:14:48,400 --> 00:14:52,480
ensures that okay, create the data, both on the data, the side and also on the planar board

211
00:14:52,480 --> 00:14:55,520
and everything is kind of correct from that sort of standpoint.

212
00:14:55,520 --> 00:15:00,520
So that can be another challenge that organizations have, okay, how can we migrate all of these

213
00:15:00,520 --> 00:15:04,360
projects in bulk, how can we successfully sort of use the schedule API in a good sort of

214
00:15:04,360 --> 00:15:09,640
way and really just ensure that we can migrate all this data successfully.

215
00:15:09,640 --> 00:15:14,440
And what data migration pitfalls, so it comes on these watch out for?

216
00:15:14,440 --> 00:15:17,600
Sorry, a couple of that questions.

217
00:15:17,600 --> 00:15:22,560
Yeah, yeah, what data migration pitfalls, so it comes on these watch out for?

218
00:15:22,560 --> 00:15:26,680
Yeah, I think it goes back to, again, as I mentioned, complexity.

219
00:15:26,680 --> 00:15:30,160
So try and just to keep, you know, keeping simple stupid, because it's always going to be

220
00:15:30,160 --> 00:15:31,880
a good thing over here.

221
00:15:31,880 --> 00:15:35,840
So use the migration opportunities to kind of simplify what you're doing.

222
00:15:35,840 --> 00:15:39,920
You know, is there a reason why your work breakdowns are so complex?

223
00:15:39,920 --> 00:15:43,840
You always need to think about things like, okay, how can we map out our resource and our

224
00:15:43,840 --> 00:15:46,680
resource profiles in a really good way in the tool?

225
00:15:46,680 --> 00:15:50,800
So we have to, for example, consider how we go and create bookable resources, how we create

226
00:15:50,800 --> 00:15:56,240
roles and skills and characteristics for those resources to represent their sort of skills

227
00:15:56,240 --> 00:15:59,160
and making sure that is also the done as well.

228
00:15:59,160 --> 00:16:04,040
Many organizations will need to ensure that they've got the appropriate dev test production

229
00:16:04,040 --> 00:16:06,120
environment configured there.

230
00:16:06,120 --> 00:16:12,160
So again, thinking about how we can kind of ensure the data is aligned accordingly, configuration

231
00:16:12,160 --> 00:16:14,440
data and all this sort of stuff is aligned.

232
00:16:14,440 --> 00:16:19,520
Who good news is that there's tooling available in the platform, things like, for example,

233
00:16:19,520 --> 00:16:24,560
the configuration migration tool that we can use to help us with that sort of process,

234
00:16:24,560 --> 00:16:27,840
but it's definitely something to think about so we can ensure that, you know, we're aligning

235
00:16:27,840 --> 00:16:29,160
data correctly.

236
00:16:29,160 --> 00:16:32,840
We can test things in the correct sort of way and that, you know, when we do our deployment

237
00:16:32,840 --> 00:16:37,000
to production, you know, all of the, all of our kind of ducks are in a row, everything is

238
00:16:37,000 --> 00:16:40,520
configured correctly for us to be successful.

239
00:16:40,520 --> 00:16:46,200
And what do us as successful and regression project look like from your perspective?

240
00:16:46,200 --> 00:16:51,360
From my perspective, if we can get all the projects to move across, if people, if project managers

241
00:16:51,360 --> 00:16:56,280
can do their job, they can go and, you know, find their projects effectively, they can assign

242
00:16:56,280 --> 00:16:59,880
their resources and they can ultimately make sure they're delivering their projects

243
00:16:59,880 --> 00:17:03,600
on time and on budget, then I think that's a pretty good success criteria for me because

244
00:17:03,600 --> 00:17:07,880
that is the key thing that the tool, the tool can support you in doing.

245
00:17:07,880 --> 00:17:13,240
And how do you approach, I say, stakeholder adaption and change management?

246
00:17:13,240 --> 00:17:15,600
And it's a great question.

247
00:17:15,600 --> 00:17:20,000
We have to always try and take people on the journey with us, you know, show them the

248
00:17:20,000 --> 00:17:26,240
benefits of the tool, engage early on with those sort of key personas, look to see what

249
00:17:26,240 --> 00:17:30,400
we can do in terms of maybe identifying some champions within the sort of company who can

250
00:17:30,400 --> 00:17:35,280
kind of help drive things sort of forward and really just focus on what we can do to make

251
00:17:35,280 --> 00:17:40,600
the user interface make the processes as easy and straightforward as possible.

252
00:17:40,600 --> 00:17:44,200
And this is a good thing about the fact that we can tap into the power platform, you know,

253
00:17:44,200 --> 00:17:49,440
it's possible for us to go and build out these custom interfaces, you know, we can use

254
00:17:49,440 --> 00:17:55,040
technologies like, for example, custom pages to make the fly day more streamlined interface

255
00:17:55,040 --> 00:17:59,920
with what we have now from an AI standpoint is possible for us to maybe do things like,

256
00:17:59,920 --> 00:18:06,400
you know, build, you know, vibe out, you know, applications, build out some web interfaces

257
00:18:06,400 --> 00:18:08,160
that can then be sort of then taken forward.

258
00:18:08,160 --> 00:18:11,120
And then again, can really simplify things from that sort of standpoint.

259
00:18:11,120 --> 00:18:17,280
So it's going to be important that we sort of look at each sort of organization's processes,

260
00:18:17,280 --> 00:18:21,720
try and align to what the tool supports natively out the boxes, which is possible.

261
00:18:21,720 --> 00:18:26,760
But then beyond that, using what we have in the power platform to, you know, do those deviations

262
00:18:26,760 --> 00:18:31,200
away, make it easy and straightforward for the company question for the users to be able

263
00:18:31,200 --> 00:18:32,800
to get the job done.

264
00:18:32,800 --> 00:18:41,600
Yeah, can you share a memorial number, the recreation success story or lesson to learn without

265
00:18:41,600 --> 00:18:45,640
explaining the client?

266
00:18:45,640 --> 00:18:48,480
Yeah, we have one of our U.S. clients that this has done.

267
00:18:48,480 --> 00:18:51,960
I wasn't involved myself in the project as one of my team members, sort of colleagues, but

268
00:18:51,960 --> 00:18:56,200
yeah, we were able to in the end migrate across all the projects.

269
00:18:56,200 --> 00:19:00,240
We built out a whole bunch of scripting that's targeted the scheduled API.

270
00:19:00,240 --> 00:19:04,240
We were able to then ensure that that was then able to be run repeatedly.

271
00:19:04,240 --> 00:19:08,520
And we were able to sort of do over several different kind of iterations, you know, test

272
00:19:08,520 --> 00:19:10,080
migrations and things like that.

273
00:19:10,080 --> 00:19:15,120
So, you know, there in the end, we were able to sort of get everything migrated across successfully.

274
00:19:15,120 --> 00:19:20,200
We've no sort of issues, the fact that we were able to, you know, make those scripting,

275
00:19:20,200 --> 00:19:23,360
make those scripts sort of repeatable, really kind of helped us a part of that.

276
00:19:23,360 --> 00:19:26,880
We could very quickly and easily, you know, spin up an environment run the scripts, check

277
00:19:26,880 --> 00:19:29,960
to see if there's anything sort of work there.

278
00:19:29,960 --> 00:19:34,760
And as well, we were able to handle the sheer volume of data by, you know, by making sure

279
00:19:34,760 --> 00:19:38,280
these scripts could be run, you know, in a virtual environment can be run in the background

280
00:19:38,280 --> 00:19:40,240
that stuff I've got.

281
00:19:40,240 --> 00:19:45,440
And to be sure, they're targeting the supported APIs that Microsoft give, you know, the schedule

282
00:19:45,440 --> 00:19:47,640
API and things like that.

283
00:19:47,640 --> 00:19:56,560
And there are, I don't know, something or companies can prepare for a successful migration

284
00:19:56,560 --> 00:19:58,560
project.

285
00:19:58,560 --> 00:20:02,480
I think it's going to be a case of looking at what you have from a, from an MPP, from

286
00:20:02,480 --> 00:20:04,760
a project, desktop sort of standpoint.

287
00:20:04,760 --> 00:20:09,480
So Microsoft, you provide some resources online that sort of talks through a KB, what is

288
00:20:09,480 --> 00:20:13,600
supported, what isn't supported, when we're sort of migrating things.

289
00:20:13,600 --> 00:20:17,560
So looking at that very carefully is going to be, is going to be useful as part of your

290
00:20:17,560 --> 00:20:19,040
sort of processes.

291
00:20:19,040 --> 00:20:23,000
And as well, just try and use it as an opportunity to simplify things.

292
00:20:23,000 --> 00:20:27,920
And maybe as well challenge the ways of working a KB, well, why are we having such complex

293
00:20:27,920 --> 00:20:28,920
work breakdown structures?

294
00:20:28,920 --> 00:20:32,760
You know, why are we having, you know, so many different sort of resource assignments,

295
00:20:32,760 --> 00:20:36,720
you know, do we need to have this level of complexity from a dependency standpoint?

296
00:20:36,720 --> 00:20:41,120
I think it's, it's always a good opportunity as part of any migration to actually take

297
00:20:41,120 --> 00:20:45,880
a step back and actually critically look at, okay, you know, is there a good business

298
00:20:45,880 --> 00:20:47,520
reason why we're doing things this way?

299
00:20:47,520 --> 00:20:53,040
Or is it, are we just doing this, doing this, this way because we've always done it and

300
00:20:53,040 --> 00:20:57,800
we don't want to rock the boat or cause any problems by deviating away from that?

301
00:20:57,800 --> 00:21:04,440
Yeah, I see, although Microsoft is, yeah, embedding it across every application.

302
00:21:04,440 --> 00:21:06,440
Yeah, exactly.

303
00:21:06,440 --> 00:21:11,720
Well, how do you see a eye-transforming project operations, especially?

304
00:21:11,720 --> 00:21:15,880
I think I mentioned some of the functionalities already, so I quite like at the moment things

305
00:21:15,880 --> 00:21:19,360
like the time entry agent, which is a really good use case there because, you know, it's

306
00:21:19,360 --> 00:21:24,400
for organizations like ours, partners, you know, a pressurization organizations, you know,

307
00:21:24,400 --> 00:21:27,920
time entries, having to do all of that on a week to week basis.

308
00:21:27,920 --> 00:21:32,640
It's, it's, it's the job that we hate, but the job that we have to do in order to be

309
00:21:32,640 --> 00:21:36,360
able to sort of, you know, ensure that we can invoice and, you know, generate revenue

310
00:21:36,360 --> 00:21:37,360
for the business.

311
00:21:37,360 --> 00:21:41,560
And so the great thing about the time entry agent is that it can automate a lot of those

312
00:21:41,560 --> 00:21:42,560
key sort of steps.

313
00:21:42,560 --> 00:21:47,440
It can go and look at, you know, what we have in terms of our existing resource assignments,

314
00:21:47,440 --> 00:21:48,600
our outlook appointments.

315
00:21:48,600 --> 00:21:53,800
It can go and preemptively sort of generate those time entries in kind of a draft form,

316
00:21:53,800 --> 00:21:57,760
based on, you know, what it thinks we're going to be doing and working on from there, the

317
00:21:57,760 --> 00:22:00,920
agent can then sort of come to life at the right point of the week and sort of say,

318
00:22:00,920 --> 00:22:04,200
hey, hey, Joe, here are your time entries for the week ahead.

319
00:22:04,200 --> 00:22:09,440
Go and review them, make sure they look okay, and then go and submit them from there.

320
00:22:09,440 --> 00:22:13,440
And as well, the agent can then handle the, okay, chasing up with people, you know, if

321
00:22:13,440 --> 00:22:16,880
I've not done anything there, you know, after a few days, you can just go knock on my door

322
00:22:16,880 --> 00:22:19,840
and go, Joe, you need to go and submit your time entries.

323
00:22:19,840 --> 00:22:23,200
You know, so really reducing the need for somebody, for, you know, somebody in the

324
00:22:23,200 --> 00:22:27,400
organization to have to go around and basically chase everyone for that information.

325
00:22:27,400 --> 00:22:32,240
Once the time entry is then submitted in the tool itself, we can then configure additional

326
00:22:32,240 --> 00:22:35,880
artificial intelligence capability to then handle the approvals process and that can

327
00:22:35,880 --> 00:22:41,240
be done based on a policy document and then the agent can just go and preemptively sort

328
00:22:41,240 --> 00:22:45,480
of approve or reject time entries, you know, as long as it meets the criteria, the boundaries

329
00:22:45,480 --> 00:22:46,480
for all positions.

330
00:22:46,480 --> 00:22:54,320
So these are usually very laborious processes, very time intensive sort of processes, you

331
00:22:54,320 --> 00:22:58,880
know, requiring human intervention, sort of do this and all this can now become a automated

332
00:22:58,880 --> 00:23:00,040
quite massive agent.

333
00:23:00,040 --> 00:23:04,880
So I really like the potential there that that sort of shows for the technology.

334
00:23:04,880 --> 00:23:14,880
So those helps, especially in resource planning, as they're also, I say, co-pilot for forecasting

335
00:23:14,880 --> 00:23:15,880
a project.

336
00:23:15,880 --> 00:23:20,440
Yeah, so there's tools there in terms of being able to generate the status reports, we can

337
00:23:20,440 --> 00:23:23,920
also do things like get suggestions for resources.

338
00:23:23,920 --> 00:23:27,200
So when we're going and planning for a project, we can basically get a list of people who

339
00:23:27,200 --> 00:23:31,880
we think are going to be a good fit based on previous sort of project performance, based

340
00:23:31,880 --> 00:23:35,840
on their current availability and we get kind of like a scorecard there that kind of just

341
00:23:35,840 --> 00:23:40,520
allow the outlines in terms of what is possible there.

342
00:23:40,520 --> 00:23:45,080
So a lot of investments going into the air from charity at the moment, particularly for

343
00:23:45,080 --> 00:23:46,880
project operations.

344
00:23:46,880 --> 00:23:50,840
So I think the future is going to be quite exciting in terms of what we see in future.

345
00:23:50,840 --> 00:23:51,840
Yeah.

346
00:23:51,840 --> 00:23:59,440
I think also, I don't know, it's possible, but I think it's also be awesome if AI can help

347
00:23:59,440 --> 00:24:09,880
to see project risk or risk, I think that's good also be an interesting case for AI.

348
00:24:09,880 --> 00:24:10,880
Yeah.

349
00:24:10,880 --> 00:24:11,920
So it does that stay actually.

350
00:24:11,920 --> 00:24:18,080
So at any point when the project's in delivery, you can go in and basically generate a series

351
00:24:18,080 --> 00:24:22,720
of risks for the project, it goes and looks at the data in the tool already, it looks at

352
00:24:22,720 --> 00:24:28,000
the assignments, the time entries, what's been submitted, whether we're close to budget

353
00:24:28,000 --> 00:24:31,200
or over budget and stuff like that and then we'll go and generate those risks for you.

354
00:24:31,200 --> 00:24:36,600
So that is a feature that's been there for a while now and can be sort of an excuse at

355
00:24:36,600 --> 00:24:37,600
any time.

356
00:24:37,600 --> 00:24:38,600
So.

357
00:24:38,600 --> 00:24:40,800
Yeah, that's interesting.

358
00:24:40,800 --> 00:24:48,040
And what will you say place the power platform and yeah, I say extending a product

359
00:24:48,040 --> 00:24:49,040
operations.

360
00:24:49,040 --> 00:24:55,760
It's an important component and one that we do very often on projects here.

361
00:24:55,760 --> 00:25:00,720
So having all of that power platform functionality there are feet means that we can go and for

362
00:25:00,720 --> 00:25:06,840
example, if we want to build an external website that allows maybe contractors to go and

363
00:25:06,840 --> 00:25:10,480
submit time entries, we can use power pages to build that out.

364
00:25:10,480 --> 00:25:14,840
If we need a more complex report, we can go and use power BI to help us with that.

365
00:25:14,840 --> 00:25:19,760
As mentioned already, we can do database schema level changes quite sort of easy and straight

366
00:25:19,760 --> 00:25:24,800
forwardly into the database and then go and build out custom app interfaces using power apps.

367
00:25:24,800 --> 00:25:29,320
So a lot of potential there to use the power platform and it really just help us, you know,

368
00:25:29,320 --> 00:25:33,400
when we need to sort of tear the application for more specific needs.

369
00:25:33,400 --> 00:25:42,520
And how did we handle governance and compliance, especially in project operation?

370
00:25:42,520 --> 00:25:46,120
So all of that, if again, falls back onto the power platform, sort of capability.

371
00:25:46,120 --> 00:25:52,440
So we know that for example, we can use features like data, cross prevention policies to allow

372
00:25:52,440 --> 00:25:54,400
to allow certain connectors.

373
00:25:54,400 --> 00:25:59,040
We know that we've got the full capabilities of data, versus from a role-based actors control

374
00:25:59,040 --> 00:26:00,040
standpoint.

375
00:26:00,040 --> 00:26:04,960
So we can use things like business units, security roles, teams, we can even encrypt specific

376
00:26:04,960 --> 00:26:08,000
columns using column security, sort of profiles.

377
00:26:08,000 --> 00:26:11,800
And then we know that, you know, at the power platform level, at the app, in central level,

378
00:26:11,800 --> 00:26:14,040
these are just data versus environments.

379
00:26:14,040 --> 00:26:19,480
So everything the data versus gives us things like managing environments, fees like pipelines,

380
00:26:19,480 --> 00:26:24,400
a handler application, lifecycle management processes, you know, all of that is immediately

381
00:26:24,400 --> 00:26:30,360
sort of supported, you know, with no additional sort of hurdle that we have to go over.

382
00:26:30,360 --> 00:26:31,360
Yeah.

383
00:26:31,360 --> 00:26:37,880
And I think, you know, we have co-pilot studio, or I think really new is co-pilot scout,

384
00:26:37,880 --> 00:26:40,480
I think, with the agents.

385
00:26:40,480 --> 00:26:46,800
Because they are also a capability for this in, yeah, in project operations.

386
00:26:46,800 --> 00:26:47,800
Yeah.

387
00:26:47,800 --> 00:26:50,560
So co-pilot studio, we can go build on custom agents.

388
00:26:50,560 --> 00:26:53,560
We think we can go and connect that into data versus directly.

389
00:26:53,560 --> 00:26:57,120
So for more specific scenarios that we want to work with, then it becomes very easy to

390
00:26:57,120 --> 00:26:58,840
build those out as well.

391
00:26:58,840 --> 00:27:02,040
All of the first party agents that Microsoft provide to us.

392
00:27:02,040 --> 00:27:07,280
So for example, time entry agent that I mentioned sort of before, that can also be customized

393
00:27:07,280 --> 00:27:08,280
as well by us.

394
00:27:08,280 --> 00:27:12,480
If we want to go and extend things out, maybe have some additional scenarios that the

395
00:27:12,480 --> 00:27:19,000
time entry agent can sort of support, then we can go and do that very easily, very straightforward.

396
00:27:19,000 --> 00:27:26,960
And did you think the AI could also become a project manager, or is there a need for human

397
00:27:26,960 --> 00:27:29,080
in the loop?

398
00:27:29,080 --> 00:27:32,800
I think we're moving into that direction, the technology, you can date today, certainly

399
00:27:32,800 --> 00:27:34,040
sort of support it.

400
00:27:34,040 --> 00:27:37,000
I think, you know, it's always going to be a case that we need to have these processes

401
00:27:37,000 --> 00:27:42,120
for the auditable, where there will be certain scenarios where we do need to get human approval

402
00:27:42,120 --> 00:27:43,120
there.

403
00:27:43,120 --> 00:27:47,440
Maybe if it is a sort of a scenario that we don't see too often, maybe an edge case sort

404
00:27:47,440 --> 00:27:50,120
of process, things like that.

405
00:27:50,120 --> 00:27:54,880
But yeah, I think it's possible that, you know, for PMO type level roles, you know, for

406
00:27:54,880 --> 00:27:59,000
somebody, somebody who's maybe working in the PMO office who's responsible for just

407
00:27:59,000 --> 00:28:03,360
going and chasing sort of time entries, you know, that sort of function can be sort of

408
00:28:03,360 --> 00:28:04,360
eliminated.

409
00:28:04,360 --> 00:28:08,240
We're still going to need to have the project manager kind of involved there.

410
00:28:08,240 --> 00:28:12,720
It's going to hopefully allow them to be in a situation where they can manage, you know,

411
00:28:12,720 --> 00:28:16,880
things on maybe a 10X basis, so they can manage more projects more easily.

412
00:28:16,880 --> 00:28:20,960
And using AI to kind of just help them help them to manage all of that, you know, at a much

413
00:28:20,960 --> 00:28:21,960
more grand scale.

414
00:28:21,960 --> 00:28:29,600
If Microsoft comes tomorrow and says, hey, Joe, you get all the money you need, the employees,

415
00:28:29,600 --> 00:28:36,800
what feature will you, the Vennel in the next 65 project operations?

416
00:28:36,800 --> 00:28:40,600
Oh, that is a good question.

417
00:28:40,600 --> 00:28:50,720
I would certainly like to have to think now, actually, I think there's definitely some

418
00:28:50,720 --> 00:28:55,760
good stuff coming in terms of the field service integration, which is looking quite sort

419
00:28:55,760 --> 00:29:05,200
of good. It would be really nice to sort of have it sort of tailor out some aspects of the

420
00:29:05,200 --> 00:29:06,200
plan aboard.

421
00:29:06,200 --> 00:29:07,200
Yeah.

422
00:29:07,200 --> 00:29:11,440
So to be able to support additional sort of capabilities, we often see that, yeah, the

423
00:29:11,440 --> 00:29:14,520
planning capabilities are not quite on a power of project desktop.

424
00:29:14,520 --> 00:29:18,760
So I probably focus my attention on trying to make that a bit more sort of expansive, make

425
00:29:18,760 --> 00:29:23,480
it easier for us to maybe go and export our into project desktop and then go and import

426
00:29:23,480 --> 00:29:28,480
back into the tool because those are kind of the scenarios that we see a lot of project managers

427
00:29:28,480 --> 00:29:29,880
wanted to do very regularly.

428
00:29:29,880 --> 00:29:33,280
I think we would make them happy if they could do that.

429
00:29:33,280 --> 00:29:38,320
And yeah, your expertise also include the Azure integrations, what will do as a play

430
00:29:38,320 --> 00:29:41,760
and a modern project operation solution?

431
00:29:41,760 --> 00:29:46,120
So very often if we are doing more complex kind of integrations, more complex things involving

432
00:29:46,120 --> 00:29:50,920
the schedule API where we need to go and perhaps create a whole bunch of project tasks

433
00:29:50,920 --> 00:29:55,520
or resource assignments and things like that, then what we can do is we can offload that processing

434
00:29:55,520 --> 00:29:56,880
into Azure.

435
00:29:56,880 --> 00:29:59,520
We can have, for example, Azure Wear plug-ins.

436
00:29:59,520 --> 00:30:04,080
We can tap into Azure Service Bus for a synchronous sort of processing and then from there go

437
00:30:04,080 --> 00:30:09,480
and have that sort of scale there to be able to handle those more complex integrations.

438
00:30:09,480 --> 00:30:13,000
As well, if we're typically, we've done this for a few projects, if we're integrating

439
00:30:13,000 --> 00:30:17,840
with external ERP systems, then again, Azure allows us to build out the patterns and the

440
00:30:17,840 --> 00:30:22,240
frameworks to be able to handle those sort of integrations, be able to process them, be

441
00:30:22,240 --> 00:30:26,360
able to scale them accordingly, and also as well to be able to ensure that we've got that

442
00:30:26,360 --> 00:30:29,040
traceability for every change that we're doing.

443
00:30:29,040 --> 00:30:33,680
We can ensure it's processed in your first in first out type of order.

444
00:30:33,680 --> 00:30:37,360
Again, using Service Bus and other tools to handle that.

445
00:30:37,360 --> 00:30:43,480
And how do you balance our customizations with maintaining a supportable and scalable

446
00:30:43,480 --> 00:30:44,480
architecture?

447
00:30:44,480 --> 00:30:48,560
Yeah, sometimes you do have to push back.

448
00:30:48,560 --> 00:30:54,040
Try and make sure that we can fit the process around the sort of system as much as possible.

449
00:30:54,040 --> 00:31:01,240
And where necessary deviate away and use supported customizations only, so use Power Platform.

450
00:31:01,240 --> 00:31:05,280
Don't be writing custom code, don't be writing plug-ins too often.

451
00:31:05,280 --> 00:31:07,680
You don't be using JavaScript and things like that.

452
00:31:07,680 --> 00:31:12,600
Use the supported accessibility points within the Power Platform, the ability to customize

453
00:31:12,600 --> 00:31:14,880
forms and views and stuff like that.

454
00:31:14,880 --> 00:31:17,360
And that would just mean that we have an easier road.

455
00:31:17,360 --> 00:31:20,920
And as well as solution would just become a lot more easily maintainable as well for the

456
00:31:20,920 --> 00:31:23,920
end customer, which is going to help with adoption.

457
00:31:23,920 --> 00:31:31,360
Yeah, what are the trends in Dynamics 365 and Business Application?

458
00:31:31,360 --> 00:31:35,760
Yeah, we should prepare for now.

459
00:31:35,760 --> 00:31:40,440
Really interesting sort of place at the moment because, you know, anybody who's got GitHub

460
00:31:40,440 --> 00:31:44,920
code pilot could go spend a weekend and they could go and vibe code themselves their own

461
00:31:44,920 --> 00:31:46,240
sort of CRM sort of system.

462
00:31:46,240 --> 00:31:48,680
You know, it's possible today with the technology to kind of do that.

463
00:31:48,680 --> 00:31:52,040
So then the obvious question from there kind of made us, okay, well, why do we still need

464
00:31:52,040 --> 00:31:53,040
SAS?

465
00:31:53,040 --> 00:31:54,720
You know, is SAS dead?

466
00:31:54,720 --> 00:32:00,240
Some people keep claiming as part of that, you know, when we can just build our own apps,

467
00:32:00,240 --> 00:32:03,520
our own sort of things that we can then sort of run from there.

468
00:32:03,520 --> 00:32:08,440
I still think that, you know, although we can do a lot in terms of building our own bespoke

469
00:32:08,440 --> 00:32:12,400
apps and things like that, you know, there is still, you know, potentially huge gaps there,

470
00:32:12,400 --> 00:32:17,880
gaps there for things like security gaps there in terms of, okay, how is the app actually scalable,

471
00:32:17,880 --> 00:32:20,320
is it able to support all of that?

472
00:32:20,320 --> 00:32:24,720
So very much think that, you know, there's still going to be a place for having, you know,

473
00:32:24,720 --> 00:32:29,400
a platform that's going to give you all of that, you know, so potential future I could

474
00:32:29,400 --> 00:32:34,480
foresee is, you know, okay, well, you know, you can vibe code your apps, but then you're

475
00:32:34,480 --> 00:32:39,600
using the Microsoft sort of offering and solution to basically host that and Microsoft

476
00:32:39,600 --> 00:32:44,680
then provides you with the ability with coverage, you know, they'll make sure that thing that

477
00:32:44,680 --> 00:32:49,120
secure authentication is in place, they'll make sure that maybe any smells, any problems

478
00:32:49,120 --> 00:32:53,680
with your code are kind of fixed, you know, it closed any sort of security, you know, that

479
00:32:53,680 --> 00:32:58,320
could be potentially a future that we could see with this sort of platform, certainly

480
00:32:58,320 --> 00:33:02,200
it's based on whether technology is looking, how the technology is looking today and where

481
00:33:02,200 --> 00:33:04,200
the future could be?

482
00:33:04,200 --> 00:33:10,800
But when the company will start their journey in project operations, what is the first

483
00:33:10,800 --> 00:33:13,960
recommendation you can give them?

484
00:33:13,960 --> 00:33:19,800
First recommendation is to look at the app, the box process, focus on that as much as possible,

485
00:33:19,800 --> 00:33:25,320
see how we can align towards that as much as sort of possible and sort of, you know, prepare

486
00:33:25,320 --> 00:33:31,160
yourself to, you know, to keep things as simple as straightforward as possible, you know, as

487
00:33:31,160 --> 00:33:35,480
if any of these sort of, you know, SaaS sort of products, the more we can deviate away from

488
00:33:35,480 --> 00:33:39,640
the standard functionality, the more potential challenges and risks that we may see in the project

489
00:33:39,640 --> 00:33:40,640
itself.

490
00:33:40,640 --> 00:33:44,600
So just try and make sure we can align to what is there as much as possible and deviate

491
00:33:44,600 --> 00:33:49,440
away only if there's a good business reason, business justification for doing so.

492
00:33:49,440 --> 00:33:55,440
And I think when we think about AI, there are a lot of company, they, yeah, they don't see

493
00:33:55,440 --> 00:34:05,360
the real outcomes of AI, how can we measure the outcomes from AI or what the RKBI is

494
00:34:05,360 --> 00:34:08,160
or how can we measure it?

495
00:34:08,160 --> 00:34:12,880
It's going to be driven by probably, you know, cost saving, time saving, you know, usually

496
00:34:12,880 --> 00:34:18,080
there's a distinction between OK, the amount of money we save, the amount of time we save,

497
00:34:18,080 --> 00:34:20,080
our target time is money.

498
00:34:20,080 --> 00:34:24,040
So, you know, having that sort of fair comparison there, if we can demonstrate technologies

499
00:34:24,040 --> 00:34:30,360
made up huge impact from a time saving standpoint, if we can show that the technology has allowed

500
00:34:30,360 --> 00:34:35,920
us to process more work, you know, handle more caseload, deliver our projects more on time,

501
00:34:35,920 --> 00:34:39,960
more on budget, things like that, you know, these are kind of the, the sweet spot metrics

502
00:34:39,960 --> 00:34:43,840
that we want to be sort of looking towards, you know, how can we, how is the technology

503
00:34:43,840 --> 00:34:51,000
helped us to improve our delivery of a certain sort of function and how is that then resulted

504
00:34:51,000 --> 00:34:55,080
in, you know, more positive experience for even the businesses or for the customers that

505
00:34:55,080 --> 00:34:56,800
were sort of working with?

506
00:34:56,800 --> 00:35:05,640
Yeah, we have also, I think the co-pilot, but that's also, as I foundry, what role plays

507
00:35:05,640 --> 00:35:10,280
the as I foundry in, in, in, in, in integration?

508
00:35:10,280 --> 00:35:15,440
So, Microsoft foundry, that would be probably for scenarios where OK, you need to have more

509
00:35:15,440 --> 00:35:20,080
control, maybe you're taking more of a pro code sort of routes for our purposes, you know,

510
00:35:20,080 --> 00:35:25,440
if you are maybe an ISV independent software vendor, you wanted to build agents that you

511
00:35:25,440 --> 00:35:29,720
want to then sort of make available to end customers, then if for me, foundry is probably

512
00:35:29,720 --> 00:35:32,160
the option that you want to be considering as part of that.

513
00:35:32,160 --> 00:35:36,800
So, we're doing a lot of investigations into that at the moment in terms of OK, how we

514
00:35:36,800 --> 00:35:41,040
can potentially leverage users' technology, it will be maybe kind of a sort of watch this

515
00:35:41,040 --> 00:35:45,960
space around all this, but certainly with foundry, you get a lot in terms of your additional

516
00:35:45,960 --> 00:35:51,040
capability, the ability to really tailor your agent experience, I think as well, the ability

517
00:35:51,040 --> 00:35:56,040
to, you know, use the model that's best for your particular scenario, you know, so it may

518
00:35:56,040 --> 00:36:00,600
be that OK, the opening eye models are not good, not sufficient for what you need, maybe

519
00:36:00,600 --> 00:36:04,040
there's a specific, you know, a throttbit model, there's a specific, maybe deep seek or

520
00:36:04,040 --> 00:36:06,680
grock model that's going to be more preferable for you.

521
00:36:06,680 --> 00:36:10,720
And as well in the foundry side, you can start to do things like maybe fine tuning the model

522
00:36:10,720 --> 00:36:14,320
as well, train it on your own business data, and therefore it's then going to be a lot

523
00:36:14,320 --> 00:36:17,520
more valuable, you can then reduce your token costs and stuff like that.

524
00:36:17,520 --> 00:36:22,240
So those are some of the advantages that I see that foundry bringing to the equation.

525
00:36:22,240 --> 00:36:31,120
And how organizations combine dynamics, project operations with fabric, data wells and

526
00:36:31,120 --> 00:36:36,480
Azure, did you think it will be an only fine solution in the future?

527
00:36:36,480 --> 00:36:37,480
I think so.

528
00:36:37,480 --> 00:36:40,040
And that's again, indeed, the advantage of relying for Microsoft standpoint because we

529
00:36:40,040 --> 00:36:44,680
can very easy, for example, can figure fabric thing from our data, the environment and then

530
00:36:44,680 --> 00:36:50,640
get that data out into fabric, fabric then becomes kind of our principle and central knowledge

531
00:36:50,640 --> 00:36:55,640
source for everything to do in the organization and can then be used by any agents that we

532
00:36:55,640 --> 00:37:01,920
create in order to be able to sort of answer questions about the organization itself.

533
00:37:01,920 --> 00:37:07,880
So certainly, you know, if you're thinking about how to adopt AI, well, it just requires

534
00:37:07,880 --> 00:37:12,640
maybe to take a bit of a step back, sort of say, okay, well, you know, maybe we need to first

535
00:37:12,640 --> 00:37:17,000
implement fabric, maybe we need to first make sure we're implementing power platform,

536
00:37:17,000 --> 00:37:20,960
well, you know, look at all the different core elements, foundational elements, they're

537
00:37:20,960 --> 00:37:22,680
going to be successful.

538
00:37:22,680 --> 00:37:26,320
And then from there, once they're in place, you can then sort of proceed and move forward

539
00:37:26,320 --> 00:37:31,280
and really deliver and start building these agente experiences with the best possible

540
00:37:31,280 --> 00:37:34,880
chance of success.

541
00:37:34,880 --> 00:37:47,600
And then, yeah, what did you think, how accurate, actually, a algorithm, yeah, tools around Microsoft,

542
00:37:47,600 --> 00:37:54,640
are they really enterprise ready or is it more, I say, gamey vacation?

543
00:37:54,640 --> 00:37:55,640
I think it's getting there.

544
00:37:55,640 --> 00:37:59,040
I think, you know, in terms of when we're looking at all the events at the moment, I think

545
00:37:59,040 --> 00:38:02,560
certainly Microsoft is, is I think head of the game there in terms of the art thinking

546
00:38:02,560 --> 00:38:07,400
about all this stuff and they are providing the tools to help support us as part of this,

547
00:38:07,400 --> 00:38:10,840
you know, whether it's your things like the responsible AI principles, whether it's the

548
00:38:10,840 --> 00:38:16,000
co-part of control system, agent 365, which is now currently in G.A., you know, they consistently

549
00:38:16,000 --> 00:38:20,440
thinking about, okay, what can we do from a technology standpoint to ensure that we can,

550
00:38:20,440 --> 00:38:25,360
you know, you know, and so the enterprises can sort of move forward, they can adopt this

551
00:38:25,360 --> 00:38:30,280
technology, you know, in at the pace that's going to suit them and that we've got all the

552
00:38:30,280 --> 00:38:34,240
appropriate protections to ensure that, okay, we can manage things like, you know, potential

553
00:38:34,240 --> 00:38:38,520
jail breaking of agents, we can handle risks around maybe data security and all this sort

554
00:38:38,520 --> 00:38:39,520
of good stuff.

555
00:38:39,520 --> 00:38:43,720
I think consistently, Microsoft are, you know, are always thinking in those sort of terms

556
00:38:43,720 --> 00:38:48,560
and providing the broad framework and the broad tools to help address those challenges.

557
00:38:48,560 --> 00:38:49,560
Yeah.

558
00:38:49,560 --> 00:38:50,560
Okay.

559
00:38:50,560 --> 00:38:52,960
Let's jump in the quick fire round.

560
00:38:52,960 --> 00:38:59,960
So I asked you, yeah, I give the question and you, yeah, you'll give what we're going

561
00:38:59,960 --> 00:39:03,400
on what comes on your mind.

562
00:39:03,400 --> 00:39:08,560
So what's the most underrated Dynamics 365 feature?

563
00:39:08,560 --> 00:39:16,240
Oh, most of the research that I feature, I would say business rules, I love business rules,

564
00:39:16,240 --> 00:39:18,880
means we have to record some code.

565
00:39:18,880 --> 00:39:24,760
What was your most exciting Microsoft announcement in the last 12 months?

566
00:39:24,760 --> 00:39:35,960
What was exciting Microsoft announcement?

567
00:39:35,960 --> 00:39:42,480
Which Microsoft product will survive longest on the zombie apocalypse?

568
00:39:42,480 --> 00:39:45,200
Probably Microsoft paint.

569
00:39:45,200 --> 00:39:46,200
Okay.

570
00:39:46,200 --> 00:39:47,200
Yeah.

571
00:39:47,200 --> 00:39:50,200
Coffee tea or energy drinks during implementation?

572
00:39:50,200 --> 00:39:51,200
Oh, tea.

573
00:39:51,200 --> 00:39:52,200
Tea.

574
00:39:52,200 --> 00:39:53,200
I'm from the UK.

575
00:39:53,200 --> 00:39:58,280
Tea, milk, no sugar, and then that'll get you free tea in the day.

576
00:39:58,280 --> 00:39:59,280
Okay.

577
00:39:59,280 --> 00:40:07,600
What was the do you think helped you more in your career, the MVP status only in the city?

578
00:40:07,600 --> 00:40:13,760
I would say being an MVP for sure based on the opportunities that's given me.

579
00:40:13,760 --> 00:40:21,840
And yeah, if you will start a new startup, what, what do you do?

580
00:40:21,840 --> 00:40:28,800
It would probably be focused around AI adoption, advisory, and how we can sort of, as I mentioned,

581
00:40:28,800 --> 00:40:32,640
best set the foundations for success here.

582
00:40:32,640 --> 00:40:39,560
Architech, draw the other grums or documentation?

583
00:40:39,560 --> 00:40:45,760
Documentation, I do like a good, thank you for your documentation.

584
00:40:45,760 --> 00:40:47,240
What, what, what, what did you think?

585
00:40:47,240 --> 00:40:52,600
What's longer than the dynamic implementation or a Marvel movie, Marlton?

586
00:40:52,600 --> 00:40:54,080
Oh, oh, good.

587
00:40:54,080 --> 00:40:56,600
Well, there's quite a lot of Marvel movies now.

588
00:40:56,600 --> 00:40:57,960
I probably have to say the Marvel one.

589
00:40:57,960 --> 00:40:58,960
There's so many now.

590
00:40:58,960 --> 00:40:59,960
Yeah.

591
00:40:59,960 --> 00:41:05,640
So if you were to take what career will you have to choose?

592
00:41:05,640 --> 00:41:10,440
I would probably be one of those guys that you see doing like history walking tours in

593
00:41:10,440 --> 00:41:13,040
like York, or London in a costume.

594
00:41:13,040 --> 00:41:17,200
So maybe, maybe, maybe, maybe that's what I do when I retire.

595
00:41:17,200 --> 00:41:18,640
Yeah.

596
00:41:18,640 --> 00:41:24,080
And what's your, yeah, I say go to productivity hack?

597
00:41:24,080 --> 00:41:26,520
Go to productivity hack.

598
00:41:26,520 --> 00:41:34,360
I really like, I put my headphones on and I usually get a podcast or some music on and

599
00:41:34,360 --> 00:41:37,240
that gets me really focused.

600
00:41:37,240 --> 00:41:40,960
And yeah, what, what's higher?

601
00:41:40,960 --> 00:41:45,400
Stakeholder management or technical architecture?

602
00:41:45,400 --> 00:41:50,960
Stakeholder management for sure, making sure people on the train with you.

603
00:41:50,960 --> 00:41:55,920
What's the full thing when you do a start a new project?

604
00:41:55,920 --> 00:42:01,200
First thing I do, yeah, make sure, have an aspect, introduce everyone and yeah, share some

605
00:42:01,200 --> 00:42:05,240
from facts, get the team, get the team on the same page.

606
00:42:05,240 --> 00:42:08,440
And yeah, really sort of excited to do the project.

607
00:42:08,440 --> 00:42:09,440
Awesome.

608
00:42:09,440 --> 00:42:10,440
Yeah, thank you.

609
00:42:10,440 --> 00:42:12,880
This was, yeah, this was, I really enjoyed it.

610
00:42:12,880 --> 00:42:14,200
This was really fun.

611
00:42:14,200 --> 00:42:20,400
Yeah, and yeah, for me, it's a, it's a complete new tool, the project operation.

612
00:42:20,400 --> 00:42:26,040
So yeah, I say, yeah, thank you, Joe, for, for joining me today and sharing your insights

613
00:42:26,040 --> 00:42:32,000
on Dynamics 365 project operations, Regretion, Stagebreeze, Azure in, and yeah, integrations

614
00:42:32,000 --> 00:42:34,400
and the future of AI project delivery.

615
00:42:34,400 --> 00:42:41,600
Yeah, I think, yeah, if listeners want to learn more about Joe or pro MX or Dynamics 365

616
00:42:41,600 --> 00:42:47,280
operations, they can look into the show notes and see all your links.

617
00:42:47,280 --> 00:42:54,760
And yeah, yeah, so until next time, keep learning, keep building and keep exploring what

618
00:42:54,760 --> 00:42:56,160
possible was Microsoft technology.

619
00:42:56,160 --> 00:42:58,360
So thank you for, for being here.

620
00:42:58,360 --> 00:43:00,400
Yeah, always thanks, we go.

621
00:43:00,400 --> 00:43:01,400
Appreciate it.

622
00:43:01,400 --> 00:43:02,400
Thank you.

623
00:43:02,400 --> 00:43:03,400
Okay, goodbye.

624
00:43:03,400 --> 00:43:04,400
Ciao.

625
00:43:04,400 --> 00:43:05,400
Ciao.

626
00:43:05,400 --> 00:43:06,400
Bye.