Builder Scrum

A biweekly "Builder Scrum" provides Builders with opportunities to discover areas where they can contribute and to report on any tasks already assigned. 

• Self scheduling for Scrum sessions on Tuesday afternoons is facilitated via Clinical Builder Committee Calendar.

Objectives

As the most frequent and familiar Builder forum, the Scrum gives opportunity for key Connect Care Builder Program objectives to be addressed:

• Facilitate Collaborative Build
  Builders, Analysts, Clinical Informaticians and Design leads are all represented at Builder Scrum in order to seek opportunities for Builders to partner with other experts in solving complex design and build problems.

• Synchronize Accountable Build
  By bringing visibility to significant build projects, unhelpful duplication of effort is avoiding and related build projects can share build objects, taxonomies and user interface functions to promote a more unified experience for end-users. Scrums ensure visibility and transparency for build assignments, while cycling back to assure accountability for outcomes.

• Promote Nimble Build
  Rapid communication of challenges, innovations and new solutions in Scrums can help multiple build projects advance in parallel, iteratively optimizing for a better user experience. The Scrum promotes just-in-time identification of the Builders, Knowledge Leads and Analysts best able to tackle a new build challenge.

• Support a growing Builder Community
  An open exchange of ideas can promote teamwork, foster creativity, engage new builders and empower continuing builder development.

Participants

Builder Scrum invitees include:

• Prescriber and Clinician Builders

• IT Application Leads (or delegates) for clinical documentation, orders and ambulatory teams

• Clinical System Design directors (or delegates) 

Topics

Scrums operate in an informal, task and action-oriented fashion. Design and development requests are pre-triaged within the JIRA task management system, then brought forward for review in the Scrum. As new and ongoing tasks are reviewed, Builders connect with Analysis and other resources to tackle specific tasks. Clinical System Design leads come prepared to provide or facilitate access to relevant clinical content and use cases. IT analysts come prepared with guidance about system impacts and build considerations.

Triage

The Connect Care Team maintains a list of design and enhancement requests. These are gathered from ServiceNow (help desk) tickets, Area Council requests, new Epic capabilities, and Connect Care governance. Items are reviewed and characterized at a high level to determine complexity and feasibility and to estimate the amount of effort required for a solution. Items require prioritization and approval from appropriate Connect Care committees and/or councils before proceeding with development. Ultimately, this 'ticket history' is represented in the JIRA task management system, where there are views of all incoming requests that might be Builder-appropriate.

Builders are expected to comply with all Connect Care enhancement request processes, many documented in the Clinical System Design Toolkit.