business architecture support of large, scaled …...delivering cures for blood cancers for people...

Business Architecture Support of

Large, Scaled-Agile Programs:

A Case Study

Operated by the National Marrow Donor Program® 1

Saving lives . . .

2Operated by the National Marrow Donor Program®

Be The Match’s Mission:

“We Save Lives Through

Cellular Therapy”


Delivering Cures for Blood Cancers

For people with life-threatening

blood cancers like leukemia and

lymphoma or other diseases, a

cure exists.

Be The Match connects

patients with their donor

match for a life-saving

marrow or umbilical

cord blood transplant.


Jade, cord blood transplant recipient

Science and Research


Patient Assistance


Facilitate Transplants


Donor Recruitment


Registry Platform Program

• Replace legacy technology

• Architect as a platform

• Reengineer data and business processes

• Develop new tools

• Improve capabilities


Previous Attempts

• Previous attempts to do this

• Partial successes

• Never reaching the goal

• Stakeholders affected – “We already did this analysis”

– Some tacit skepticism

• Recognition of need and urgency overcame this


Agile

• Be The Match is a recent adopter of Scrum

• Agile methods had been used on smaller,

stand-alone projects

• But not yet done on a large program

• Scaling Agile challenges


Program Structure

• Program

– 3 years, Large Scope

– One Program Manager

– Two Business Sponsors

– Steering Committee

• Included most of the C Level executives


Projects and Teams

• Program included

– Four projects • 3 PMs

– Six agile development teams

• 2 of them offshore (Minsk)

• 4 Scrum Masters (1 in Minsk)

– Data team, Design team, Solution Architecture team


Business Analysts, Products Owners, and

Business Stakeholders

• One Enterprise Business Analyst

– Program Level Business Analysis & Architecture

• Six Business Analysts

– Project Level Business Analysis

• Three Product Owners, Four Business Leads

• Numerous SMEs


Challenges

• Multiple Scrum teams

– Some teams offshore

• Multiple Products

– Needing to work together as a value chain

• Complex domain

– Data


What the Program Needed

• Context – How things fit together within value chain

• Abstraction– Strip away information to facilitate communication

• Insights

– Actionable


Existing Business Architecture Knowledgebase

• None– Knowledge was there, but not in anything like a

centralized, managed Biz Arch repository

• Wasn’t Ask For– Strip away information to facilitate communication

• This is Common and Normal– BA to meet a specific need vs. formalized, devoted effort


Models

• Modeling techniques that provide context

for user stories and epics

– BPMN

– Data Flow

– Use Case

– Ad-Hoc


Useful?


Las t update: 10 /9/2017 8:50 :38 AM page 1of 1C:\Us ers\d lars on2\Doc um ents\Phoenix\Phoenix Bus ines s Proc es s L2 M odel Cord 2 Selec t v1.7.v s dx

Cu

sto

me

r(T

rans

pla

nt C

ente

r)

DC

BM

S

(Do

nor

Co

nta

ct

Tea

m)

Re

gis

try D

ata

Qu

alit

yS

earc

h S

tra

teg

yC

ord

Blo

od

Ban

kLa

bC

ase

Ma

na

gem

en

tM

edic

al S

erv

ice

sFi

na

nce

Update

CBU Information

Create ISL“Haplogic ”

Regis ter Patient

Create

Cus tomer Orderfor Search

Create

Patient Case

New

Case?

View Integrated &

Filtered Search Lis ts

NeedTes ting?

ToQual i fy

To

El ig ib i l i ty

Yes

Pay

Supplier / Provider

Invoice

Cus tomer

Validate Patient

aa

ab Create Filtered

Search Lis t( TC Preferences)

ae

No

Apply

“ad hoc” Filters

(cus tom c riteria)

af

Create Fulfillment Order

for Search Strategy

ah

Receive Fulfillment Order

ak

Dis tribute

to Strategis t

Internal or External?

al

Create Search Strategy Advice

(SSA)

In ternal

Analyze HLA

(tool based)

Conduct PeerReview

Create Search Strategy Advice

(SSA )

Receive

Supplier Order

Send Search Strategy Advice

(SSA)

Receive Search

Strategy Advice

(SSA)

Dis tribute to Strategis t

Create Supplier Order

for

Search Strategy

Ex ternal

ao

Release Search Strategy Advice

(SSA)

View Search

Strategy Advice(read only SSA)

Create / Modify

Order Preview Lis t

Proceed with CBU( s)

Yes

No

Reques t Subsequent

Search Strategy

Review(s)

bc

bb

at

ba

bq

As s um ption: This is a po int-

in-tim e s naps hot w/i the patient’s rec ord

Create

PatientClinical Record

Apply

Preferences? Yes

Create Starter Lis t ( Inputs : ISL,

SS Preferences,

TC Preferences,ad hoc Filters)

Analyze HLA

(tool based)

Incorporate

Recommendations

Send Released

Search

Strategy Advice ( SSA)

Receive Released

Search Strategy

Advice (SSA)

as

Create

Purchase Order

bo

Invoice NMDP

Import SSA Recommendations

into

Order Preview Lis t

Receive

Cus tomer Orderfor Search

ac

Send

Unit Report

and/or RACBI

Receive

Supplier Order

As s um ptions:

If d ig i ta l de l iv ery (In ternational), arti fac t is added to CDR.

If paper de l iv ery, doc um ent m gm t owns proc es s arti fac t and is added to CDR

Validate

Unit Report and /or RACBI

bl

Uni t Reportand/or

RACBI

Av ai lab le

SendUnit Report

and/ or

RACBI

Unit Rpt and/ or

RACBI

Available?

ViewUnit Report and/

or RACBI

Create

Customer Orderfor

Unit Report and /or

RACBI

Yes

No

bk

an

bg

CreatePatient Case Plan

& Workflow

Update/Adjus t

Patient Case

Selec t CBU( s) for

Cus tomer Order(Source Service)

Val idation bas ed on form at

From

Regis ter

Process model includes:

1) Register patient2) Create ISL

3) Create SSA 4) Create OPL

5) TC adding NMDP Registry CBUs on ISL to OPL6) TC adding NMDP Registry CBUs not on ISL to OPL (TC Co-op search) 7) TC adding NMDP Registry CBUs not on ISL to OPL (BMDW list )

8) Patient directed transplant case orders

Process model excludes:

1) Dynamic new CBU matches to active patient searches 2) TC adding Non-NMDP Registry CBUs to OPL

3) CBU selection and internal order for typing/testing4) Customer order cancellation5) Domestic CBB providing Unit Report and/or RACBI

6) Validation requirements change control7) ISL and SSA archival

au

Receive

RFI

SendRFI

for CBU Update

Transformation includes:

1) Automated ISL2) Automated Starter List (Auto SSA)

3) Automated work load balancing twice within process 4) Closed loop payments with supplier invoices

CreatePurchase

Requis ition

Receive

Purchase Requis ition

Reconc ile

Invoices

HLA c ons ul tants work in m any s ettings inc lud ing labs and hom e offic e.

Phoenix Initiative – IDEAL Future State Business Process Level 2 Model 2: Search and Confirm Availability (Select ) – Cord Blood

bp

Create

Sales

Order

ad

No

n-N

MD

P

Re

gis

trie

s

Re

crui

tme

nt

Ce

nte

r

Co

llec

tion

Cen

ter

Aph

ere

sis

Ce

nte

rC

lini

cL

ab

Se

rvic

esR

epo

sito

ry

Se

rvic

es

ApplySupplier Order

Bus . Rules

bd

Rec ip ient

Evaluate

Results &

Responses

Update CBU

Clinical Status

Send

Clinical Status

or Alert

Updated Cl in ic a l Status or

Cl in ic a l Alert (e .g . IDM )

ReceiveClinical Status

bj

Uni t Report

and/orRACBI

Av ai lab le

ar

CBU

Clinical

Record Exis t?

Create CBU Clinical Record

No

Yes

br

Update/Fulfill

Service Order( s)

Update/Fulfill Cus tomer Order( s)

Receive

Fulfillment Order

CreateSupplier Order

for

Unit Report and/ or RACBI

am

ax

Receive

Cus tomer Order

for Search Strategy

Receive

Cus tomer Order

for Search

Create

Cus tomer Orderfor Search Strategy

ag

bf

Update

Source Regis try

ay

bs

Review/Track

Cus tomer Order Progress

CreateFulfillment Order

for Unit Report and/ or

RACBI

ReceiveCustomer Order

for

Unit Report and/or RACBI

be

Receive

Clinical Status

bt

az

Ass ign

Staff

Confirm

CBU Information

Confirm

Information

ap aq

Re

gis

try

Do

nor

Monitor

Orders

DC

BM

S(O

the

r)

bv

Receive

Unit Report and/

or RACBI

CreateCustomer Order

for

Unit Report and/or RACBI

Unit Rptand/or

RACBI

Needed

bh

ReceiveUnit Report

and/ or

RACBI

Receive

Supplier Order

Write

Clinical Order

CBU

Clinical

RecordExis t?

Create CBU Clinical

Record

No

Yes

Monitor

Orders

Create

Supplier

Order for Clinical Order

Receive

Clinical

Order

av

aw

Receive

Clinical Status

bn

Las t message serial number used: bw

ai

a j

bwBi l lab le

No

TC SSA

Preferenc e

TC SSAPreferenc e

Ex ternal Strateg is t

Update Patient

Case Plan & Workflow

Update CBU Sub -Case

Plan( s) & Workflows

Update Patient




Update Patient




Create CBU Case

Plan & Sub-cases

Inc ludes heal th h is tory

MonitorCase

Proceed with CBU(s)

Flow Legend

Phy s ic a l Pac k age Shipm ent

M es s age flow between bus ines s uni ts

Ac tiv i ty flow / order o f ex ec ution

Condi tional ac tiv i ty flow

Condi tional m es s age flow

M es s age flow, not i l lus tra ting s equenc e

M es s age flow between bus ines s uni ts,

not i l lus tra ting s equenc e

Add/RemoveCBU

Create

RFIfor

CBU Information

Proc es s Owner:Repos itory & Laboratory

Services

Case Mgmt& Operations

Services

Donor / Cord Blood

Mgmt Svcs

Finance CustomerMedical Services

National Marrow Donor Program Business Units

PartnerNOTE: Yellow highlighted areas are a suggested “ideal” future state with no

conditions/criteria related to minimum need, frequency, cost, schedule, or complexity. The current process(es) may be within the noted swim lane, others or

a combination of thereof –Validation with said area(s) is required to understand current process steps and area ownership impact before ANY solutioning against

future state area(s) begin. Yellow w/Red Letters speculate significant restructure.

Last Model Update – 02/25/2014

BPMN: the go-to process model

Scre

enin

g an

d C

on

sen

t

DC

00

1 W

ork

up

Sp

ecia

list

Do

no

r

Cas

e M

anag

er

Clie

nt

Pro

cess

Sp

ecia

list

WU

Lia

iso

n

Fin

ance

Order from Case Management

2.1Call Donor to

determine identified RCDAD risks and get

agreement to proceed

2.2Schedule info

session. Request a Information Packet

be sent to Donor

HHSQ

Phone call

Information Packet

2.4Call Donor to

conduct information session

Phone call

No Identified Risk,Suitable,

and Willing

Eligible, Willing,

and Suitable

Ineligible,or Not Suitable,

or Willing

Signed Consent Formand HHSQ

2.5Enter information

into system. Submit HHSQ and consent

for review

2.7Update status.

Call and send follow up email to donor regarding

participation status

2.8Verify release and

inform client of Donor release

Donor release

Identified Risk, or Not Suitable,

or Unwilling

2.6Review HHSQ and

consent. Send final Gate review docs

back to WU Specialist

HHSQ and docs

Final Gate review docs

EligibilityEmail

2.3Prepare and send

Information Packet to Donor

FinanceTrigger

FinanceTrigger


Data Flow Diagram: awesome context conveyor


STAR CrisLink

Donor

DIY Application

(web)

Application

Demographics

Key in Application

Application

Demographics

Recruiter

Receive, inspect and store swab

Swabs

Sample storage info

Sample storage info

Send Sample Info to STAR

Sample storage info

Finance System

Key in drive info

Drive Results

Drive info

Create typing

requests

Queue

Typing Request

Use Case Analysis: perspective


Registry/Data Quality

Lab Services

Biorepository

Finance

UC1:Receive and Process

Donor Recruitment Samples

UC2:Analyze Queue and Plan

Lab Shipments

UC3:Submit Lab Test

Batch Order

UC4:Assemble and Send

Shipments

UC5:Manage Supply of QC

SamplesUC6:

Conduct Tests and Send Results

UC8:Evaluate

Test Results

UC7:Receive

Test Results

UC9:Update Registry

UC10:Track Order Fulfillmentand Lab Performance

UC11:Pay Labs

Donor Management

External Labs

Ad Hoc Diagrams: just add value, baby

Program Defines, Delivers, and Pays

For It

Program Defines and Pays For It; Other Teams Deliver

Program Defines; Other Teams Deliver and Pay For It

B2B

Finances

Crislink

Haplogic

Case

Traxis

CordSourceStarLink Web

CIBMTRBioinformatics

Unite

PTRMatch PTR

(not in CORE?)(no UI display neeeded)

Legacy PTR(no UI display needed)

Historical Test Result: Primary Data

A

Historical Test Result: GL String

BHistorical Test Result:

Haploid

C

His

tori

cal T

R

(CO

RE)

P

TR F

orm

att

ing

12

3

1.1 GL String: up-to-date version of the GL string that was persisted in TR history TR and identified as the PTR.

1.2 Genomic List: up-to-date genomic list (table view) version of the GL string that was persisted in TR history TR and identified as the PTR.

1.3 Haploid: up-to-date MAC haploid translation of the GL string that was persisted in TR history TR and identified as the PTR.

2.1 Genomic List: up-to-date, (fully decomposed to the allele level and utilizing short names), genomic list (table view) version of the GL string that was persisted in TR history TR and identified as the PTR, and which is consumable by Haplogic. This would enriched with other info from GRD.

3.1 Reference ID: PTR Maintenance

Updates

PTR Maintenance Updates

PTR Maintenance Updates

Event 1

Event 1.1, 1.2, . . . *

His

tori

cal T

R

(Leg

acy

)

Historical Test Result: Primary Data

One time re-interpretation of Legacy primary data into GL strings using a specific GRD version, and then saving those GL strings into Core

One time migration of Legacy primary data into Core

Historical Test Result: Haploid


Ad Hoc Pt. 2


Legacy

His

tori

cal T

Rs

- C

ore

PTR

s - Co

re

Match PTR

Legacy PTR

Primary Data

GL String

Haploid

Primary Data

Haploid

Step 1:ETL of Search Typing values

from RegODS to PTR in Core

Step 2a:Reinterpret GL

Strings from Primary data

Step 2b:Migration of

sequence data to Core

Sequence only

Step 3:PTR Curation

PTR

(GL string)

(Haploid)

Search Typing

(RegODS)

Genotype list

Pdtl

Business Architecture

• Business Architecture domains that spoke

to project sponsors and program leaders:

– Capabilities

– Information

– Products and Services


Capabilities


Su

pp

ort

ing

Co

re

Test Result (TR) Management

TR Processing

TR Persistence

TR Intake

TR Provisioning

Performance Tracking & Reporting

Source Management

Non-Member Source

Management

Source Sharing

Member Source Management

Search & Match

Sample Inventory Management

Sample Storage

QC Sample Generation

Sample Intake and Inspection

Shipment Management

Financial Management Medical Services Management

Business Party Management IT System Management

Legal and Regulatory Management

Security and Privacy

Compliance

Order Management

Fulfillment Order

Management

Customer Order

Management

Supplier Order Management

Funding Program

Management

Reference Data Management

Ref DataCuration

Ref DataIntake

Case Management

Suitability Management

Scheduling

Eligibility Management

Counseling

Consent Management

Automated Search and

MatchBioinformatics

Search Strategy

Network Management

Contract / Agreement

Management

Transplant Center

Management

Apheresis Center

Management

Donor Center Management

LabManagement

Registry Network

Management

Research Network

Management

Standards Group

Participation

Cell Collection Cell Supply Chain Management

Registry Management

Data Quality Management

Information

Submission

-Who the Submission is from

-Why they are sending the Submission

Sample Result

-Sample ID (supplied by NMDP)

-memberName

Typing Test Result

-memberName

-memberName

1

1 . . *

Lab Test Order

-memberName

-memberName

0 . . 11. . *Is often in response to >

Order Line Item

-memberName

-memberName

1

1 . . *

0 . . *1 . . *

Is fulfilled by >

1

1 . . *

Test Result Information Lab Test Supplier Order

Information

-HML Version they are using

-Unique ID Submitter assigned

Subject

-Donor Center (if Subject is a Donor

-Cord Blood Bank (if Subject is a CBU)

Subject Information

11. . *

Is an order to test a sample from a >


Customer Order

-memberName

-memberName

Fulfillment Order

Fulfillment Steps

-memberName

Supplier Order

-memberName

-memberName

0..1

0...*

Lab Test Supplier Order

-Order Line Items (SOLID)

-memberName

0..1

1...*

Characteristics:· A CO is a request for a source; · It is initiated by a Customer (e.g. TC, BioTherapies Client)· It serves as a “container” for the 1 or more FO’s that are used to accomplish a

CO· A CO is initiated with the initial FO for a customer; it can have many different

outcomes depending on the results of those FOs

Characteristics:· A FO is for a specific thing that a Customer wants NMDP to do for a specific

source; and in exchange doing the work, the customer will pay NMDP· It is initiated by or on behalf of a Customer · A FO is often done as part of a larger CO (Are there exceptions where a FO can

be done outside of a CO?)· FO’s are defined “menu items” that a Customer selects (e.g. for Donor: CT, HR,

Hold, WU) · Each FO has a defined set of Fulfillment Steps· The completion of the Fulfillment Steps determine the status of the FO.· NMDP can be paid for products delivered and services done (at the Fulfillment

Step level)

Characteristics:· A SO is initiated by NMDP. · A SO is a request for a supplier to do something specific for NMDP; and in

exchange for doing what was ordered, NMDP will pay the supplier.

Characteristics:· A type of SO · Used when i) the supplier is a contracted lab, and ii) what’s being ordered is

typing results from a source sample

Products and Services


Capabilities

deliver value in the form of

Processes

are combined and made actionable through

Clients

purchase

are external facing descriptions of

combinations of 1..*

Products/ Services

Developing Artifacts for Scaling Agile Programs

• Develop point-in-time artifacts

• Describe the business needs

• Define business goal “initiatives”

• Assist in identifying and grooming epics and stories

• Manage an executive summary of the backlog

• Start a “Discovery Club”


Point-In-Time Artifacts


Describe the Business’ Story

Gat

eway

Co

reSO

M

Submitted HML Message

1)Determine whether

the submitted message is valid{Structure Val.}

2)Determine whether

all TRs pass basic content rules {Content Val.}

HML Submission

4)Determine whether test results are for

Research or Registry

RegistryIntended

Use

Research

6)Extract TR submission from Registry Queue

of file repository

HLA8)

Genomic Validation

Report to Dashboard

Invalid TR

16)Discordant/Discrepancy

Determination and PTR Determination.

Flagged

Display for internal user to review

15) Associate TR to Subject ID and Persist in Core

7) Identify what gene

family the test result is for For each TR

KIRCCR5

ABO/RhD

9) Pass TR info to SOM

when SOLID is present

10) Look up the Order

Line Item ID

Order Line Item matched?

yes11)

Determine if the attributes match?

12) Reply back to Core

and Gateway

Reply via processor which then reports to dashboard

no

Report to Dashboard

14) Test Result

Exception Handling

13) Try to find a Subject ID to associate to TR

Able to find TR to a Subject? yes

no

3.5) Determine whether any TR

failed SOLID related schema validation. If so, post an advisory message

to Dashboard

Failed Structure Validation Failed Content Validation

5)Save TR submission

to the Registry Queue of file

repository

Update Dashboard3)

Determine whether all TRs have either a

SOLID or a Center Code

Failed Content Validation

Changes to be made to HML:Add· Order Line Item IDNo longer required · Center Code

Note: Project Name / Test Reason will remain as a required field so that that the determination of

Research or Registry can be done in Activity #2

Info passed on to SOM· Supplier Order Line ID (SOLID)Info for received-to-ordered comparison

· Sample ID· Reporting Center · Test done

Info for SOM use only· Resolution done· Method used · Date & Time (persisted to file queue)· Failed Result (y/n)

Info needed {for reporting to Dashboard

· Doc ID GUID

Info reported to Gateway if there’s a “no” for any of the following questions:- Was OLID found? If yes, - DO SIDs match? - Do RCs match? - Do Tests match?

Expect lab to resubmit messages. They will need to

do so to get paid


Use a Business Initiative Level in the Backlog

New

Ready to Estimate

Ready for a High-Level SWAG

Estimated

It has a SWAG

Decomposed into Epic

Has a set of epics that cover the initiative

Has a comprehensive set of epics that cover the initiative

Planned

Epics are estimated

Done

all of the work under this initiative is done

New

Ready to Estimate

Groomed and ready for a High-Level SWAG

Estimated

It has a SWAG

Decomposed into Stories

Has a comprehensive set of stories that cover the epic

New

In-Progress

One or more stories under epic are being actively worked on

Done

all of the work under this epic is done

Ready to Estimate

Groomed and ready to estimate

Estimated

It has an estimate

Ready for Sprint

Ready to be allocated to a sprint

In-Progress

Story is being actively worked on

Done

Ready to Test

Tested

• Capability

– Epic

• Story

• Story

– Epic

• Story

• Capability


Assist in identifying and grooming backlog

• Contribute to and Edit

backlog content

– Rationale

– Acceptance Criteria

– Description

• Initiatives and Epics


Manage an “Executive Summary” of Backlog

Organize backlog:

• Immediacy

• Releases

• Teams

• Components


Questions?


Give. Join. Volunteer. Participate.


Be The MatchGive, Join, Volunteer, Participate at:

https://bethematch.org/support-the-cause/donate-bone-marrow/join-the-marrow-registry/

Dean LarsonLink in with me at:

https://www.linkedin.com/in/deanlarson/


https://bethematch.org/support-the-cause/donate-bone-marrow/join-the-marrow-registry/

https://www.linkedin.com/in/deanlarson/

business architecture support of large, scaled …...delivering cures for blood cancers for people...

Documents