Role of Industry Catalogs

This article discusses the role of Industry Catalogs in the Prescriptive Delivery methodology. It outlines the key components of the Industry Catalogs, including SOW templates and attachments, Prescriptive Design Requirements, User Stories with acceptance criteria, and an Estimation Guide.

The key component of Prescriptive Delivery methodology will be the use of the Pricefx Industry Catalogs as a tool to help implementation teams to become more prescriptive.

Contents of Prescriptive Delivery Industry Catalogs

There are four main sections of the Prescriptive Delivery Industry Catalogs; SOW template and attachments, Prescriptive Design Requirements , User Stories with acceptance criteria, and the Estimation Guide. The first three will be delivered to our customers (or partners) while the last document is used for scoping. Each of these sections, for each use case in the catalog, are documented and packaged together.

SOW Templates and Attachments

Each Prescriptive Delivery Industry Catalog contains a single SOW (Statement of Work) template. This template outlines the general scope, governance criteria, and rate information, typically included as Exhibit B in the Order Form.

Additionally, each use case within the catalog has a dedicated attachment to the SOW template, detailing the specific activities and deliverables associated with that particular use case. This modular approach enables the swift and flexible construction of the SOW.

Prescriptive Design Requirements (PDR)

Each use case within the Prescriptive Delivery Industry Catalog is accompanied by a dedicated prescriptive design requirement document. This document outlines the recommended approach for configuring the platform to address the specific business problem.

It includes a comprehensive business description as well as a set of detailed requirements detailing how to configure the platform, including the necessary platform modules and data types required for successful implementation.

User Stories and Acceptance Criteria

For each use case, there is a set of User Stories that help the customer gain a comprehensive understanding of the proposed solution. These use cases are documented using standard agile product management formats. Furthermore, each user story defines the corresponding acceptance criteria, which are then leveraged during sprint testing to assess the success of the platform configuration.

Estimation Guide

For each use case, there is a dedicated estimation guide that outlines the assumptions made during the standard scoping process. Additionally, this guide includes a set of questions to be asked during the "Scope Validation and Project Readiness Workshop." These questions help determine the appropriate configuration level - high, medium, or low - for that specific use case and customer. The estimation guide ultimately aids in estimating the number of person-days required for that particular use case and customer.