Hello @Diego Galan ! Welcome to the Atlassian Community!
IN GENERAL, it sounds like you have a lot going on!
If I read this right, you are responsible for releasing new functionality (set up as tasks) while at the same time doing support in the production environment. That sounds like your teams are drowning in a lot of work!
A few things to ponder before we talk about Scrum vs. Kanban:
1. Does your team have a good idea of the things that need to be done before the task is accepted into the sprint? It sounds like they don't and are finding out that it's too much, which means it keeps moving to future sprints.
2. Does your team have an idea of its capacity? This usually may come from story point velocity or number of t-shirt sizes. How do you know your team has an appropriate load?
3. This capacity is definitely being affected by the unplanned work (the production tickets). What's the nature of the unplanned work?
Scrum looks at delivering work by the end of the sprint. To do this, teams have to have an idea of how much work they can take. If there is confusion and creating of subtasks during the sprint, the work is not clear or it's too big. Your team should look at breaking it up.
If you move to Kanban, that may not be a "magic solution" because you have a lot of unplanned work coming in. You have to make sure that your team can focus otherwise they'll be drowning (like they are right now!)
Tell me more about how your team is planning their work, estimating effort, and judging their capacity.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.