Applying Scrum to a Template-Based Product Backlog: Handling Frequent UI/UX Updates
"Hi everyone,
I am currently working on a project called Funnelsflex, where we develop high-performance sales funnel templates. As our library of templates grows, we are finding it challenging to manage the Product Backlog effectively using Scrum.
Specifically, we face a lot of 'Emergent Work' due to frequent UI/UX browser updates and changing marketing automation APIs. My question to the community is:
How do you manage a Sprint when a significant portion of the work is 'Refinement' of existing templates versus building new features? Does anyone have experience using Scrum in a high-volume digital asset or marketing template environment?
I'm looking for advice on how to keep the Sprint Goal focused when maintenance of previous templates starts to compete with new development.
Looking forward to your insights!
Best regards."
It's not clear to me what the problem is.
Is this "emergent work" to "refine" the existing templates critical and interrupting the planned work? If so, is there any reason why it can't go on the Product Backlog and be ordered for a future Sprint instead?
If the work isn't interrupting the team, I'm not sure why the Sprint Goal isn't a focusing tool for the team. If so, I'd like to understand what can be done to minimize those interruptions. That could mean identifying the work before it becomes critical, so it can be planned rather than interrupting the team. Or it could mean restructuring the work. But knowing the types of work the team faces and the impediments to planning a Sprint can start those conversations.