2020-04-21 Institutional Adoption Group Meeting Agenda/Minutes

Jane Shellum

@Sean Muir

@Lorraine Constable

Traci Bernardi

Lee Wise

Bill Curtis

Beth Meyers

@Ken Rubin

Denis Gagne

Sree Vaddi

Joey Wang

Linda Chan

Edwin Butterworth

Michael Cesino

Bruce Bray

Atlassian Overview

Sean Muir

Sean Muir provided the work group with an overview of the new work space on the logica/BPMPLUS site:

• Landing page (note - meeting schedule needs more detail than “biweekly”

• Wiki page - Sean provided a starter outline that can be adjusted as needed. He demonstrated the ability to add child pages and link them to the wiki. This space is meant to be a working space, with the “nitty gritty” detail. the page will contain links to the Maturity Model and to the Playbook.

• Minutes page - we will use the minutes template going forward; historical minutes will be uploaded.

The site allows for anonymous users, but Sean will also help to create a group that has authorization to add and edit content. Sree Vadi has experience with Atlassian and offered to help with the site. Traci will send out the link to the work group. Call attendees who are not currently on the list for the workgroup were reminded to visit the OMG BPM+ website to sign up :https://www.bpm-plus.org/working-groups/index.htm#adoption

Work Product Discussion

Jane Shellum

The work group has two products in development. In order to keep momentum on the work, work group members were asked to volunteer to draft sections and bring them back for discussion. In the course of reviewing the products, the following observations were made:

1. The title of the “Capability Maturity Model” is potentially misleading. This model addresses business capabilities broadly, where other well-known capability maturity models scope the meaning of “capability” to mean technical capabilities. A better title is needed to convey the scope of an organization’s ability to adopt computable practice guidelines.

2. Before selecting use cases to include in the playbook, the workgroup needs to better define the characteristics of a good use case, for example, a topic that is applicable to multiple organizations, a topic on which discrepencies exist between organizations, a topic in which there are known quality issues, etc. The group suggested that rather than COVID/non-COVID use cases, a better distinction might be between high-stress situations (necessitating rapid adoption) and low-stress situations such adoption of processes related to published quality measures. Trisotech has a library of COVID-related models and other models that could be candidate use cases. They are available at Trisotech.com/covid-19 or cds.trisotech.com.

3. The main section of the playbook is the process for adopting computable practice guidelines. This content will need to address two distinct axes: The “level” of adoption (documentation/conceptual/platform independent/platform dependent) and the transition between the current maturity level and the desired maturity level.

4. Future work for the team: monitoring and evaluating how the work products are used in practice

Homework Assignments

Jane Shellum