The biggest problem I have right now is the team is unable to commit on the stories and tasks planned during a sprint.
For example, we wanted to implement a new database, which is very complex and we have a number of possibilities. We knew we had to find out how we could implement the database, and searched for awhile, but after three weeks during the sprint demo we had nothing to deliver and it was communicated only at that moment.
They don't seem to comprehend that they have to deliver what was talked about in the sprint planning, that they have to talk about the fact that they can't deliver something during the daily stand ups, and that they can change or not respect the scope of the sprint.
How do I get them to understand that they should commit on what they planned during the sprint planning, so that they are more capable of planning their next sprint and respect what they planned?
- I tried putting up a visible burndown chart with post-its but it takes so much time to write all the user stories...
- Force them as a team to create the tasks during the sprint planning (before the last sprint, I would be showing them jira on a projector and a team member would tell me what they would do, while the others would not be listening).
- I'm also trying to put shorter sprints (from 3 weeks to 2), but I'm receiving a lot of challenge from my team lead: he says at 2 weeks they are not able to deliver anything, but in my opinion they are not able to deliver enough in 3 weeks sprint also.