The need to deliver value, delight customers and compete in a rapidly evolving, fast-paced market while maintaining a sustainable pace is driving many organizations to adopt Agile practices. The key to a successful Agile transformation effort is maintaining a competent team of business analysts performing effectively as part of an Agile team throughout the life of the project.
The transition to Agile development dramatically changes how and when business analysts derive and communicate pertinent project information critical to delivering value. This lively two-day workshop gives business analysts, product owners and value managers the theory and hands-on experience they need to confidently and competently derive business value in an Agile environment. Participants will learn to better define and progressively elaborate requirements by using the tools and techniques best suited for Agile projects, including prioritization methods, product/project roadmaps, story mapping, user stories and acceptance criteria.
This course is aligned with the International Institute of Business Analysis ® Business Analysis Book of Knowledge (BABOK) and is accredited by the International Consortium of Agile (ICAgile). Class time will consist of equal parts discussion and hands-on exercises. Participants who complete this course earn the ICAgile Certified Professional in Business Value Analysis Designation and can claim 14 hours of professional education.
2 Days
Audience:
This workshop is intended for business analysts or those performing business analysis tasks. It is also suitable for anyone wanting to learn Agile/Scrum analysis in-depth, including any stakeholder or participant in an organization preparing to apply Agile.
Prior knowledge of Agile fundamentals and practices is necessary to get the maximum value of this course. To be eligible for ICAgile Certified Professional in Business Value Analysis (ICP-BVA) certification, participants must be an ICAgile Certified Professional (ICP).
- Identify the similarities and differences between process-driven (“waterfall”) and empirical-driven (“Agile”) approaches
- Explore the various Agile frameworks, including Scrum, XP, Kanban and Lean
- Understand the concept of product backlogs, epics, features and user stories to convey requirements in Agile frameworks
- Learn how analysis adds business value to Agile projects
- Define key roles and responsibilities of Agile team members
- Discover the ways business analysis aligns with the principles of the Agile Manifesto
- Explore the role of the business analyst in an Agile project
- Discover how to leverage early and continuous feedback to deliver delightful products to your customers
- Learn how to craft effective user stories and define acceptance criteria for them
- Explore the techniques of story mapping, story decomposition and story elaboration
- Understand relationship between user stories and use cases
- Introduction
- Value and Value Management
- Defining Value
- Defining Value Management
- The Professional Value Manager
- Value Management in Agile
- Business Analysis in Agile Principles
- The Discovery Framework
- See the Whole
- Think as a Customer
- Analyze to Determine What is Valuable
- The Delivery Framework
- Get Real Using Examples
- Understand What is Doable
- Stimulate Collaboration and Continuous Improvement
- Avoiding Waste
- Business Analysis Guidelines and Agile Principles
- Lab: Bumper Sticker Lab
- Value Management in Agile Frameworks
- Value Management in XP
- Value Management in Lean
- Value Management in Kanban
- Value Management in Scrum
- Value Management Team
- Product Owner
- Product Manager
- Division Manager
- Scrum Manager
- Development Team
- Business Analyst
- Aligning Goals Throughout the VM Team
- Levels of Value Management
- Motivation and Alignment
- Value Management and Agile Planning
- Agile Planning Review
- Planning Terms
- Five Levels of Agile Planning
- Release Planning
- Preparing for Release Planning
- Business Analysts Responsibilities
- Iteration Planning
- Conducting Iteration Planning
- Business Analysts Responsibilities
- What to Do During the Iteration
- The Discovery Framework
- Seeing the Whole
- Personas
- Value Stream Mapping
- Thinking as a Customer
- Decomposing Stories
- Wire Frames
- Story Boarding
- Story Mapping
- Prioritizing for Value
- MoSCoW
- Monopoly Money 1
- 00 Point Method
- Requirements Prioritization Model
- Business Value Points and Risk Model
- Kano Analysis
- Business Value Points
- Accounting for Risk
- Expected Monetary Value
- Risk-Adjusted Backlog
- Risk Burndown Chart
- Spikes
- The Delivery Framework
- Using Real Examples to Create Understanding
- Behavior-Driven Development (BDD)
- Agile Modeling
- Understanding What is Doable
- Estimates in Agile
- Planning Poker and Other Methods
- Stimulating Collaboration
- Overview of 10 Collaboration – Agile Games
- Continuous Improvement
- Retrospectives
- Process Tailoring
- Avoiding Wastes in Software Development Projects
- Quality in Agile Projects
- Building Quality in
- Frequent Verification and Validation
- Definition of Done
- Story Definition of Done
- Sprint Definition of Done
- Release Definition of Done
- Test-Driven Development (TDD)
- Benefits of Test-Driven Development
- Acceptance Test-Driven Development
- Continuous Integration
- Monitoring and Reporting Value
- Key Agile Metrics
- Release Burndown Charts
- Sprint Burndown/Up Charts
- Earned Value Management
- Escaped Defects
- Key Agile Metrics
