Learnt a lot... I started my career on software product management this year, and I am currently managing a team. It wasn't funny, as a new team, I actually do face to face valuation of each member having my UI design, and story. I ask question like, are you comfortable with this task? He will give his opinion and we will engage our self until I find out how long in days he can fix the task. from his capacity I did develop a 1day is to 1 story point. Then I repeat for the rest of the team. I continued repeating the same strategy until I got my 5 sprints. That's when I started using the average velocity which I feel comfortable with though not smooth due to the team experience but better. Thank you for your video.
@AishaTech655 Жыл бұрын
Thank you so much for sharing your experience, I am glad you were able find what works for your team 🙏🏾🙏🏾🙏🏾
@tinnakash Жыл бұрын
Thank you Aisha for being consistent with helping people. I am glued to this channel
@AishaTech655 Жыл бұрын
Thank you, I appreciate it 🙏🏾
@yvettembih5415 Жыл бұрын
Thanks Aisha, we just moved from estimating from Hours to story points and this came in handy.
@AishaTech655 Жыл бұрын
Thank you, I am glad it helpful 🙏🏾🙏🏾🙏🏾
@alexanderleanzabhnsdalen88473 ай бұрын
Hi, thank you for the nice explanation!! 😊 regarding the last part of past average velocity to be used as reference for a sprint planning and people on holidays, i do not understand the mathematics, how you do? So let’s say: Sprint 1 : 100 points (all team present) Sprint 2 : 50 points ( 60% of the team is present, this is 60% of the total working hours for that team due to holidays) Sprint 3 : 100 points ( all the team present) Average velocity: 250/3 = 83 points So now I go to planning Sprint 4 but only 50% of the team is present. Would you still use 83 points as average to plan which includes past holidays? Is there some mathematics to use to suggest some number to plan? or only ask the team how they “feel “about it? Does it make sense to do the following? Sprint 1 = 100 points ( all team) Sprint 2 = 83 points (50 points /0,6), this is a number adjusted to full capacity as if the whole team would have been present. Sprint 3 = 100 points ( all team present) Average adjusted to full capacity = 95 points So in sprint 4 if 50% of the team is present, then I would propose in planning = 95 *0,5 = 48 points. Does this makes sense? Or just average 83 points*0,5 = 41 points to propose in planning? How you handle average velocity (which includes past absences) to use to proposed in planning and people off in next sprint in a mathematical way in this situation? I hope I am understood.? 😅
@AishaTech6553 ай бұрын
I need to do a video on this 😃😃😃😃, but to answer your question your first scenario I will not insist on 84 as the team dynamic is not the same. Also go with how the team feels.
@alexanderleanzabhnsdalen88473 ай бұрын
Hi! Thank you for the quick answer 🥳, ohh got confused about the 84? 😅🙏 But then aside from feelings if is a big team can be a bit confusing, so if I wanted to propose a number for sprint 4 with 50% of the team, would be the calculation which proposes 41 points or the one that proposes 48 points? I see a correlation between average velocity and capacity, afterall if in the same scenario in planning for sprint 4 were 100% of the team present I would go more with an average velocity of 95 or 100 points to initially propose to plan than the plain average velocity of 83 points? I never see anyone talking about this? Just to calculate average velocity of past 3 sprints for sprint planning not considering if the team had less capacity on those past sprints?
@mrsjohnsonization Жыл бұрын
Thank you Aisha, you rock
@AishaTech655 Жыл бұрын
Thank you for watching 🙏🏾🙏🏾🙏🏾
@michaelmoses-oloyede8387 Жыл бұрын
This is very helpful Aisha. Thanks
@AishaTech655 Жыл бұрын
Thank you 🙏🏾
@missclara35277 ай бұрын
Aisha, thanks for this insightful video. Does it mean if you're doing relative estimation you don't have to do a capacity planner? My question is born from the statement you made that if you're doing absolute estimation then you can do your planner. Thanks
@AishaTech6557 ай бұрын
Hello, You always should to planning regardless of the type of estimation you use. You need to keep track of team availabilities, vacation, and holidays.