A retail buyer keeps emailing engineering leadership directly with feature requests instead of going through the Product Owner, and leadership keeps forwarding those emails straight into the Sprint Backlog. A consultant is asked to name the core Scrum problem with this pattern. What should the consultant say?

This scenario stacks two separate violations. First, retail requests routing around the Product Owner straight to leadership strip out the value judgment the Product Owner is accountable for — a buyer's request gets treated as automatically important because of who asked, rather than weighed against a firmware safety item or certification blocker already in the backlog. Second, leadership forwarding those requests directly into the Sprint Backlog bypasses the Developers entirely; the Sprint Backlog is the Developers' plan for delivering the Sprint Goal, and items land there through Sprint Planning or a Developer-managed process mid-Sprint, not by leadership injection. Calling this responsiveness mistakes speed for health — a fast pipeline that skips both the Product Owner's judgment and the Developers' planning just means bad decisions arrive quickly. Framing it as a tooling problem, email versus a ticketing system, misses that the issue is who is being bypassed, not which system carries the message. And routing the buyer into the Daily Scrum misunderstands that event too — it's a short, Developer-focused inspection of progress toward the Sprint Goal, not a stakeholder-request intake channel. A concrete check: can the retail buyer's next request be traced through the Product Owner's evaluation before it ever reaches a Sprint Backlog?