Here is part 4 of the presentation to the IIBA® (International Institute of Business Analysis TM) Cincinnati Chapter and the Bluegrass IIBA® Chapter.
NEW workshop: User Stories – From Discovery to Acceptance Testing
Techniques for Capturing and Analyzing User Stories, Acceptance Criteria, Scenarios, and Examples
to Communicate Business Needs
About Part 4: Operational Business Analysis uses Stakeholder Requirements in the traditional sense or User Stories in the new Lean and Agile world to define Solution Requirements (a.k.a. Functional and Non-functional or Quality Requirements). This video introduces typical outcomes of Operational Business Analysis and common business analysis techniques used during this stage.
During Operational Business Analysis, developers, someone wearing the business analysis hat, and test engineers work with representatives from the business community using appropriate business analysis techniques to flush out the details of a User Story, Work Item, Kanban task, or stakeholder requirement to the level of comfort developers and testers need to code or test the software. The use of a consistent set of sound business analysis techniques significantly reduces misunderstanding and misinterpreting the intent of the user stories and/or stakeholder requirements.
Watch all parts of the IIBA presentation
Part 1: Agile, Lean, DevOps, Kanban, ATD, BDD, Cynefin – the New World for Business Analysts
Part 2: Business Analysis Techniques Used by the Strategic Business Analyst
Part 3: Business Analysis Techniques Used by the Tactical Business Analyst
Part 4: Business Analysis Techniques Used by the Operational Business Analyst
Part 5: When Do You Do Business Analysis in Agile Projects
Part 6: The Now and Future Business Analyst Profession