My current project started as a simple website refresh, but now the stakeholders are asking for an integrated chatbot and a full member portal. We are working in two-week sprints, but the Product Backlog is growing faster than we can close tickets. How can a BA effectively push back without damaging stakeholder relationships?
3 answers
I always use the "Change Request" log even in Agile. It sounds formal, but documenting the "Why" and "When" of a new requirement helps hold people accountable later on.
Scope creep often happens when there isn't a clear "Definition of Ready." As the BA, you need to implement the MoSCoW method (Must-have, Should-have, Could-have, Won't-have) for every new request. When a stakeholder asks for a chatbot, ask them which "Must-have" feature they are willing to trade for it to maintain the release date. This reframes the conversation from "No, we won't do it" to "Yes, we can do it, but what is the priority shift?" Visualizing the "Impact vs. Effort" matrix during backlog grooming sessions also helps stakeholders see the cost of their requests.
Does your Product Owner back you up when you try to prioritize the backlog, or are they the one saying "Yes" to everything? The relationship between the BA and PO is crucial for scope control.
Dennis, that is the million-dollar question. In many cases, the PO is under pressure from the C-suite and says yes to avoid conflict. As a BA, your job is to provide the "Data" to the PO—show them the burndown chart. If the team's capacity is 40 points and the PO just added 60 points of "Critical" work, the math simply doesn't add up. Presenting the capacity constraints as a logical reality rather than a personal refusal makes it much easier for the PO to have those tough conversations with the upper management.
I like that, Donna. It provides a historical trail so when the project is late, you can point to the 15 "new" features that weren't in the original vision.