Are Product Owners and Business Analysts Different? with Hal Hogue and Misi Eyetsemitan

Published: July 15, 2022, noon

This week, Dan Neumann is joined by two colleagues, Hal Hogue and Misi Eyetsemitan.

\xa0

In this episode, they explore a question that came up in a Coaches\u2019 practice recently that was about the differences between a Product Owner and a Business Analyst. Are both the same? Do they have different business accountabilities? How do both enter the big picture?

\xa0

Key Takeaways

\u25cf Product Owner and a Business Analyst are totally two different roles.

\u25cb They vary by responsibility and by definition of functions; they are two entirely different roles.

\u25cb Both roles can help in the accountabilities of Scrum.

\u25cb Exploring the history, we traditionally had Business Analysts and Project Managers. The Scrum Framework does not have either of these titles. this

\u25cb The Product Owner focuses on the vision and the profitability/marketability of the product (all about value).

\u25cb The Scrum Master is all about the framework.

\u25cb The Development Team has the accountability to develop the product and the process that will ensure that the product or task is addressed in an achievable way.

\u25cb Business Analysts can help the Scrum Team by making sure that the backlog is representative of the vision of the product and the input of the users, stakeholders, and the Developers.

\u25cf Business Analysts are valuable when there is a scale in Agile.

\u25cb When there is a robust product that has multiple Teams working on it, a BA is valuable.

\u25cf Is the need product- or experience-driven?

\u25cb The answer may depend on the organization and on how Teams are set up. If the organization already has the operational role of a BA embedded within the Scrum Team, you can\u2019t ignore it, it is part of the structure of that Team.

\u25cf Exploring each Team member\u2019s accountabilities and responsibilities is a great way to prevent problems and safely scale. The Herculean Doughnut is an effective practice to determine roles and their reaches.

\xa0

\xa0

Mentioned in this Episode:

Learn more about the Herculean Doughnut

Zombie Scrum Survival Guide, by Christiaan Verwijs

Find what Dan Harmon\u2019s Story Circle is about.

\xa0

Want to Learn More or Get in Touch?

Visit the website and catch up with all the episodes on AgileThought.com!

Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!