Working on a new platform development where future state process maps and list of features along with UI wireframes are already baseline. But now some stakeholders are evaluating current platform’s business rules and trying to incorporate the same into future state model resulting in tremendous changes to all the three baseline artifacts. Overall project schedule requires preparation of product backlog in next two weeks but new changes would mean constant rework on all baseline artifacts as well as product backlog if created. I am thinking of pushing back on two fronts 1.) Push the unnecessary changes to future state which brings it back to current state and reduces its efficiency 2.) Explain that product backlog will be based only on baseline artifacts and every change would be handled as a change request. Any suggestions on what additional options can be there or how this can be communicated back to the stakeholders? Saving Changes...
have you considered developing a story map to help the PO and other stakeholders trace from their vision to a set of personas, themes, epics & stories?
I find that technique is a good way to ensure folks aren't getting hung up on the "weeds" and it becomes a good basis of discussion for scope & release plans.
"We welcome change in Agile." If time and schedule constraints can't move, then it's just a matter of shifting priorities in the backlog. If the customer keeps making changes by adding new stories or changing existing ones, that will just mean some other stories will have to miss out (assuming the new ones are higher priority) or the goal post will have to move for time and/or schedule. Saving Changes...
