0 votes
in Playback Approach by

2 Answers

0 votes

Playback 1 & 2 Approach, Tasks and Deliverables

Overall goal for Playback 1 is to work with users to gain User Acceptance on Process Flow, Process Routing , Tasks/Activities, UI Layouts and Report Layouts and in the process create an implementation ready fully decomposed BPM Service Layer of the Process Model. The BPM Service layer consists of General Services, Human Services, Integration Services, BPM Web Services, Decision Services (Rules), UCAs, External Implementations.

The integration stream and db stream cater to the needs of the Process Model by using the identified input outputs and operations defined by the Model. A rough design of the integration services and db model is in place as part of the Planning/Discovery Phase but it needs to align with what is actually modeled and expected by the BPM integration Layer.

We have to be ready for user feedback at the Process work stream which will affect the integration stream as well as the data stream.

  1. Business Process Work Stream
Playback 1Playback 2
  • Construct BPM Variable Types and  Data Structure
  • Construct Complete Wireframes for User Interfaces (with Manual Unit Tests Created)
  • BPM Process/Service Decomposition to implementable level (with inputs and outputs defined and Manual Unit Tests Created)
  • Construct Report Mockups in BPM (Coach Based Reports and Actual BPM Reports)
  • Enhance and Finalize BPM Variable Types and Data Structure
  • Implement User Interfaces
  • Implement Processes/Service
  • Implement Integrations
  • Implement Reports

  1. Playback Ready User Interfaces
  2. Ready to implement BPM Process Layer
  3. Ready to implement BPM Service Layer
  4. Playback Ready Report Mockups
  5. BPM Variable Types and Variable Structure


  1. Unit Tested Processes
  2. Unit Tested Services
  3. Unit Tested User Interfaces
  4. Unit Tested Reports

  1. Integration Work Stream

Playback 1Playback 2
  • Prototype BPM Integration Services layer with stubbed Data (inputs and outputs defined and Manual Unit Tests)
  • Web Service Development – Align with BPM Integration Service layer definition (what you have identified and designed meets the need of the integration layer and matches with its operations and inputs and outputs)
  • Prototype web services and db operations (initial and simple version of integrations with only basic operations and some data available)

  • Develop Web Services
  • Integrate Web Services and DB Operations – Complete BPM Integration Services Layer with Unit Testing.
  1. Implementation ready Integration Services Layer
  2. Detailed Web Services Design
  3. DB operations list with inputs and outputs defined
  4. Prototype web-services and DB operations.
  5. Unit Tested Web Services
  6. Integration Tested BPM Integration Layer

  1. Data Work Stream

Playback  1Playback 2
  • Identify static/reference data needed by reports and processes and define logical structure.
  • Identify transactional data needs of process app and define logical structure.
  • Identify and define DB Operations needed with inputs and outputs.
  • Identify web-service needs of data and define logical structure
  • Identify audit tracking needs and define logical structure.
  • Create Initial Logical DB Model
  • Partial Physical Model as per needs of prototype web-services and prototype db operations.

  • Construct and Complete Physical Model
  • Load Unit Test Data
  • Develop DB Operations
  1. Enhanced Conceptual Model
  2. Source to Destination Data Mapping  Sheet
  3. Initial Logical DB Model
  4. Partial Physical DB Model
  5. Enhanced Logical DB Model
  6. Complete Physical DB Model
  7. Unit Tested and Scripted DB Operations
  8. Scripted Unit Test Data

  1. Infrastructure Work Stream
Playback  1Playback 2
  • Identify and Plan Source System Access needs (Data Sources, Transactional Gateways etc.)
  • Identify and Plan Active Directory(LDAP) Needs
  • Identify and Plan Deployment Process
  • Identify and Plan Environment Availability.
  • Plan for Non-Functional Requirements
  • Obtain Source Systems Access aligned with development and deployment level.
  • Get LDAP groups created.
  • Deploy
  • Ensure DEV, QA and PROD Environment(s) Availability
  • Performance Testing

  1. Project Management Work Stream

Playback 1Playback 2
  • Staffing, planning, estimation, enablement
  • Organizing Playback s
  • Iteration Plan (multiple iterations per playback)
  • Work Stream Alignments
  • Real time visibility and Oversight
  • Issue identification, tracking and ensuring resolution.
Development workshop engagementOrganizing Playbacks
+1 vote
by (250 points)

refering to the developerworks (http://www.ibm.com/developerworks/bpm/bpmjournal/1302_col_simmons/1302_col_simmons.html )

quickly summarize the four playback phases. The abbreviated points listed here are taken from the Redbook:

Playback 0

  • Focus: High-level process flow (requirements definition and process discovery)
  • Goals:
    • Discovery and definition of key business processes
    • Define the implementation scope and project plan
    • Alignment of expectations, KPIs, and metrics from sponsors
    • Transfer context and responsibility from analysis to development
  • Deliverables:
    • An executable business process definition (BPD)
    • A participant and user group model (for example, swim-lanes/roles)
    • A basic data model using BPM variable types
    • Mocked-up reports to demonstrate visibility, analysis, and control
  • Out of scope
    • Implementation of user interfaces (use stubs or mock-ups)
    • Implementation of process activities (use stubs or mock-ups)

Playback 1

  • Focus: User interface design and implementation
  • Goals:
    • Implementation of BPM user interfaces
    • Extend data model to support user interfaces and decisions
    • Define human tasks, ad hoc interfaces, and reports, dashboards, and scoreboards to support visibility and control
  • Deliverables:
    • User interface implementation
      • Definition of validation to ensure and maintain data and decision integrity
      • Appearance (styles, themes, headers, consistent layout)
    • Updated data model for process and date captured via human tasks and interfaces
  • Out of scope:
    • Integrations, reference data or system-of-record population

Playback 2

  • Focus: Integrations to external systems (applications, infrastructure components, such as email, B2B)
  • Goals:
    • Implementation and exception handling for all integrations (external integrations and any system of record (SOR))
    • Definition and acceptance on service level agreements (SLAs)
    • Alignment with owners of external systems
  • Deliverables:
    • Definition of interfaces required for each integration point
    • Definition of the data transformation between systems
    • Definition of exception handling and fault codes arising via integrations
    • Definition of validation to ensure and maintain data and decision integrity
  • Out of scope
    • The solution is not a complete or functional solution; it is not ready for user acceptance testing at this point

Playback 3

  • Focus: Consolidation and finalization of the end-to-end solution
  • Goals
    • Completing details to consolidate and finalize the solution, such as process automation, user interfaces, and integrations
    • Delivery of a fully deployable and testable solution that is ready for user acceptance testing
    • Key point: This playback should not introduce any new functionality to the solution -- the focus is strictly on completeness, refinement, and stability
  • Deliverables:
    • An end-user solution that is ready for user acceptance testing environment
    • Implementation of required functionality necessary for an end-to-end solution
    • Documentation (beyond defaults in the BPM product) to enable end users, administrators, and system-level developers to understand the solution
    • Description and prioritization of all functionality to defer to the next version of the project (the "parking lot" for new features/functions)

Related questions

0 votes
0 answers 53 views
0 votes
1 answer 653 views
0 votes
1 answer 94 views
0 votes
0 answers 16 views
0 votes
1 answer 98 views
+1 vote
1 answer 1k views
0 votes
1 answer 16 views
0 votes
0 answers 18 views
0 votes
1 answer 183 views