Azure For IT Professionals

Learn more about implementing Azure as part of your infrastructure.

Staying Sharp on Microsoft Office Can Save Time & Money

Learning the latest Microsoft Office tips and tricks can benefit you greatly.

"How do I determine if this new technology is for real?"

Michael Bird explains how to navigate new technology waters.

Training partners

Spindustry Training - (515) 334-9556

Bookmark and Share

Business Analysis in Agile Projects

Length: 2 Days
Tuition: $1,495.00

Schedule for this Course

There are no dates scheduled for this course.
If you would like to be added to the wait list for this class Click Here

Course Description:

This course is compliant with IIBA® and the BABOK®, including the recently-published Agile Extension.

Learn how to:

  • Understand the importance of business analysis in Agile projects
  • Learn how analysis adds business value for an Agile project's sponsors and customers
  • Define key roles and responsibilities of Agile team members
  • Discover the ways business analysis aligns with the principles of the Agile Manifesto
  • Explore the role of the business analyst in an Agile project
  • Realize the similarities and differences between plan-driven ("traditional") and change-driven ("agile") approaches, and how business analysis supports both
  • Discover how to use early and continuous feedback to drive change in your projects
  • Explore the various flavors of Agile: Scrum, XP, Kanban, Lean, etc.
  • Understand key concepts of Agile approaches such as backlogs, sprints and stories
  • Learn how to write effective user stories and define acceptance criteria for them
  • Investigate the techniques of story mapping, story decomposition and story elaboration
  • Discover the connection between user stories and use cases
  • Explore the concept of behavior-driven development
  • Build an effective discovery and delivery framework to help your Agile project succeed

Agile is changing the way we work
Traditional system-development methodologies are rapidly being replaced by more iterative or agile approaches. More and more organizations are realizing the benefits of faster product deployment at a lower cost, with less rework due to missed requirements. Effective business analysis is key to developing those requirements and keeping projects on track. This indispensable course explores the contributions of good requirements development in an Agile environment and equips business analysts with the critical thinking, analytical skills, and necessary people skills they need to add value to every Agile project.

"Agile" does NOT equal "no business analysis"
Business analysis is an essential function in every project, whether it be traditional, incremental or Agile. Effective analysis performed by competent business analysts can make the difference between successful and challenged or failed projects, even in an Agile project. This practical workshop provides participants with an understanding of the changing role of the business analyst, the tools and techniques best suited to Agile projects, and the timing for performing key tasks and events during the project.

Practice real-world tools and techniques for immediate application
This two-day course gives business analysts hands-on experience with proven techniques for discovering, understanding and describing product vision; understanding and depicting personas and user stories; identifying and describing additional requirements and acceptance criteria; modeling desired product features and functions; working collaboratively with other team members; and communicating expertly with colleagues, sponsors and business customers. Lively lectures combined with insightful demonstrations and realistic practice exercises provide you with the competence and confidence you need to improve project outcomes through better requirements definition. If you play a role in defining project scope or developing requirements on Agile projects, you can't afford to miss this course!

In-Class Group Exercises

A variety of demonstrations, large-group activities and small-group team exercises will refine and enhance your Agile business analysis skills. Working in small groups, you and your peers will identify, discuss and practice the tools and techniques your organization should be using to better define and communicate requirements for your Agile project.

Specifically, you will:

  • Evaluate a variety of Agile "flavors"
  • Review levels and types of requirements
  • Define the roles of Agile project team members
  • Practice defining personas
  • Work as a team to discover and write user stories
  • Review requirements elicitation and discovery methods
  • Understand story decomposition and modeling with simple graphical methods
  • Practice eliciting and validating information from project stakeholders
  • Assess the importance and priority of product features
  • Hone your problem identification, definition, and solving capabilites
  • Experience effective business analysis through learning games and simulations



Course Outline:

I. Agile Essentials

You've heard it all before: "Agile means developing software without any documentation"; "Agile means developers decide on a product's features"; "Agile is the same thing as scrum"; or possibly the most misleading concept of all: "Agile means we don't do business analysis any more and therefore we don't need BAs." Learn the truth about what Agile really is, what the variations and hybrids of Agile are, and how business analysis is critical to the success of your Agile projects.

  1. What is Agile?
  2. The Agile Manifesto and Guiding Principles
  3. A Variety of Agile Approaches
  4. Hybridizing Agile
  5. Which Agile is Right for You?
  6. Business Analysis for Agile Projects

Practice Session

We’ll present a series of stakeholder meetings and examine the results. Once product vision, personas and user stories are defined, we’ll ask the following: “What’s missing? Can we develop from this?” Starting here, begin developing an understanding of Agile business analysis.

II. The Agile Business Analyst

As more and more projects are undertaken using Agile approaches, it's critical for a business analyst to understand the tools, techniques, skills and knowledge required to make those projects successful. In this section, we'll review some basic concepts of requirements development and revisit the underlying competencies that become more important as we move toward conversation and interaction and away from rigid process. We'll work to understand which techniques are best used on Agile projects and how to adapt them when needed. Finally, we'll evaluate the changes we need to make in our business analysis process to ensure our project's success.

  1. The Role of Business Analyst in Agile Projects
  2. BA Underlying Competencies
  3. Review of Requirements Basics
  4. It's Still About Asking the Right Questions
  5. Business Analysis Techniques: Some You Know and Some New Ones
  6. Mapping BA Techniques to Agile
  7. Guidelines for Agile Business Analysis

Practice Session

The class will perform a question-generating exercise to clarify user stories from Scrum simulation. We’ll then discuss which techniques will elicit and clarify requirements and acceptance criteria for those stories.

III. The Product Vision

Successful projects begin with a clear definition of scope--the "big picture." Even Agile projects need some kind of a starting point--we may not know or see all of the details, but we should at least have a sense of the overall vision of a product or solution. This section explores how to begin an Agile project by identifying key project parameters and high-level components.

  1. A Framework for Assessing Business Needs and Value
  2. Defining the Product That Solves the Problem
  3. Building a Product Roadmap
  4. The Importancce of Release Planning
  5. Stakeholders, Actors and Personas

Practice Session

Working with a hypothetical but realistic case project company, you and your team will put your analysis skills to the test as you conduct a guided assessment. You'll define and document the business environment, clearly describe the scope of the business, and perform a straightforward analysis of a proposed business opportunity. Finally, you'll assess and describe the project's stakeholders, actors and personas.

IV. The Voice of the Customer

The "customer" is the individual who gets value from the product we are building. In order to understand the required capabilities of the product, we need to consider the customer's goals and then decompose these goals into more and more detail. This decomposition eventually reveals low-level requirements and acceptance criteria for them. In this section, we'll explore this process of goal decomposition.

  1. Concepts--Goals, Themes and Epics
  2. User Stories
  3. Use Cases
  4. Story/Feature Mapping
  5. Story Decomposition
  6. Story Elaboration
  7. Defining Acceptance Criteria
  8. Storyboarding for Validation

Practice Session

Working with our case project, you and your team will identify and develop the themes, epics and user stories that describe our customers' required capabilities. You'll use your best analysis skills to elicit additional requirements and acceptance criteria for your stories. Finally, your team will create a storyboard to validate what you think you already know.

V. Prioritizing for Business Value

Agile projects continuously assess and prioritize features and capabilities that add the most business value to customers at a particular point in time. Those that have the highest value are built and delivered in the current sprint while the remaining items are placed into the product backlog. In this section, we'll examine some concepts, tools and techniques for prioritizing capabilities and managing the backlog.

  1. What is a Product Backlog?
  2. Prioritizing Items for the Backlog
  3. The Importance of Sprint Planning
  4. Managing and Grooming the Backlog

Practice Session

Working with your team, you'll evaluate and prioritize your user stories and create a sprint plan.

VI. Clarify with Examples: Moving Toward Behavior-Driven Development

Sometimes our customers themselves are unsure of what they really want or need a system to do for them. Here is a great opportunity for an Agile BA to use real examples to communicate how the product can serve the customer's need. In this section, we'll explore a simple yet effective technique to draw out additional requirements via examples.

  1. Understanding Behavior-Driven Development
  2. How Real Examples Bridge the Gap
  3. Using Analysis Models for Elaboration and Clarification
  4. The "Given/When/Then/And" Technique

Practice Session

You and your team will clarify requirements for our case project using real examples.

VII. Collaboration and Continuous Improvement

Successful Agile projects depend on communication and collaboration among team members. So much of our work is done in face to face facilitated sessions where good communication, trust, and teamwork become increasingly important. As we continue to work together to deliver value to our customers, we also need to consider how we might maximize our own process so that future iterations or sprints go more smoothly.

  1. Creating a Safe Working Environment
  2. Using Collaborative Games
  3. The Importance of Stand-Ups and Sprint Reviews
  4. Retrospectives: Lessons Learned
  5. Toward Continuous Improvement

Practice Session

Teams will participate in a fun and energizing game intended to demonstrate the importance of communication, collaboration and teamwork.

20 Immediate Benefits of Participating in this Workshop

  1. Explore the vision of Agile, the Agile Manifesto, and Agile principles
  2. Understand how business analysis fits into the Agile environment and why it's essential for project success
  3. Gain exposure to a variety of Agile approaches and learn which is right for you
  4. Increase business value to your project's sponsor and customers
  5. Discover how to define personas and user stories
  6. Analyze user stories for additional requirements and describe them effectively
  7. Experience a variety of analysis tools and techniques used on Agile projects
  8. Ensure the right information is available to your development team at the right level of detail and at the right time so they build the right product
  9. Understand the relationship between user stories and use cases
  10. Realize the importance of release and sprint planning
  11. Optimize your Agile project experience by incorporating stand-ups, sprint reviews and retrospectives
  12. Gain exposure to proven tools and techniques for defining product vision
  13. Understand what deliverables might be produced in an Agile project
  14. Improve your questioning, listening, elicitation and validation skills
  15. Collaborate effectively with project stakeholders and team members
  16. Help to bridge the gap between business customers and designers, developers, and testers
  17. Overcome common pitfalls and traps encountered on Agile projects
  18. Enhance relationships with stakeholders throughout your organization and improve your ability to satisfy stakeholders from both the business and IT organizations
  19. Help your organization understand and successfully apply Agile approaches for analyzing and solving business problems
  20. Discover tips and tricks that have helped other business analysts be successful with real-world Agile projects

back to top