Hi everyone,
I’m curious how other Agile teams deal with feature requests that keep changing during a sprint.
We’re working on a SaaS product for digital membership card, and every client has different priorities. Some ask for Apple Wallet and Google Wallet support, others want loyalty rewards, QR check-ins, or CRM integrations. The backlog keeps growing, but the sprint capacity stays the same.
We’ve tried prioritizing based on customer impact and business value, but there are still times when urgent requests appear halfway through the sprint.
Has anyone found a process that works well for situations like this?
- Do you allow mid-sprint changes?
- Do you use WSJF, RICE, MoSCoW, or another prioritization framework?
- How do you explain to stakeholders that some requests need to wait?
We’ve been looking at products like MembershipAnywhere to understand how mature membership platforms balance new features with ongoing development, but I’d really like to hear real-world experiences from Agile teams.