Become an Agile Business Analyst in Scrum - IIBA Endorsed

Explore IIBA-defined business analysis as enabling organizational change by defining needs and recommending solutions that deliver value to stakeholders and customers, with the BA acting as a change agent.

Collaborate with end users and SMEs to align business needs with the product backlog and create value-driven user stories. Facilitate team dialogue and guide the product owner toward delivering value.

Learn a typical day in the life of an agile business analyst, balancing stand-ups, backlog prioritization, and collaboration with product owners to craft user stories.

Solve unmet and unrealized user needs by researching and validating potential solutions through experiments and cost-benefit analysis. Collaborate with product owners to master problem-solving and apply qualitative and quantitative signals.

Learn how the IIBA's agile extension to the BABOK guides standards for agile projects, the AAC certification, and how this course helps apply practices to drive value.

Explore how business analysts remain essential in agile environments, with scrum roles defined yet flexible, and learn how analysis happens across the agile extension's three horizons to deliver value.

Explore the agile business analysis core concept model (BACCM) and how its six interrelated concepts: need, change, solution, stakeholders, value, and context establish a common language for effective change.

Explore the 12 agile principles and the seven BA principles from the IPA extension, and discover how a business analyst can apply them and cultivate the agile mindset.

Align the business analyst view with the agile manifesto values: individuals and interactions, working software, customer collaboration, and responding to change for feedback-driven, incremental delivery.

Explore the twelve agile principles from a business analyst perspective, showing how to decompose features, prioritize value, embrace changes, deliver working software frequently, and foster collaboration.

Discover the seven agile business analysis principles, from seeing the whole and thinking like a customer to valuing impact, using examples, and avoiding waste through continuous improvement.

Adopt an agile mindset that centers on human collaboration, delivering value rapidly, iterating to learn, simplifying to avoid waste, and adapting products to market feedback for quality.

Streamline HR workflows with Trainable by enabling recruiters to create role requisitions, invite candidates, collect resumes and audio or video assessments, and rank top applicants for interviews via email.

Define the strategy horizon by aligning organizational goals with evolving external factors like competition, technology, and customer needs, while assessing internal changes and validating initiative value and outcomes.

Apply seven agile principles for agile business analysis to the strategy horizon, guiding value, collaboration, and continuous improvement while avoiding waste to meet customer needs and organizational goals.

Identify and analyze solution options in the initiative horizon, shaping features with stakeholder feedback to maximize value with minimal effort. Prioritize and sequence the backlog for future delivery.

Apply seven agile principles to initiative horizon by prioritizing value, getting real with customer feedback, ensuring feasibility, and fostering collaboration to reduce waste and support continuous improvement.

Clarify needs through the delivery horizon with continuous collaboration from stakeholders, elaborating user stories into a prioritized backlog, refining toward solution features, and removing items to maximize outcomes.

Explore the agile horizons: delivery, initiative, and strategy, and learn how business analysts collaborate with stakeholders to refine the backlog, compare options, and align solutions with measurable value.

Monitor changes in customer expectations and the outside environment on the strategy horizon, identify threats and opportunities, and decide whether to start a new initiative with the right team.

Portfolio kanban visualizes and manages multiple initiatives, increasing visibility into status, work in progress, decision criteria, and feedback for executives.

Explore the product roadmap as a high-level, agile guide that communicates vision, strategy, and alignment with stakeholders while outlining themes and features for planning.

Identify and define the problem, then build a minimal feature set and MVP to deliver maximum value quickly while testing hypotheses and gathering early customer feedback.

Map value streams to analyze the flow of information, people, and materials from discovery to consumer. Identify queue times to drive future-state improvements and reduce lead time.

Identify and evaluate solution options for the initiative horizon, facilitate team discussions, and align with strategic outcomes to maximize value with minimal features using impact mapping.

Identify and group user roles for writing effective user stories, focusing on hiring managers, recruiters, and candidates, grouping common functionalities like login and share, then consolidate roles and model attributes.

Define personas as imaginary representations of user roles, detailing templates, names, traits, motivations, and needs, then use ongoing user dialogue to refine them for better user stories.

Explore what user stories are and why use them in Scrum. Center the end user, foster conversation, and align business analysts with the development team to deliver high value.

Learn to write effective user stories using the who, what, why format, focusing on user personas. See real-world examples from recruitment and interviewing to clarify value.

Visualize the customer journey with story mapping to reveal themes, activities, and backlog items. Align teams and prioritize MVP releases using user stories.

The business analyst translates initiative decisions into a delivery backlog, writes user stories with who, what, why and acceptance criteria, and coordinates feedback, dependencies, and agile techniques to deliver value.

Define the product backlog as a living, prioritized list owned by the product owner. The business analyst coordinates content with stakeholders and uses MoSCoW or Kano analysis to maximize value.

Learn how analysts and product owners refine the backlog and prioritize user stories. Understand two refinement phases, definition of ready, time-boxing, and stakeholder alignment before sprint planning.

Invest criteria guide story splitting by focusing on independence, negotiability, and value. Create vertical, small, and testable user stories with clear acceptance criteria and rough estimates.

Showcase the completed sprint items during review sessions, gather stakeholder feedback on value delivered, and narrate a working software story that informs the next high-value steps through inspect and adapt.

Explore agile retrospectives to reflect on the last iteration, identify impediments and wins, and use start-stop-continue with data templates to derive actionable insights and decisions.

Facilitate stakeholder conversations as a business analyst by preparing with intention, guiding time-boxed meetings, and driving toward a shared understanding, clear outcomes, and actionable next steps.