Business Events as a focal point of analysis

Transcription

1 Business Events as a focal point of analysis November 5, Las Vegas John Bethke, MBA, CBAP, CPA Bethke Consulting, LLC

2 Purpose of Presentation! To describe an analysis framework using business events to lead discovery for product or process vision, bridge the gap between business and technology and create useful output that is easily consumed by stakeholders, and reduce the risks of project challenge or failure.

3 Agenda! The problem is not understanding the problem! Project Success Data! What are Business Events and why focus on them?! Event Framework and Example! Models and other useful artifacts

4 The problem is, not understanding the problem

5 Definition of a requirement Babok A condition or capability needed by a stakeholder to solve a problem or achieve an objective. Babok A requirement is a usable representation of a need. Requirements focus on understanding what kind of value could be delivered if a requirement is fulfilled. Copyright Bethke Consulting, LLC 2013!

6 Path to useful requirements Listen Executive and stakeholder description of objectives and problems Conduct Analysis Enterprise Competitive Stakeholder Problems Agreement Elicit, Write Stories Document Obtain Then Capability Gaps Prioritization Scope, Plan etc Result Requirements targeted to specific capabilities identified and prioritized

7 Path to less useful requirements Guidance: We have a system to replace We want to purchase some software We want some enhancements We want to go mobile Direction: Gather the requirements, write the stories, project plan etc. No agreement on problems from stakeholders. Project team members have little to no understanding of the problem, stakeholders or capabilities needed prior to elicitation of requirements

8 Project success data

9 Success rate by dollar value Source: Standish Group

10 Project Success

11 Project Success Factors Source: Standish Group

12 ! Finding and fixing requirements defects early is 6 times less costly than fixing during development, testing, and after deployment to production! According to NIST, 70% of defects are injected during the requirements elicitation and 60% of those are not fixed until testing Source: Gartner Research

13 What are Business Events and why focus on them?

14 What is a Business Event?! An observable occurrence that is significant to a business Examples:! An order was received! Someone wants to view something! An application was approved! A customer profile was updated! A point in time passes and a report is generated

15 ! Lightweight easy to document and discuss, least abstracted! Clarity on business objectives and strategy! Provides a broad and informed view of business domain! Input for complex event processing configuration! Bridges understanding between strategic goals and implementation! Find the business processes, rules, roles, states, contexts, and domains that need to be modeled! Find User Stories! Identify areas of improvement! Deliver to technology a manageable set of units to be understood to facilitate informed scoping! Reduce variability and defects Understanding events facilitates understanding of the problem space to fill the gap between goals and implementation

16 Amount of Detail Level of Abstraction Corporate /Organizational Core Strategic Vision or Mission Statement Low Product/Organizational Goals Problems to be Solved/Business Needs/Objectives Stakeholders and/or Customers Capabilities Road Maps Medium Business Events Business Process Models Workflow State, Domain & Context Models Harvested Business Rules Conceptual Wireframes High Use cases/user Stories/Authoring Context Business Rules/Decision Tables Acceptance Criteria User Interface Design System Interfaces Data Requirements

17 Vision, Problems to solve, Capabilities needed Business Events Models, Detailed Requirements

18 Business Event Analysis links Executive Intentions and Implementation Planning, Requirements etc. Vision, Business Objectives & Strategy Definition Implementation

19 Business Event Approach Framework and Example

20 Business Triggering Event Stakeholder or Role Work Flow State Business Domain Objects Activities and Result Business Rules Gap What causes a customer or business operations person to do something? Who or what responds to the event? Can be a person or system When does it happen? Ex: In process, Received, approved Open Closed What business objects are created or consumed? What activities follow? What's the result of the event? What are the business rules relevant in context of the event What is the gap between current and desired future state?

21 Example: Information request case management Business Objectives: Automate costly, manual information and document request process that relies on US Mail, paper submissions and physical storage. Reduce operational, reputational and legal risks Buy or build software to support the process Reuse software where possible to support other business processes

22 Before the Sessions! Interviews and document analysis! Draft the event table content! Gain understanding of goals, strategy and objectives! Set expectations for the session i.e.: tell us what events you respond too or What makes you do something! Assume:! They did not clearly defined their objectives and goals! Artifact created may be temporary

23 Business Triggering Event Role Work Flow State Business Domain Objects Activities and Result Business Rules Gap External entity requests information or case File Liaison None, No open Case Requesting Entity Information Request Case Requested Item Correspondence Request Contacts o o o o o Create Case Add Contacts Add correspondence Add requested items Notify assigned Result: Case Created and notifications sent to assignees Requests for sensitive information require Executive approval prior to producing the required documents Requests from International entities are fulfilled for closed investigations No visibility from executives into the process Process inconsistently applied Metrics not easily available Duplicate requests Process tracked in excel

24 Business Triggering Event Role Work Flow State Business Domain Objects Activities and Result Business Rules Gap Follow up request for information or documents Liaison In Progress Requested Item Correspondence Add requested items to case Notify assigned individuals Closed cases are not opened Difficult to relate cases Case will require secondary due diligence Request Coordinator In progress Awaiting Exec approval Information Request Case Request EVP approval if necessary Mark case to require secondary due diligence Same as initial business event Response Documents and narrative ready for due diligence Liaison In Progress Review Response Documents Narrative Docs and narrative reviewed, case marked as due diligence complete Case status moves to ready for production Response Documents and narrative ready to be shipped to requesting entity Request Coordinator Production Ready Production Edit Case Crate Response Production Multiple shipping methods, Packages contain sensitive information

25 Next Steps after Events Identified! Problem Statements! Business Domain Model and Glossary! Business Process Models! Actor or Role models! State Diagrams! User Event Mapping! Context Diagrams

26 Problems Discovered! Requests not centralized causing duplicate requests! Information and documents requested that were previously requested and provided! No visibility into request process i.e.: number of requests, source of response, how fulfilled, time spent! No controls in place ensuring the integrity of the documents provided! Various delivery methods, all non electronic! Inconsistent workflow for the responses! Lack of common vocabulary

27 Models and other useful artifacts

28 Business Process Model What is the model telling the audience? How? Who is doing something? What are they doing? What sequence? Why are they doing the activities? Roles and Swim lanes Activities Control Flow (lines and arrows) Business Events

29 State Model What is the model telling the audience? How? What are the states or statuses of the business domain object? How does the business object move to the next state? What sequence? What starts the state diagram? States Business Events and/or Activities in the Transitions Control Flow (lines and arrows) Business Events/Initial State

30 Business Domain Model What is the model telling the audience? How? What are the business objects produced or consumed in the process? What is the meaning or use of each business object? What are the attributes of the Business Object What is the relationship of the objects with the other business objects? Objects or Classes Glossary Class Attributes Associations and cardinality

31 Actor or Role Model What is the model telling the audience? How? What are the roles in the business process? What is the purpose of the role? What is the relationship of roles with other roles? Actors Descriptions Generalizations

32 User Event, Role, and State Mapping What is the model telling the audience? How? When do roles execute events? Table of events, roles and states Which roles execute which events? What events are unique to a state?

33 Process Context Models What is the model telling the audience? How? What do other stakeholders expect from the process? What do the process stakeholders expect from outside stakeholders Directional arrows describing the information sent

34 UI & Business Event Mapping What is the model telling the audience? How? What business events are supported by the wireframe? Where is the wireframe used in the process? Business Event table display with wireframe or UX design Link to business process model and/or state model

35 Use Business Events as input for detailed requirements Business Event Analysis Models User Stories or Use Cases Models & Detailed Requirements linked to User Stories/ Cases

36 John Bethke, MBA, CBAP, CPA Management Consultant/PM/BA Business Process Improvement Business Architecture Business Requirements 15+ Years Experience in Finance, Accounting, Mortgage, Real Estate, Government, Regulatory Thanks! BethkeConsulting.com - Veteran Owned! linkedin.com/in/johnbethke/