Onsite

Analysis is critical in agile! Without analysis, teams build uninspiring products and take longer to do so. The Agile Analysis Boot Camp helps agile product owners and BAs operate effectively on an agile team and get great agile results! A deep case study is used throughout the learning experience and includes product visioning, road mapping, BA/PO collaboration, healthy backlog and backlog refinement, user stories and related techniques, deeper analysis, and facilitating high-impact refinement meetings.

• Illustrate the direct relationship of great analysis to successful projects & products
• Understand the BA and PO roles on an agile team
• Distinguish what activities are part of agile business analysis
• Define a powerful product vision and roadmap and align them to the details of your everyday work
• Know where business analysis fits into agile ceremonies
• Describe what a healthy backlog looks like and how to prioritize it
• Practice key analysis techniques
• Learn to facilitate high impact backlog refinement meetings

Agile Mindset for Success

• The Agile Manifesto and what it means to agile success
• 8 Agile Practices & Guidelines that Matter
• The Agile Analysis Horizons – Levels of Detail and Planning
• Product Owner, BA & Team Collaboration

Case Study and Agile Analysis Concepts to Apply

•     Product Vision and Case Study Overview
  • Vision – Creating a compelling vision for the product
  • Defining a Problem Statement
  • Defining Outcomes and Impact Metrics
  • Vision/Roadmap/Release Planning
•     A Healthy Backlog
  • Attributes of a Healthy Backlog
  • Level of detail in a healthy backlog (Product – Release – Sprint Level)
  • Managing the backlog  

•     User Stories
  • What makes a good user story
  • Identifying good and poorly written user stories (practice on case study)
  • Practice writing user stories (practice on case study)
  • Conducting a user story workshop
• Acceptance Criteria for User Stories
  • What makes great acceptance criteria
  • Gherkin Method (practice on case study)
  • Practice writing acceptance criteria (practice on case study)
• User Story Splitting
  • Why it’s important
  • Strategies to split stories 
  • Good and poor patterns in splitting stories (practice on case study)
  • Practice splitting stories (practice on case study)
• User Story Mapping
  • Create a story map (practice on case study)
  • What the story map is used for
    • Analyze the user experience (practice on case study)
    • Analyze for gaps (practice on case study)
    • See the whole
    • Define MVP (practice on case study)
    • Organize releases (practice on case study)
• Analysis Models – Assets and Exhibits for the Team (3^rd day)
  • Scope modeling, functional decomposition, data flow, decision tables, sequence diagrams, state diagrams, process models
  • How we use models in agile
  • How models relate to user stories (practice on case study)
  • Identify what stories from case study need models (practice on case study)
• Collaborating for Success on Agile Teams (3^rd day)
  • Facilitating for better conversations and rich dialog (practice on case study)
  • Facilitation techniques for innovation (practice on case study)