In my teams at the moment they did never reach there goals. it is mostly 60-70% of what we planned. The product backlog Items are too big for one sprint and it obviosly Not possible to make them smaller. Most of them are moved to the next sprint then. We have two Week sprints but releases every 3 month, sometimes in the middle of the sprint.
What would you recommend?
I was thinking about to switch to a mix if Scrum and kanban. we are developing a Quite complex standard software for public administration.
Thank you very much
“The product backlog items are too big for one sprint”
Remember that the PBIs are not the core thing in Scrum, its the Sprint Goal, which is a stepping stone to the Product Goal.
It’s not some random bundle of functionality, or a set of requirements, it’s an experiment to explore product-market fit.
“Not possible to make them smaller”
What’s the barrier to making them smaller?
Are you using Jeff Patton’s approach to user story mapping?
Do you apply all of the story-slicing patterns?
Does the architecture need to be reworked?
Maybe try a “magic wand” retro or an Ishikakwa fishbone exercise on this?
“Recommend Scrum with Kanban”
If you are not doing product innovation I’d always suggest this, but NOT as a way of getting out of having Sprint Goals, a Product Goal and a roadmap.
The only exception there might be a compliance project where the requirements are known and you are implementing “policy as code”
But – Kanban won’t help you split the items smaller, and you still need to do that….