Help team building
My scrum team is new. We are in our second sprint and even my team is advancing they are working every one on separate stories. All stories are "almost finish" any one is finish yet.
I am trying to make them understand to get the job done by priority and focus on fast delivery.
Any advice, agile game to help them focus?
why not play the Marsmallow Challenge with your team?
After the challenge your team can discuss your concern from a different point of view.
Maybe a bit of a bite out of the budget, but how about taking your team to a real flight simulator where they have to work together in order to fly and land a plane safely.
It sounds as if your team is in the forming phase (forming-storming-norming-performing) - I'm sure there are team building exercises, etc. that you can utilize to help them transition, but there's no short cuts to teams 'working things out'...sometimes it best to stand to the side and ensure everyone is moving in the same direction-as best as possible.
Have you talked with the team about limiting work-in-progress, and using techniques such as pair programming to improve focus and throughput?
Has pair programming been tried before or are they afraid without trying?
Maybe a reminder on the benefits of limiting WIP would be great, if not done yet. Or simpler, as a Team how could we improve the speed to deliver a user requirement faster?
How does the Product Owner feel in this situation? Would he feel better to receive smaller pieces regularly with maximum value to give to the end users (with the highest priority)?
They are afraid without trying pair programming.
Minimizing wip it is something i ve been talking to them, and explaning beneficts and "better feeling of the client" with smaller pieces delivery.
PO feel good because he only cares about final delivery of sprint. I ve been working with him too about continuos small delivery and the advantage of been able to check something sooner into the sprint and getting his initial feedback.
I am curious of what stop them to try new things to improve as a team. Like the Scrum Guide states:
Scrum makes clear the relative efficacy of your product management and work techniques so that you can continuously improve the product, the team, and the working environment.
Scrum offers a safe place to improve. Why don't they want to take the opportunity given to them?
Another thing I am curious is the adaptation they work on at every single sprint. During the previous sprint, as a Scrum Team, did you identify at least one potential improvement?
Yes, we did identify potential improvements. Like, tasking better, aovid some re working.
But they still dont try to work together on one small thing. They feel it will be slower.
That is why i am looking for some exercises to demostrate it is not necessary slower to work together and minimize wip.