Skip to main content

Challenges in consistent predictable delivery?

Last post 07:42 pm June 12, 2020 by Daniel Wilhite
3 replies
11:47 am June 12, 2020

I have recently joined an organization that is experiencing challenges in predicting the delivery from its dev team, and I want to help them team back on track. So my manager asked me to report with a plan:

1. What is the approach I need to take?

2. What are the tools or techniques that I have to use since they already started practicing Scrum?

3. What do I need to focus on for the next few sprints? 

Can you please share your thoughts?


05:36 pm June 12, 2020

In my opinion, you should have the team discuss and do a root-cause analysis of the issue in the retrospective. It can be pretty much everything, i.e. a lack of availability of the Product Owner leading to uncertainty during the Sprint, a high level of technical debt, a lack of knowledge or availability in the development team, or many other reasons...

The tools, techniques or focus will depend on the root causes.


06:33 pm June 12, 2020

The team should deliver a valuable increment of release quality each and every Sprint. There's your prediction.

If the team can't do that, what is their plan to "get back on track"? If they cannot create such a plan themselves, why not?


07:42 pm June 12, 2020

If you volunteered to do this you should have some ideas.  What were they?  Which of the Scrum Roles will you be fulfilling? 

Give us some of that information and we will be able to provide you better guidance. 

In the meantime you might also want to read up on things like cycle time, lead time, limiting work in progress, velocity so that you have some basis for identifying your plan. 


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.