+1 978.394.0597
Software Architects • Analysts • Educators
Agile Business Analysis Practices
In this two-day in-depth course, participants will gain the skills and knowledge necessary to be a
productive analyst on agile projects. The course focuses on skills for all three levels of an agile
project: product level, release level, and iteration (sprint) level. Participants will work in small teams to
build lean analysis skills and will learn how to do the right amount of analysis for the project team to
be successful. In particular, participants will understand the role of the business analyst on an agile
project, how to elicit and document requirements with stories and other rapidly developed models,
how to prioritize requirements, and how to guide the stakeholders through the project.
Principles of Agile Methods
- Agile Principles
- Agile Methods: Scrum, XP, FDD
- Agile Development Practices
- Iterations, Sprints, and Releases
- Communication in Agile Projects
- Law of Distance
- Importance of Co-Location
Agile Teams
- Roles and Responsibilities
- Product Owner
- Stakeholders
- Developers
- Business Analyst
- Proxies
Agile Project Cycle
- Agile Planning Phases
- Cycles and Rythms
- Progressive Elaboration
- Verbal vs. Written Communication
- Value of Collaboration
Agile Business Analysis Practices
- Interviewing
- Horizontal Prototyping
- Collaborative Storyboarding
- Observations and Job Shadowing
- Story Time Workshops
- Agile Requirements Elicitation Skills
- Managing the Backlog
Agile Analysis vs IIBA BOK 2.0
- Analysis Process
- Skills versus Methodology
Agile Analysis: Product View
- Establishing a Product Vision
- Product Vision Statement
- Feature Elicitation
- Establishing the Backlog
- Creating a Product Roadmap
|
Agile Analysis: Release View
- Eliciting User Stories
- Story Writing Workshops
- Decomposing Complex Stories
- Managing Epics and Sagas
- Prioritizing the Backlog
- Prioritization Strategies
- Documenting Constraints
Agile Analysis: Sprint View
- Eliciting Story Details
- Story Selection Strategies
- Card-Conversation-Confirmation Approach
- Establishing "Minimal Done Criteria"
- Sizing Stories
- Using Use Cases to Strengthen Stories
- Story Testing
- Pre and Post Conditions
- Agile Modeling
Agile Planning
- Story Estimation Techniques
- Measuring Sprint Velocity
- Calculating Team Capacity
- Establishing Scope Boundaries
- Pruning the Backlog
- Task Decomposition
- Task Estimation
- Collecting Time Remaining Metrics
- Project Metrics & Charts
- Product Demonstration
Agile User Analysis
- Stakeholder Analysis
- User Experience Analysis
- Story Boarding
- Manual Prototyping
- Participatory Design
Agile Analysis Skills & Tools
- Story Writing
- Use Case Tracing
- User Experience Analysis
- Lean UML Modeling
- Whiteboarding
- Wikispecs
- Story Backlog Management Tools
|
|


"Dr. Schedlbauer was the reason
I took this course -- his style &
past work experience were very
conducive to learning -- would
gladly take another course
taught by him."
Course Objectives
- define the key principles of agile project management and system development
- master agile requirements analysis techniques, including user stories and lean modeling
- understand the role of the business analyst on agile projects
- establish project scope through requirements prioritization
- validate requirements with stakeholders
- appreciate the value of collaboration and collaborative planning
- learn how to estimate stories and plan releases and iterations (sprints)
- adjust documentation rigor to increase productivity and facilitate communication
This course is only offered for custom on-site delivery.
Please contact us to schedule this course for your team at a location of your choice.
|
Course Contents
Suggested Length
2 Days
Audience
Business Analysts, Project
Managers, Software
Developers, Product
Owners, Scrum Teams
Cost
from $900 per day for up to
6 participants; each
additional participant is
charged at $75 per day
"Dr. Schedlbauer is an excellent
instructor! His energy and
knowledge are fantastic. He was
able to explain practical uses
that you don't get from reading a
book. "
Benefits and Takeaways
- improve accuracy of requirements while reducing time to communicate and document
- handle project risks and stakeholder expectations through collaborative prioritization
- communicate necessary requirements to ensure acceptable project quality
- increase the productivity, effectiveness, and speed of development teams