What Business Analysts Should Know About Agile
Agile has transformed how we approach software development and project delivery. But for many business analysis professionals, it remains a tangled web of conflicting expectations, misunderstood roles, and vague buzzwords.
In a recent episode of Business Analysis Live, I sat down with Kent McDonald—freelance product manager, author, and longtime agile coach—to unpack what Agile really means for business analysis professionals today. Together, we explored the evolution (and dilution) of Agile practices, the confusion around roles like Product Owner and Business Analyst, and how professionals can navigate Agile environments without getting lost in jargon or rigid frameworks.
If you've ever felt boxed in by "the Agile way" or wondered how to demonstrate your impact as a business analysis professional—this episode is for you!
Understanding the Agile Shift
Agile wasn’t always the juggernaut it is today. As Kent shared, it started with a simple goal: to help teams deliver better software through collaboration, iteration, and adaptability. But over time, it became both a marketing term and a box to be checked, often losing sight of the principles that made it effective in the first place (a familiar story).
The result? A pendulum swing. Agile was once criticized for being chaotic. Now it's accused of being too rigid. Business analysis professionals often find themselves caught in the middle.
What Business Analysts Should Really Focus On
1. Agile isn’t a religion—it’s a means to an end
The value of Agile lies in its ability to help teams learn quickly, collaborate effectively, and deliver meaningful outcomes. Kent reminds us that Agile isn't about following rituals. Instead, it’s about adapting to your context.
2. Avoid the method trap
Business analysis professionals can sometimes get boxed in by method. Whether it’s Scrum, SAFe, or some hybrid model, don’t lose sight of your purpose: understanding problems, supporting decision-making, and enabling outcomes. Process is a tool—not a goal.
3. Your role might not be defined, but do the work anyway
Many Agile frameworks don’t explicitly call out business analysis. But that doesn’t mean the work isn’t needed. Understanding the problem space, engaging stakeholders, and modelling processes are still crucial. Sometimes, you’ll need to lead without a title (scary, I know). And sometimes, you’ll need to do the work without waiting for permission.
4. Talk about outcomes, not value
“Value” is vague. Business stakeholders and executives are more interested in results, outcomes, and impact. Want your work to be taken seriously? Understand how your organization makes and spends money and speak that language. Link your work to the goals your organization invests in and show how you help drive them.
5. Context is everything
Agile isn’t one-size-fits-all. The approach that works for a two-person startup likely won’t work for a 2000-person enterprise. Good business analysis professionals consider the context and tailor their contributions accordingly.
6. Collaboration is your collateral
Kent emphasizes that one of the most important contributions business analysis professionals make in Agile teams is facilitating effective collaboration. Whether that means designing better stakeholder meetings or clearing communication roadblocks, business analysis professionals can create the conditions for teams to learn, adapt, and deliver.
The Role of Business Analysts in Agile Teams
As I mentioned earlier, there’s often confusion between roles like Product Owner and Business Analyst. Kent’s advice? Stop worrying about the label. Instead, understand what your team needs, what your organization expects, and where you can make the biggest impact.
Roles can often be just as limiting as models or frameworks. Whether you’re helping define scope, clarifying goals, or uncovering user needs, your business analysis skills are valuable—even if no one calls it “business analysis.”
Business analysis professionals are everywhere, after all, and they come in all shapes and sizes.
Working Better
Agile isn’t about stand-up meetings, user stories, or ceremonies. It’s about better ways of working. For business analysis professionals, that means stepping into a leadership mindset, focusing on outcomes, and creating environments where teams can succeed.
You may not always be invited to do the work that matters—but you can always choose to do it.
Want the full story?
Listen to the complete episode of Business Analysis Live with Kent McDonald to hear real-world insights, humorous takes, and practical tips for navigating Agile as a business analysis professional.
Are there topics or trends you’d like us to explore? Share your ideas with me and help shape the conversations that matter. And don’t miss a single episode—subscribe now to stay in the loop.
Until next time, stay agile and keep delivering—catch you in the next iteration!
About the Author
Susan hosts Business Analysis Live to discuss business analysis topics and answer questions from the live audience. There's a backlog of upcoming topics and she's happy to take suggestions. Add a comment to one of our videos to suggest a topic you would like Susan to cover in an upcoming episode or connect with her via email at live@iiba.org.
