Work item types for deliverables and workshops (#605)

Author: edupont04

guidance/TOC.yml

@@ -369,10 +369,16 @@ items:
                     href: business-processes/about-import-catalog-devops.md
                   - name: Work item types in Azure DevOps
                     href: business-processes/about-import-catalog-devops-process-work-item-types.md
-                  - name: Manage updates to the catalog in Azure DevOps
-                    href: business-processes/about-import-catalog-devops-updates.md
+                  - name: Deliverables work item types in Azure DevOps
+                    href: business-processes/about-devops-work-items-deliverables.md
                   - name: Other work items types in the template
                     href: business-processes/about-devops-work-items-other.md
+                  - name: Workshop work item type in Azure DevOps
+                    href: business-processes/about-import-catalog-devops-workshop-work-item-type.md
+                  - name: Manage updates to the catalog in Azure DevOps
+                    href: business-processes/about-import-catalog-devops-updates.md
+                  - name: Reference for fields on work items
+                    href: business-processes/about-devops-work-items-deliverables-fields.md
               - name: Import the catalog to Mavim
                 items:
                   - name: Import the catalog to Mavim overview
@@ -397,6 +403,8 @@ items:
                     href: implementation-guide/process-focused-solution-define-requirements.md
               - name: Learn about process maturity
                 href: business-processes/process-maturity-introduction.md
+              - name: Use the catalog to drive workshops
+                href: business-processes/about-workshops.md
               - name: Standardize business processes during an implementation
                 href: business-processes/standardize-business-processes.md
               - name: Map departments and business processes

guidance/business-processes/about-catalog-levels.md

@@ -4,7 +4,7 @@ description: Dive into the structured hierarchy of the business process catalog,
 author: edupont04
 ms.author: edupont
 ms.reviewer: edupont
-ms.date: 12/10/2025
+ms.date: 01/12/2026
 ms.topic: concept-article
 ---
 
@@ -32,13 +32,13 @@ The following list provides a few examples of this level of the business process
 
 The following table outlines key properties of an end-to-end process.
 
-|Property|Description  |
-|---------|---------|
-|Comprehensive  |An end-to-end process covers the entire lifecycle of a business operation.|
-|Cross-functional |An end-to-end process involves multiple departments or functions.|
-|Outcome-oriented |An end-to-end process focuses on delivering a specific business outcome.|
+| Property | Description |
+| --------- | --------- |
+| Comprehensive | An end-to-end process covers the entire lifecycle of a business operation. |
+| Cross-functional | An end-to-end process involves multiple departments or functions. |
+| Outcome-oriented | An end-to-end process focuses on delivering a specific business outcome. |
 
-## What an end-to-end process isn't
+### What an end-to-end process isn't
 
 The following list outlines what an end-to-end process isn't.
 

guidance/business-processes/about-devops-work-items-deliverables-fields.md

@@ -4,7 +4,7 @@ description: Discover how the Azure DevOps template supports structured project
 author: edupont04
 ms.author: edupont
 ms.reviewer: edupont
-ms.date: 12/19/2025
+ms.date: 01/07/2026
 ms.topic: concept-article
 ---
 
@@ -423,16 +423,16 @@ Here's an example of a status report: *Steering committee status report*
 
 The following fields are recommended for the **Status Report** work item type and included by default in the Azure DevOps template for the business process catalog:
 
-|Name  |Description  |
-|---------|---------|
-|Title| Display name of the status report, such as *Week 47 Status Report*.|
-|Reporting Period|Start and end dates.|
-|Summary| Narrative of progress and outlook.|
-|KPIs| Quantitative indicators (% completion, defect counts).|
-|Risks / Issues / Decisions|Highlights by category.|
-|Next Steps| Planned actions for upcoming period.|
-|Status| Current state (Draft, Published, Archived).|
-|Tags| Labels for capability, phase, priority classification.|
+| Name | Description |
+| -- | -- |
+| Title | Display name of the status report, such as *Week 47 Status Report*. |
+| Reporting Period | Start and end dates. |
+| Summary | Narrative of progress and outlook. |
+| KPIs | Quantitative indicators (% completion, defect counts). |
+| Risks / Issues / Decisions | Highlights by category. |
+| Next Steps | Planned actions for upcoming period. |
+| Status | Current state (Draft, Published, Archived). |
+| Tags | Labels for capability, phase, priority classification. |
 
 When users create new work items based on this work item type, recommend that they also take the following steps:
 

guidance/business-processes/about-devops-work-items-deliverables.md

@@ -4,7 +4,7 @@ description: Track your implementation of business process scenarios in your Dyn
 author: edupont04
 ms.author: edupont
 ms.topic: concept-article 
-ms.date: 12/10/2025
+ms.date: 01/12/2026
 ms.custom:
   - ai-gen-docs-bap
   - ai-gen-description
@@ -27,23 +27,23 @@ Learn more at [Overview of the business process catalog levels](about-catalog-le
 
 The tree is organized into six levels with increasing granularity:
 
-- **Level 1 – end-to-end processes:** Broad business capabilities such as [Order to Cash](order-to-cash-overview.md) or [Source to Pay](source-to-pay-overview.md).
+- **Level 1 – end-to-end processes**: Broad business capabilities such as [Order to Cash](order-to-cash-overview.md) or [Source to Pay](source-to-pay-overview.md).
 
-- **Level 2 – process areas:** Logical groupings within an end-to-end process, such as*Manage Sales Orders*.
+- **Level 2 – process areas**: Logical groupings within an end-to-end process, such as [Manage accounts payable](source-to-pay-manage-accounts-payable-overview.md).
 
-- **Level 3 – business processes:** Specific functions that describe what the business does, system-agnostic and reusable across industries.
+- **Level 3 – business processes**: Specific functions that describe what the business does, system-agnostic and reusable across industries, such as [Process supplier rebates and incentives](source-to-pay-process-vendor-rebates-incentives-overview.md).
 
-- **Level 4 – scenarios or patterns:** Variations of processes for different industries or solution approaches.
+- **Level 4 – scenarios or patterns**: Variations of processes for different industries or solution approaches, such as *Manage supplier prepayments in Dynamics 365 Finance* or *Create a prepayment on a purchase order in Dynamics 365 Business Central*.
 
-- **Level 5 – system processes:** Detailed steps tied to specific forms or pages in Dynamics 365.
+- **Level 5 – system processes**: Detailed steps tied to specific forms or pages in Dynamics 365, such as *Create vendor prepayment using payment journal* for the steps in Dynamics 365 Finance or *Create prepayment invoices* for the steps in Dynamics 365 Business Central.
 
-- **Level 6 – test cases:** Actions for validating functionality during testing phases.
+- **Level 6 – test cases**: Actions for validating functionality during testing phases.
 
 This layered structure ensures that projects can start at a high level and drill down to detailed, actionable items as needed. Learn more at [Overview of the business process catalog levels](about-catalog-levels.md).  
 
 ## Using the tree in Azure DevOps
 
-In Azure DevOps, you implement the catalog tree through custom work item types that mirror these levels. Each level corresponds to a work item type, such as **end-to-end**, **Process Area**, **Business Process**, and **Scenario**, and links hierarchically to maintain traceability. This structure enables teams to manage scope, track progress, and align deliverables with business objectives. By importing the catalog into Azure DevOps, your organization gains a standardized framework for planning, fit/gap analysis, and execution. It also supports integration with testing tools like RSAT, ensuring that processes documented in the tree flow seamlessly into test cases and quality assurance activities.
+In Azure DevOps, you implement the catalog tree through custom work item types that mirror these levels. Each level corresponds to a work item type, such as **End to end**, **Process Area**, **Business Process**, and **Scenario**, and links hierarchically to maintain traceability. This structure enables teams to manage scope, track progress, and align deliverables with business objectives. By importing the catalog into Azure DevOps, your organization gains a standardized framework for planning, fit/gap analysis, and execution. It also supports integration with testing tools like RSAT, ensuring that processes documented in the tree flow seamlessly into test cases and quality assurance activities.
 
 One of the primary functions of this tree is to define project scope. By mapping all business processes and their variations into a structured hierarchy, the catalog provides a clear view of what is in scope for the implementation. This view helps stakeholders agree on boundaries early in the project, reduces ambiguity, and ensures that any gaps or enhancements are identified and managed systematically. Scope definition at this level also supports governance and change control, as you can trace any additions or modifications back to specific processes and their related work items.
 

guidance/business-processes/about-devops-work-items-other.md

@@ -4,7 +4,7 @@ description: Track the work needed for workshops in your Dynamics 365 implementa
 author: edupont04
 ms.author: edupont
 ms.topic: concept-article
-ms.date: 06/11/2025
+ms.date: 01/07/2026
 ms.custom:
   - ai-gen-docs-bap
   - ai-gen-description
@@ -61,4 +61,5 @@ Find the related articles here:
 
 - [Use the business process catalog as a template in Azure DevOps Services](about-import-catalog-devops.md)  
 - [Custom work item type for processes in the Dynamics 365 business process catalog](about-import-catalog-devops-process-work-item-types.md)  
-- [Custom work item type for configuration deliverables in the Dynamics 365 business process catalog](about-import-catalog-devops-configuration-deliverable-work-item-type.md)
+- [Custom work item type for configuration deliverables in the Dynamics 365 business process catalog](about-import-catalog-devops-configuration-deliverable-work-item-type.md)  
+- [Workshop preparation for Dynamics 365 implementation projects](about-workshops.md)  

guidance/business-processes/about-import-catalog-devops-process-work-item-types.md

@@ -4,7 +4,7 @@ description: What's new or changed in the December 2025 version of the business
 author: edupont04
 ms.author: edupont
 ms.reviewer: edupont
-ms.date: 12/09/2025
+ms.date: 01/07/2026
 ms.topic: concept-article
 ---
 
@@ -131,12 +131,14 @@ This release adds a dedicated **Jobs** work item type to the Deliverables tree,
 > [!NOTE]
 > These entries represent jobs in finance and operations apps, such as [batch jobs](/dynamics365/fin-ops-core/dev-itpro/sysadmin/batch-processing-overview) or [scheduled tasks](/dynamics365/supply-chain/production-control/job-scheduling). They don't represent jobs in Dynamics 365 Business Central that are now [projects](/dynamics365/business-central/projects-manage-projects).
 
-
 ## Updated Business Central scenarios
 
 We removed erroneous descriptions for 35 Business Central scenarios in *Project to Profit*. We also updated five Business Central-related scenarios that had mismatched values in the **Process Sequence ID** field. Thank you, Marcin, for submitting these issues and collaborating to ensure the catalog is accurate.
 
 ## Related information
 
+- [Overview of the business process catalog levels](about-catalog-levels.md)  
+- [Other work item types in the business process catalog](about-devops-work-items-other.md)  
+- [Workshop preparation for Dynamics 365 implementation projects](about-workshops.md)  
 - [What's new or changed in the business process catalog](about-whats-new.md)  
 - [About the business process catalog for Dynamics 365 apps and services](about.md)