- Company politics and bureaucracy that delay tickets
- Managers need to help the Team talking to other managers and finding the way through
- Knowledge restricted to few people in the team
- Teams to become cross-functional
- Promote: Technical discussions, Dojo sessions, Documentation with clear steps on what to do, Grooming Sessions, Pairing to do the work
- Environment issues that end with Engineers doing far more work than expected
- Each team should have time allocated for improvements (5% capacity for IS Projects?)
- Maybe an IS Project is needed to sort out problems
- Poor requirements force Engineers to chase Customers
- Avoid tickets to get into your Ready column if requirements are not clear
- Improve your Catalogue maybe with some information being mandatory
- Lack of planning on dependencies with other teams
- Interaction with teams that are not doing Kanban takes time as they are not working based on priorities and there is no coordination
- Lack of Automation
- Each team could have time allocated for improvements (5% capacity for IS Projects?)
- Customers requesting more work than originally requested on the same ticket
- Customers need to be educated to open a new ticket or we can open a Request for them.
- Team members feel bad about telling this to customers and end up doing the work. Managers could help here.
- Tickets are too big(almost a project)
- Break tickets into smaller ones that are easier to estimate and as a project easier to keep track and deliver it on time
- Ticket workflows not properly defined
- Talk to your Team to find where they lose time and if they are acting as intermediaries between parties.