- Are you an experienced Business Analyst?
- Would you like to learn what Agile software development is?
- What the common terms and practices are and how Agile could benefit your project?
If you'd like to gain a clear understanding of the Business Analyst's role in Agile teams, how Agile compares to traditional methods and what tools are available to you, then join this course with Alan Kelly!
In this course, we'll cover the main Agile methods Scrum and XP, and the relationship of Agile to Lean. Alan will explain common terms and practices in Agile, how Agile software projects and teams are organised and the roles on these teams. We'll then learn about the essential role of Business Analysis on Agile projects and how you, as a Business Analyst can apply Agile practices to help accelerate delivery, increase business value and ensure teams do the right thing.
If you are a Business Analyst (or you are responsible for Business Analysis or requirement gathering on a software team), and you want to learn the practices and skills required to work on an Agile Team, this Essential Agile for Business Analysts course is for you!
No results for
Essential Agile for Business Analysts
Please contact Focus on 0845 450 6120
Learn how to:
- Describe the main Agile methods: Scrum and XP, plus the relationship of Agile to Lean
- Use effective tools and practices for Business Analysts on Agile Teams.
- Apply Agile practices to help accelerate delivery and increase business value on an Agile project.
- Add value to an Agile Team and understand how Agile Teams are organised
- Become an effective Business Analyst on an Agile Team
To benefit from this Essential Agile for Business Analysts course, you'll need several years experience in Requirements Gathering and Business Analysis on software development projects, prior to attending. Prior Agile experience is not necessary.
Agile & Scrum Overview
- What is Agile software development?
- Review of Scrum and Extreme Programming (XP) methods
- The relationship between Agile, Scrum and other methods
- Benefits of Agile and Scrum
- Empirical processes control
- Agile Manifesto: values and principles
- Self-organizing teams
Sprints and Iterations
- Sprint/Iteration Cycle
- Sprint Backlog
- Daily Scrum
- Sprint Reviews
- Sprint Goal
- Abnormal Termination
- Test Driven Development (TDD)
- Acceptance Test Driven Development (ATDD)
- Continuous integration
- Code Reviews and Pair Programming
- Work breakdown
- Estimation with Planning Poker
- Impediment removal
- Vertical teams
- Risk management
- Burn-down, burn-up and cumulative flow charts
- Definition of Done
- Kaizen continuous improvement
- Product Owner role
- Customer involvement
- User Stories: Epics, Features and Tasks
- Story breakdown and estimation
- Product Backlog
- Roadmaps and Release plans
- Scrum Master
- Product Owner, Customer and Business Analyst
- Developers and Testers
How Agile Affects Business Analysis
- Short iterations and just-in-time analysis
- TDD and model driven analysis
- Communication over documentation
- Up-front QA with BA
- Business value over requirements or features
Tools for Agile Business Analysis
- User Stories and INVEST
- User stories as placeholders
- Prioritisation: MOSCOW rules and Absolute - prioritisation
- Managing backlogs
- Assigning business value
- Real options based investment
- The role of documentation
- Overview of Kanban software development method
- Importance of quality
- ScrumBut and The Nokia Test The Learning Organization