Agile teams and organizations find out sooner or later, that with agile, building the wrong things faster is very possible if you leave out a key component: understanding the real problem and evaluating the impact of the potential solution before going off and doing your sprint as fast as you can. Our goal is to provide agile analysis approaches and techniques for your team to ensure the right thing is built, have user stories that clearly identify the minimum viable product, and potentially eliminate unnecessary stories.
The course provides practical guidance on handling complex projects, spontaneous scenarios and decision points that occur on an agile project. Our material covers many variations of agile analysis so that each technique taught can be adapted to different types of projects, different types of agile teams, and even a variety of agile frameworks.
At the end of this course students will be able to:
- Practice Scrum, release, and iteration/sprint planning sessions through mock exercises.
- Understand how the different agile environments (Scrum, SAFe, Kanban) impact roles, planning, and ceremonies.
- Review the top-down hierarchy of managing value.
- Align scoping and analysis techniques with each stage and step in the agile framework.
- Understand how to best facilitate communication among the agile team (i.e. the product owner, the domain stakeholders, the development team).
- Perform team skills gap analysis to help the team become even more effective and responsive to changes.
- Develop user stories using the 3Cs, the features, the epics, and cross-functional supporting content (ie:acceptance test, examples, models) for the purposes of building the right solution and tracing value.
- Discuss other types of backlog items including non-functional requirements, spikes, technical debt, and impediments.
- Elicit and communicate the appropriate level of requirement detail and how to use “just in time” practices for delivering the details.
- Outline the role analysis plays in managing, estimating, and prioritizing the backlog, along with designing, building, and testing activities.
- Identify and negotiate the factors associated with ready and done.
- Identify supporting artifacts and determine when to introduce them.
- Effectively establish a triage approach to manage the flow of changes that is encouraged and to ensure ongoing backlog grooming.
- Determine how an analyst is to adjust their practices and techniques due to the changing needs of the team.
This course is designed for anyone working on an agile team, but is especially helpful for product owners, business analysts, systems analysts, or any other team member involved with requirements on an agile project. This course may also be appropriate for individuals who manage individuals working on an agile team and need a more in-depth understanding of the process and skills useful for an agile team.
There is a short pre-requisite quiz for students to help tailor the learning process.
Each student will receive the documentation according to the contents of the course.
An immersion learning approach, along with role playing, allows students to practice the techniques as they learn. Students will experience what a project that is fully leveraging agile concepts and culture looks and feels like. This allows them to better understand their role on the team and appreciate their team member’s contributions. During the course, we will demonstrate how analysis is used at every step in the process, even if the techniques are not always recognized as analysis in their current environment.
This course includes many of the concepts found in the Scaled Agile Framework (SAFe), as well as Scrum and Kanban. It supports the standards outlined in the IIBA BABOK® Guide V3. This course will also touch upon alternate agile approaches (XP, Iterative, DAD, hybrids such as Scrumban, Scrumfall and other organic approaches) to allow those pursuing agile to consider all the practices and options. Students who have previously take our Essential Skills for Business Analysis will see how to leverage and reuse those skills in an agile environment.
To ensure the knowledge gained during class is transferred to actionable plans, we include an optional comprehensive quiz after class along with our Make Learning Stick program. Students are encouraged to bring projects into class for exercises and to develop a more personalized post-class action plan to take their project to the next step.
A certificate of attendance will be issued to students who attend the course for at least 75% of the duration.
This course is included in our Business Analysis Certification Program. By attending this course, students earn credit towards the BA Associate and BA Certified certifications, as well as credit towards the Agile Analysis Badge.
Students will earn 21 credit hours for their attendance.
- Introduction to Business Analysis in an Agile Environment
- Understanding the agile evolution
- Level-setting the fundamentals of the Agile Manifesto
- Review the pros and cons of various agile approaches (including a brief of SAFe)
- Understanding agile project characteristics and their impact on the approach to use
- Workshop: Mock sprint
- Analysis Techniques Applied on an Agile Team
- Review scope and problem statement
- Define SMART objectives used as decision filters
- Identify business drivers
- Create a feature poster
- Apply relative sizing
- Identify dependencies
- Determine the minimum viable product
- Take user stories from discovery to ready to done
- Workshop: Walk through a mock Scrum/planning case study
- Define and practice various agile planning activities
- Apply analysis techniques for the creation of features and stories
- Practice managing value during design, build, and test
- Taking User Stories to the Next Level
- User stories – more than the 3 Cs
- Identify the key criteria for the definition of ready and done
- Apply analysis techniques to create a discovery board and backlog
- Identify the analysis tasks for backlog refinement and prioritization
- Applying the 4 core components of requirements
- Explore 21 ways to break down a story
- Workshop: Writing user stories, creating acceptance criteria, examples, test cases
- Analysis Techniques Applied using Kanban Concepts
- Discuss WIP, Kanban board, workflow states
- Define and address urgent/expedited issues
- Utilize swarming to solve roadblocks
- Manage with no sprints, continuous release
- Workshop: Walk through a mock Kanban case study
- Define and practice various agile planning activities in Kanban
- Apply analysis techniques for the creation of work Items
- Practice managing value during design, build, and test
- Troubleshooting Agile Challenges
- Discuss how SAFe helps enterprise (program, portfolio) management of agile teams
- Troubleshooting agile challenges: shark tank exercise
- Team members not co-located
- No scrum master
- Not using the user story forum
- No documentation
- Introducing changes during a sprint
- Lack of regular backlog grooming
- Only putting user stories in a sprint (100% user stories)
- Team member being pulled off to do support work
- Unending enhancements without measuring ROI
- Team has abandoned retrospectives
- Implementing agile tools
- Being lean but not too lean
- Course Summary
- Bringing it all together – learning backlog review
- Develop an action plan with next steps on the student’s current project