Business Analysis in Corporate Value Stream
Great Benefits That are Hiden
New Project Management Course
Business analysis has become a competency of critical importance to project management.
Becoming certified as a business analysis (BA) expert can move your career in a fresh direction while opportunities for BAs are on the rise.
- Duration: 16 Contact hours = 16 PDU
- Start: 12 - 13 April 2018
- Price: 390 EUR
- Location: Semos Education
- Language: English
- Application deadline:5 April 2018
- Apply to the link - Application
Who can attend this course?
Project Managers, Project Team Members, Functional Managers
Lecturer: Miroslav Anicin, MScE
Lean-Agile Transformation Coach - SAFe Program Consultant - Project Rescue Expert Software Delivery Expert, Software Delivery Expert, Executive and Practitioner with 20+ years of diverse experience in Project Management, Business Analysis, Business Process Management, Solution Architecture, Software Development and Solution Implementation.
- Corporate Value Stream
- What is Corporate Value Stream?
- Value Stream Mapping
- Portfolio Level – Pre-Project Activities
- Portfolio Prioritization
- Wish list vs Capacity
- Program & Project Level – Project/Program Execution Activities
- Operations – Using Product in Everyday Activities
- Output, Outcome & Benefit
- Introduction to Business Analysis
- What is Business Analysis?
- What is the Role of Business Analysis in Corporate Value Stream?
- Who is the Business Analyst?
- Business Analysis Terms
- The Requirements Classification Schema
- Requirements vs. Design
- Who are the stakeholders?
- Stakeholder Analysis
- Needs Assessment
- Defining Business Problems or Opportunities
- Developing a Solutions Scope Statement or Business Case
- Determining the Business Problem or Opportunity Value
- Identifying Business Needs
- Identifying Stakeholders and Stakeholder Values
- Determining Business Analysis Activities
- Establishing Requirements Traceability
- Preparing the Requirements Management Plan
- Defining Requirements Change Control and Communication Processes
- Identifying Document Control Processes
- Specifying Business Metrics and Defining Acceptance Criteria
- Eliciting and Identifying Requirements
- Analyzing, Decomposing, and Elaborating Requirements
- Evaluating Options and Decision-Making
- Allocating Requirements and Creating a Requirements Baseline
- Facilitating Stakeholder Consensus in order to Obtain Sign-off
- Creating Requirements Specifications
- Validating Requirements with Stakeholders
- Elaborating and Specifying Detailed Business Metrics and Detailed Acceptance Criteria
- Traceability and Monitoring
- Tracking the Status, Sources, and Relationships of Requirements
- Monitoring the Lifecycle of Requirements
- Updating the Status of Requirements and Communicating Requirements States to Stakeholders
- Using Communication Methods to Share Important Requirements Information and Status with Stakeholders
- Determining and Managing Change Impacts to the Requirements
- Comparing Solutions Test Results to Defined Requirements Acceptance Criteria
- Analyzing, Communicating, and Resolving Solution Gap Analysis
- Obtaining Stakeholder Sign-off and Moving Toward Deployment
- Measuring How Well the Solution Met Business Needs and Values
- Agile vs Traditional
- What are the Differences in Agile vs Traditional Approach?
- How to Scale Agile to Corporate Level?
- Agile Prioritization on Portfolio Level