Ah, it is the old "change the data to make it look pretty" approach. :) You are very right about training. This is what your burn up/down looks like ... in a perfect world. You have to listen to what the data is telling you. That analytical step is definitely missing or glossed over. In your example, could the team create a sprint(s) dedicated to the business reviewing the work? I'm thinking more SAFe I think. Sprint, sprint, sprint, review sprint, release?
Yes, I think a more SAFe like approach would work well for them. Maybe its a reverse discipline problem? When moving from Scrum to Kanban, make sure you have the discipline for Scrum well in hand as you need more for Kanban. Perhaps if you're struggling with the discipline of Scrum, you should move to SAFe because it has more rules and structure?
Ah, it is the old "change the data to make it look pretty" approach. :) You are very right about training. This is what your burn up/down looks like ... in a perfect world. You have to listen to what the data is telling you. That analytical step is definitely missing or glossed over. In your example, could the team create a sprint(s) dedicated to the business reviewing the work? I'm thinking more SAFe I think. Sprint, sprint, sprint, review sprint, release?
Yes, I think a more SAFe like approach would work well for them. Maybe its a reverse discipline problem? When moving from Scrum to Kanban, make sure you have the discipline for Scrum well in hand as you need more for Kanban. Perhaps if you're struggling with the discipline of Scrum, you should move to SAFe because it has more rules and structure?