How to Estimate Partially Completed User Stories.

Join this channel to get access to perks:

@BeingAgile Consulting
#agile #scrummaster #interview #projectmanagement #productdevelopment

Hey lovelies, thank you so much for watching!
If you are looking to explore the Agile Coach/Scrum Master/RTE career path, if you are struggling with conquering that interview, if you are struggling with doing your job and you need a mentor/coach to guide you through this journey, we can help you!

For Mentoring/Coaching services, please visit our website to learn more:
Instagram: BeingAgile_Consulting
FaceBook: BeingAgile Consulting
LinkedIn: BeingAgile Consulting

Great practical books for practicing and aspiring Scrum Masters:

DISCLAIMER ALERT: Some of the links in this description may be affiliate links which means that if you purchase this product through these links, we will get a small commission at no additional cost to you. Your purchase is a way of expressing your support to this platform which really encourages us to want to bring more rich contents to you every week. Thank you so much

DISCLAIMER: This is not a sponsored video

If you have a question/input regarding this video, please leverage the comment section.

@Karen Fomafung - Your Agile Evangelist

[ntuifamgerman]

Hey Karen, please we need a video on technical debt, cycle time and lead time. Thanks

[judicaeldjomo]

Karen, I agree with your approach 1000%. I have had this issue with my teams before. Thanks for your insight.

[cyrielletchaya]

You GOD sent🤣🤣🙌🙌. It's like you knew I needed this video rn!!

[victorseaba]

Regardless how you explain this capacity or velocity driven approach (arguable means the same). It is important that user stories are properly refined which in turn will help with accurate estimation.

A user story/ticket may be incomplete within a sprint for several reasons. Whatever the reason, I’d strongly advise re-estimation for the following reasons:

1. If no work was done on the ticket within the sprint due to underestimation of the effort required to do the work, then the best approach is to refine/breakdown the story to achievable chunks of work and re-estimate.

2. If the team suffered unavailability of a team member due to unforeseen circumstances within the sprint, the ticket should be re-estimated to make sure that the effort required to complete the ticket remains the same (or may have changed due to new information about the ticket).
3. If work was done on the ticket but the team discovered dependencies, the ticket should be re-estimated because some work has already been done, a new dependency has been identified and the effort required to complete the ticket may have changed.

Whatever the situation, any ticket that is not finished within a sprint should be re-estimated. This will also help you accurately manage stakeholder expectations.

[justechos]

Hi Karen, nice video. What is the difference between capacity and velocity based planning, in the long run will velocity not equal capacity? Also when story pointing, do you convert story points to hours within a team so we all know what to expect when we say a story is 5story point for example. Thanks for your videos .

[gregmester]

I enjoyed your topic. At a level of truth it does not really matter as we typically use a 3 sprint average. So the effort to re-estimate is not valuable. Plus I would rather the team to get done sooner and close out all the work in the Sprint Backlog. This allow the team to celebrate as a team and gives them time to figure out why the stories were not done in the prior sprint and take some real time to root cause the problem if it is a major problem with multiple stories. Last please be careful as Points have no real business value and so many people misunderstand this and those people in my opinion are the ones trying to repoint stories.

[_onyinye_chi_]

Hi Karen, is it possible to do a video showing how to reestimate on Jira? Probably showing how to estimate an unfinished work on Jira

[learningandentertainmentce]

Tell us what you understand by TDD & TBD and how these work in an agile environment.

[learningandentertainmentce]

What is the difference between Azure Devops and Jira and which would you say is the prefered one

[abhishekpanthangi]

How do we calculate the velocity for a project ?

[learningandentertainmentce]

As a Snr. SM, how would you coach and mentor fellow Scrum masters?

[themfamily]

This video explains why Ron Jefferies apologized for inventing story points, organizations are abusing it. Story pointing is one of Agile's most popular hacks. Don't do it, really don't just do it because it's a lot wrong. Think about it this way, all that time you spend estimating and re-estimating and planning is a whole waste of time because what are you not doing then? Working. That time could otherwise be spent delivering customer value. The more time you spend planning and estimating, the less value you are able to deliver. Estimation makes you less predictable in software development. Just think about how many times you are interrupted for Estimation and how much time that costs?

[ashishkatariya]

The partially completed user story doesn't meets the Acceptance criteria also will not add any value take it as a spill over.