Business Analysis Support of Large, Scaled-Agile Programs: A Case Study. Operated by the National Marrow Donor Program 1

Transcription

1 Business Analysis Support of Large, Scaled-Agile Programs: A Case Study 1

2 Saving lives... 2

3 Be The Match s Mission: We Save Lives Through Cellular Therapy 3

4 Delivering Cures for Blood Cancers For people with life-threatening blood cancers like leukemia and lymphoma or other diseases, a cure exists. Jade, cord blood transplant recipient Operated by the National Marrow Donor Program Be The Match connects patients with their donor match for a life-saving marrow or umbilical cord blood transplant. 4

5 Science and Research 5

6 Patient Assistance 6

7 Facilitate Transplants 7

8 8

9 9

10 Donor Recruitment 10

11 Registry Platform Program Replace legacy technology Architect as a platform Reengineer data and business processes Develop new tools Improve capabilities 11

12 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 12

13 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 13

14 Program 3 years, Large Scope Program Structure One Program Manager Two Business Sponsors Steering Committee Included most of the C Level executives 14

15 Program included Four projects 3 PMs Projects and Teams Six agile development teams 2 of them offshore (Minsk) 4 Scrum Masters (1 in Minsk) Data team, Design team, Solution Architecture team 15

16 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 16

17 Business Analysis Challenges Multiple Scrum teams Some teams offshore Multiple Products Needing to work together as a value chain Complex domain Data 17

18 What the Program Needed from BAs Context How things fit together within value chain Abstraction Strip away information to facilitate communication Insights Actionable 18

19 Models Modeling techniques that provide context for user stories and epics BPMN Data Flow Use Case Ad-Hoc 19

20 Useful? 20

21 BPMN: the go-to process model Donor Client Finance Donor release Case Manager 2.8 Verify release and inform client of Donor release Finance Trigger 2.6 Process Specialist Finance Trigger Screening and Consent DC001 Workup Specialist Review HHSQ and consent. Send final Gate review docs back to WU Specialist Order from HHSQ 2.1 Call Donor to determine identified RCDAD risks and get agreement to proceed Identified Risk, or Not Suitable, or Unwilling No Identified Risk, Suitable, and Willing 2.2 Schedule info session. Request a Information Packet be sent to Donor 2.7 Update status. Call and send follow up to donor regarding participation status Ineligible, or Not Suitable, or Willing 2.4 Call Donor to conduct information session Eligible, Willing, and Suitable HHSQ and docs 2.5 Enter information into system. Submit HHSQ and consent for review Final Gate review docs Case Management WU Liaison Phone call 2.3 Prepare and send Information Packet to Donor Phone call Eligibility Signed Consent Form and HHSQ Information Packet 21

22 Data Flow Diagram: awesome context conveyor Application Donor Application Swabs Recruiter DIY Application (web) Key in Application Demographics Receive, inspect and store swab Sample storage info Drive Results Key in drive info Demographics Drive info STAR Sample storage info Send Sample Info to STAR Sample storage info CrisLink Finance System Create typing requests Typing Request Queue 22

23 Use Case Analysis: perspective UC11: Pay Labs UC1: Receive and Process Donor Recruitment Samples UC10: Track Order Fulfillment and Lab Performance UC2: Analyze Queue and Plan Lab Shipments UC9: Update Registry Finance Donor Management Lab Services UC3: Submit Lab Test Batch Order UC8: Evaluate Test Results Registry/Data Quality Biorepository UC4: Assemble and Send Shipments UC7: Receive Test Results UC6: Conduct Tests and Send Results UC5: Manage Supply of QC Samples External Labs 23

24 Ad Hoc Diagrams: just add value, baby Program Defines; Other Teams Deliver and Pay For It B2B Program Defines and Pays For It; Other Teams Deliver Traxis Historical TR (Legacy) Historical Test Result: Primary Data One time migration of Legacy primary data into Core One time re-interpretation of Legacy primary data into GL strings using a specific GRD version, and then saving those GL strings into Core Historical Test Result: Haploid Historical TR (CORE) B Historical Test Result: GL String A Historical Test Result: Primary Data C Historical Test Result: Haploid StarLink Web Finances Program Defines, Delivers, and Pays For It Unite CordSource Case Haplogic PTR Formatting Event PTR Event 1.1, 1.2,... * 1.1 GL String: up-to-date PTR Maintenance version of the GL string that Updates was persisted in TR history TR and identified as the PTR. 1.2 Genomic List: up-to-date genomic list (table view) PTR Maintenance Updates version of the GL string that was persisted in TR history TR and identified as the PTR. 3 Match PTR Legacy PTR (not in CORE?) (no UI display needed) (no UI display neeeded) 2.1 Genomic List: up-to-date, 3.1 Reference ID: (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. Bioinformatics Crislink CIBMTR 1.3 Haploid: up-to-date MAC PTR Maintenance haploid translation of the GL Updates string that was persisted in TR history TR and identified as the PTR. 24

25 Ad Hoc Pt. 2 Legacy Primary Data Haploid Genotype list Pdtl Sequence only Search Typing (RegODS) Step 2b: Migration of sequence data to Core Step 2a: Reinterpret GL Strings from Primary data Step 1: ETL of Search Typing values from RegODS to PTR in Core PTR Historical TRs - Core Primary Data GL String (Haploid) (GL string) Match PTR Legacy PTR PTRs - Core Haploid Step 3: PTR Curation 25

26 Business Architecture Business Architecture domains that spoke to project sponsors and program leaders: Capabilities Information Products and Services 26

27 Capabilities Test Result (TR) Management Source Management Search & Match Case Management TR Intake TR Processing Member Source Management Non-Member Source Management Automated Search and Match Bioinformatics Eligibility Management Suitability Management TR Persistence TR Provisioning Source Sharing Search Strategy Consent Management Scheduling Reference Data Management Sample Inventory Management Registry Management Counseling Supporting Core Ref Data Ref Data Intake Curation Cell Collection Business Party Management Financial Management Funding Program Management Sample Intake Sample Storage and Inspection Shipment QC Sample Management Generation Cell Supply Chain Management Performance Tracking & Reporting Medical Services Management Data Quality Management IT System Management Legal and Regulatory Management Security and Privacy Compliance Network Management Apheresis Contract / Center Agreement Management Management Transplant Donor Center Center Management Management Registry Lab Network Management Management Research Standards Network Group Management Participation Order Management Customer Fulfillment Order Order Management Management Supplier Order Management 27

28 Information Customer Order -membername -membername 0..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 Fulfillment Order Fulfillment Steps -membername Supplier Order -membername -membername 1...* * 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. Test Result Information Submission -Who the Submission is from -Why they are sending the Submission -HML Version they are using -Unique ID Submitter assigned * Sample Result -Sample ID (supplied by NMDP) 1.. * -membername * Typing Test Result -membername 1.. * -membername Is often in response to > Is fulfilled by > Lab Test Supplier Order Information * Lab Test Order -membername -membername Order Line Item -membername -membername * 1.. * Is an order to test a sample from a > Subject Information Subject 1 -Donor Center (if Subject is a Donor -Cord Blood Bank (if Subject is a CBU) Lab Test Supplier Order -Order Line Items (SOLID) -membername 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 28

29 Products and Services Capabilities are combined and made actionable through Processes are external facing descriptions of combinations of 1..* deliver value in the form of Products/ Services purchase Clients 29

30 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 program backlog 30

31 Point-In-Time Artifacts 31

32 Describe the Business Story Expect lab to resubmit messages. They will need to do so to get paid Gateway Failed Structure Validation 1) Determine whether the submitted message is valid Submitted {Structure Val.} HML Message Failed Content Validation 2) Determine whether all TRs pass basic content rules {Content Val.} Failed Content Validation 3) Determine whether all TRs have either a SOLID or a Center Code 3.5) Determine whether any TR failed SOLID related schema validation. If so, post an advisory message to Dashboard 4) Determine whether test results are for Research or Registry Research 5) Save TR submission Intended Registry to the Registry Use Queue of file repository Update Dashboard HML Submission Changes to be made to HML: Add Order Line Item ID No 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 no Report to Dashboard 14) Test Result Exception Handling Report to Dashboard 13) Try to find a Subject ID to associate to TR Able to find TR to a Subject? yes Core KIR CCR5 Invalid TR Reply via processor which then reports to dashboard 6) Extract TR submission from Registry Queue of file repository 7) Identify what gene family the test result is for HLA For each TR 8) Genomic Validation Display for internal user to review Flagged ABO/RhD 9) Pass TR info to SOM when SOLID is present 15) Associate TR to Subject ID and Persist in Core 16) Discordant/Discrepancy Determination and PTR Determination. SOM 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 10) Look up the Order Line Item ID Order Line Item matched? yes 11) Determine if the attributes match? 12) Reply back to Core and Gateway 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? no 32

33 Use a Business Initiative Level in the Backlog New Ready for a High-Level SWAG Ready to Estimate Has a set of epics that cover the initiative It has a SWAG Estimated Has a comprehensive set of epics that cover the initiative Decomposed into Epic New Initiative Epic Epics are estimated Groomed and ready for a High-Level SWAG Planned Ready to Estimate It has a SWAG all of the work under this initiative is done Estimated Done Has a comprehensive set of stories that cover the epic Decomposed into Stories One or more stories under epic are being actively worked on In-Progress all of the work under this epic is done Done New Groomed and ready to estimate Ready to Estimate It has an estimate Estimated Ready to be allocated to a sprint Ready for Sprint Story is being actively worked on In-Progress Ready to Test Tested Story Story Epic Story Initiative Done 33

34 Assist in identifying and grooming backlog Contribute to and Edit backlog content Rationale Acceptance Criteria Description Initiatives and Epics 34

35 Manage an Executive Summary of Backlog Organize backlog: Immediacy Releases Teams Components 35

36 Give. Join. Volunteer. Participate. 36