So I know that this question has been asked before, but since I haven't really seen anything that benefited my problem, I thought I would give it a chance.
So first things first, in a perfect world we would be completing sprints and at the end of every sprint, we will deliver all the story points that we have committed to. I know that it is not always attainable, so a 90% delivery to me is still acceptable.
The problem I am facing at the moment, is that we commit to (For arguments sake) 100 story points, but only complete 20. This becomes a nightmare as trying to manage the client becomes almost impossible. Now the logical thing to say here is that we are over committing each sprint or underestimating stories which is very possible.
Just to explain the process, maybe I am missing something,
- We have 2 week sprints
- During sprint, product team gets requests from the client and do requirements gathering, running details past the team/tech lead prior to prioritizing the backlog (We don't have a dedicated grooming session, however stories are fleshed out properly prior planning 1)
- Thursdays of every second week, we do planning 1. This session is run by the product team, we try to estimate as much of the stories on the backlog as possible, backlog is ordered based on the current priority.
- Fridays of every second week, we do planning 2. This session is run by the Team lead, expectation is that the team took some time between session 1 and 2 to go through work required in order to adjust estimations, but we go into more technical detail of the change required
- Planning 1 is for initial estimations, this can change during the planning 2 session
- The team is left for 2 weeks, there are cases where scope creep occurs, however try to limit it as much as possible as we have a dedicated Developer to work on production issues that is not part of sprint work
The problems I am facing are the following,
- Team does not communicate that they will not make sprint deadlines
- Team seems to not fully understand the features that are requested (Could speak to lack in requirements, however I don't fully think so)
- Team takes too long to develop features, going over the expected delivery estimation.
- Team does not take the initiative to go through future stories during the gap between planning 1 and 2
I know that this is a very common issue in software development, however it is an extremely frustrating one as you struggle to build confidence with your client if you cannot deliver on time. Just to give context on myself, as that might have a direct influence. I am currently the SDM for multiple teams, due to a bit of a lack of technical understanding (Team/Tech lead) in some teams, I am quite involved with some planning sessions. I come from a senior developer background, have been developing software for about 10 years.
Team in question, can differ in size, but 10 Developers, 3 QA, 2 Product, 2 Team Leads.
Sorry if this is a duplicate question, I have checked the other questions and answers and thought it made more sense to post a new question.