Summary
Dynamics 365 implementations often struggle with unclear scope, limited traceability, and misalignment between business processes and delivery work. In this session, Rachel Profitt explains the Microsoft Business Process Catalog, including new process levels, deliverables, Azure DevOps structures, and APQC mapping. Viewers gain a structured, standards‑based foundation to align objectives, processes, and delivery artifacts across Dynamics 365 projects.
Speakers
Rachel ProfittPrincipal Program Manager, Microsoft
video Chapters
01:53
Why the Microsoft Business Process Catalog exists and what it contains
07:19
Business Process structure and new process levels
11:53
Deliverables tree and Azure work items types
18:02
Objectives and delivery planning in Success by Design
In partnership with 
Processes documented, not executable
Traditional Dynamics 365 projects rely on static documentation and disconnected process lists. Teams understand high‑level processes, but struggle to translate them into concrete configurations, workflows, and test cases. This gap leads to manual effort, unclear scope, and limited traceability between business intent and delivery work inside Azure DevOps.
Implementation Complexity Keeps Increasing
Dynamics 365 continues to expand with new features, agents, and system processes. The Business Process Catalog reflects this by adding hundreds of scenarios, system processes, and test cases. Without a structured process and delivery model, teams are forced to manage growing complexity using spreadsheets and custom work breakdowns.
From process thinking to delivery alignment
The Business Process Catalog introduces a structured hierarchy that connects business processes, deliverables, objectives, and delivery plans. Processes explain why work exists, deliverables define what must be built, and delivery plans organize when and how work is executed. This model replaces fragmented planning with consistent alignment across teams.
Depth, structure, and traceability at scale
The Business Process Catalog provides a standardized structure that spans end‑to‑end business processes, detailed scenarios, flow diagrams, and implementation deliverables. Processes are organized across multiple levels and mapped to recognized standards such as APQC, supporting consistent comparison and governance.