My company is transitioning to Scrum and they are telling the BAs that we are now "Product Owners." However, I feel like the roles are fundamentally different in terms of decision-making authority. Can a BA effectively act as a PO if they don't have control over the budget? How do you navigate the "BA in a PO role" trap without burning out or losing the respect of the development team?
3 answers
This is a classic "Agile Anti-pattern." A Product Owner is a decision-maker who owns the ROI, while a Business Analyst is a researcher who supports that decision-making with data. If you are a "BA as PO" but can't make the final call on the roadmap, you are actually a "Proxy PO." To survive this, you need to establish a very close relationship with the person who does hold the budget. Your job is to make their life easy by presenting options, pros/cons, and data-backed recommendations. You handle the "tactical" backlog refinement, while they handle the "strategic" vision. It’s a partnership, not a replacement.
Does your Scrum Master support you in setting boundaries with stakeholders, or are you being treated as a personal secretary for their requests?
Focus on the "Product Backlog Refinement." That’s where the BA skills truly shine in a Scrum team, regardless of what your official title is.
I agree, Jennifer. Backlog refinement is the engine room of Scrum, and a good BA makes that engine run smoothly for everyone else.
Robert, the Scrum Master is actually part of the problem—they keep saying "The PO will handle that" whenever a stakeholder has a random idea. I need to have a sit-down with the SM to clarify that my role is to analyze the value of those ideas, not just say "Yes" to everyone. I want to move toward a more disciplined intake process where every new request needs a basic "Business Value Statement" before I even spend time documenting it. This should help me protect the team's velocity and my own sanity.