The statement "In Scrumban, you need to break down the tasks as much as possible" is indeed a myth because Scrumban does not prescribe a one-size-fits-all approach to task breakdown. Instead, Scrumban encourages teams to find a balance in task size that optimizes flow, reduces risk, and increases transparency without causing unnecessary overhead in task management.I
n Scrumban, the emphasis is on visualizing and managing work in a way that aligns with the team's context and goals, rather than adhering to a rigid rule of breaking down tasks. This visualization is achieved by considering the complexity of backlog items without necessarily using story points. Teams in Scrumban environments often move away from story points, opting instead to break down the backlog into items that are relatively uniform in size. This approach provides clarity on the work and helps in forecasting and managing flow more effectively.When faced with a task that appears to be a week or more of work, it's not always advantageous for a single person to tackle it due to the risks associated with prolonged tasks, such as delays or challenges in handover if that person is unavailable. Instead, breaking down tasks into smaller, more manageable pieces allows for work to be pulled by cross-functional teams, supporting gradual feature testing and reducing the likelihood of tasks becoming bottlenecks.
Regarding the breakdown of the backlog, there isn't a universally perfect method. It's beneficial for teams to experiment with different task sizes and choose what yields the most accurate forecasting and smoothest workflow for their specific context.In summary, tasks should be broken down not to the smallest possible size, but to the extent that they support the team's objectives and enable a smooth workflow.
Tip: Setting a limit, such as 1-2 days for the implementation of each backlog item, can be beneficial. Larger items can carry greater complexity and risk, potentially creating bottlenecks. For those still unsure, consider exploring exercises like "Elephant Carpaccio" to experience the benefits of breaking down tasks effectively.