Hi @Cristina Ygarza -- Welcome to the Atlassian Community!
Based on this browser translation of your question:
Can a sprint be blocked so that new User Stories cannot be included?
I know it's not the best way to do it but we have difficulties getting people to adapt to working with sprints and we have thought about this desperate measure.
The idea is to do it while the sprint is active.
Although there may be ways to do this by limiting permissions or using automation, I recommend not doing so.
Instead please consider the root cause to why people are adding stories to the active sprint. These could be many things, such as:
- backlog refinement (or sprint planning) problems, and so the planned work is not aligned with capacity or product owner needs
- the team has production support responsibilities, and so just-in-time, urgent work arrives
- challenges with focus
- challenges with task switching and amount of work in progress (WIP)
- challenges with work completion and definition of done
- learning gaps of Scrum value and practices
- etc.
I recommend meeting with the team to discuss this symptom, reviewing recent sprint data, and perhaps using a technique like 5-Whys to uncover and develop experiments to address the cause. The team's scrum master / agile coach can help with that.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.