Duration 3 days – 21 hrs.
Overview
The “Business Analysis in Agile Environment” training course is designed to equip business analysts with the knowledge and skills necessary to effectively perform their roles within agile teams. This course focuses on the principles of agile methodologies, the role of a business analyst in agile projects, and techniques for effective requirement gathering and management in a fast-paced, iterative environment.
Objectives
- Understand the fundamentals of agile methodologies and frameworks.
- Define the role and responsibilities of a business analyst in an agile environment.
- Apply agile principles to business analysis activities.
- Effectively gather, document, and manage requirements in agile projects.
- Collaborate with stakeholders to ensure the delivery of high-quality products.
Audience
- Business Analysts: Professionals looking to enhance their skills in agile environments.
- Product Owners and Managers: Individuals responsible for product development and requirement management.
- Scrum Masters and Agile Coaches: Those facilitating agile processes and ensuring team adherence to agile principles.
- IT and Development Professionals: Members of development teams working in or transitioning to agile frameworks.
Pre-requisites
- Basic understanding of business analysis principles.
- Familiarity with software development processes (helpful but not mandatory).
Course Content
AGILE Overview
- 4th Industrial Revolution
- Business Agility
- Agile Overview
- Agile Manifesto
- Agile vs. Waterfall
- Agile Mindset
- Flavors of Agile
- Kanban
- Scrum
- Scrum vs. Kanban
Business Analysis in AGILE
- Business Analyst in Agile Teams
- Product Backlog Development
- Techniques in Requirements Gathering and Analysis
SCRUM
- What is Scrum
- Scrum Values
- Scrum Pillars
- Scrum Roles
- Scrum Events
- Scrum Artifacts
- Scrum Board and Tools
SCRUM Execution
Pre-Sprint/Product Backlog Development
- Product Vision to Product Roadmap
- Design Thinking and Design Sprint
- User Persona
- User Journey
- User Story Mapping
- Building the Product Backlog
- Theme
- Epic
- Definition of Ready
- Definition of Done
- User Story Writing
- From Epic to User Story
- Writing User Stories
- Acceptance Criteria
- Product Backlog Refinement
- Prioritization
- Release Planning
Sprint
- Sprint Calendar
- 4-Week Sprint
- 2-Week Sprint
- Sprint Planning
- Presentation
- Discussion
- Estimation
- Commitment
- Sprint Backlog
- Daily Scrum/Standup Meeting
- Did Yesterday
- Do Today
- Impediments
- 16th Minute
- Mid-Sprint Product Backlog Refinement
- Sprint Review and Demo
- Review
- Demo
- Acceptance
- Sprint Retrospective
- Went Well
- Needs Improvement
- Action Items
- Next Sprint
- READY User Stories
- Release Plan Refinement
- Schedule of Release
Summary
- Communication and Collaboration in Agile
- Requirements Management in Agile
- Validation and Verification in Agile
- Q and A
- Closing Remarks
