Story Points & Velocity by Naveen Nanjundappa

[@ipsitaroy6242]

The relation between Sprint planning, Velocity, and Story point is explained very well.

[@divya733]

Important concept explained very well. Story points make or break the sprint development plan.

[@snehitajain7609]

Very good explanation on sprint planning,velocity and story point .

[@mamtagarg3875]

Good review on velocity, story points & how it impacts the team performance & in estimation

[@affannafees7147]

The concept of velocity is very well explained for sprint planning, whether the scope is fixed or the date is fixed.

[@lauraesene4975]

This was very informative Naveen. Thank you

[@subarnakhatri6245]

Story points, velocity, and estimation are well explained in terms of user stories.

[@sankhyachattopadhyay2158]

Interesting way to quantify the efforts. Thanks!

[@NaveenNanjundappa]

Thank you

[@heriantoherianto4053]

key takeaways are understanding of story points, velocity and run rate. This is a new knowledge for me that we can use velocity as the guideline to do sprint planning. But I'm also wondering, can velocity become guideline if we only do a few sprints (like 2-3)? and can velocity become such a thing to be discussed in sprint retro? for example can we ask like why the velocity of this time is in this number? Thanks for the explanation

[@sarahrathana]

Very Informative video. Thanks

[@nikkiayeni2790]

velocity helps to give an indication of team strength

[@vincenzoaltimari7320]

Very interesting way of thinking to the velocity and how it's not impacted by the continuous improvement. I also think that at one point the skill gain in the team will bring to higher velocity due to the increase in effectiveness and efficiency

[@NaveenNanjundappa]

Velocity is the result of work.. so focus on being efficient and effective Thank you.

[@drpritir]

Well explained

[@vksomething]

This is very helpful, many thanks for the video

[@NaveenNanjundappa]

You are welcome!

[@catherinemarymathew8141]

Obtained detailed information on estimation, story points and velocity

[@jakobsch8377]

Understanding the use of comparison to improve planning for future sprints

[@mvrsrivatsava13]

Take aways: 1. Definition of story points. 2. Size of a user story. 3. We look at the complexity of work 4. Use Stacey diagram to determine 5. We use comparison techniques to determine the size of a story. It gives relative size. 6. It is based on the team and reference point. Definition of velocity: total of each individual sprint points/ no of sprints. It is used for future estimates. It helps to upskill a team to improve velocity. This skill can be part of sbl.

[@virendratheprince]

Nice corelation between story points and velocity

[@ts-krishnan]

Takeaway/learning: An appreciation of various terms like story points, estimation, complexity, velocity, etc. Need to get a better grip using real project examples during the CSPO session.

[@sarthakjena2000]

3 key takeaways: 1. Story points are the estimation of the size of the story 2. Reference helps in comparison 3. Sprint velocity reflects as average work done during the sprints

[@mohitgupta4489]

Key takeaways: 1. Size estimation in Agile software development uses the Fibonacci series as a reference scale, measured in "story points" and is non-linear. 2. The goal of size estimation is to ensure that all team members are estimating the same size, regardless of who is doing the estimation. This is achieved by using a technique of comparison, where an existing item called "Reference" is used for comparison. 3. The complexity of work is determined using the Stacey Diagram, which compares requirements with technology. 4. Velocity is a metric used to measure the amount of work completed in a sprint and can be represented graphically as work done vs time. It is important to note that velocity should be used as a guideline for short-term planning, and not as a definitive measure of team performance. 5. The sprint backlog includes not only items from the product backlog, but also items from previous sprints. 6. It is important to understand that a perceived decrease in team velocity does not necessarily indicate a lack of skill among team members, but rather is a normal part of continuous improvement. 7. Negative impacts of incorrect use of velocity include: teams becoming stretched, team members overestimating the size of work items, confusion among team members, and customers not wanting to pay for skill development.

[@proudkislaya]

Key Takeaways 1) Storypoints are for a points for a current scrum Story. They can be given to a prod backlog item based on the reference of similar items post discussion among the team. 2) Velocity of a team is defined as total units of work completed divided by the number of sprints 3) We can use velocity value to find work done for a fixed date release and can calculate the approximate number of sprints required to finish work for a scope fixed release. For Shortterm projects, we can use velocity as a guidance for planning.

[@purvaverma2524]

Key Takeaway: Storypoints are used to estimate the size i.e the complexity of the work item. Storypoint can be given to a Prod Backlog item based on the reference of similar items. Velocity is the average of work items done in a given sprint. Velocity is more useful for long term predictions. In a scope based release using the velocity one can predict the number of sprints required to deliver a given set of work items.

[@sanjeebkumar8843]

Key Takeaway: 1. How the technique of comparison can be used to determine story- points 2. Insightful explanation on 'Velocity' of the team. 3. If the focus the short term the Velocity calculation should just be used as guideline to plan upcoming sprints

[@Shrie8]

Key takeaway: 1.Story point is a sizing technique used to estimate the time required to complete a unit of work. 2.Story point is relative to the team and specific to the reference point.If the scrum team changes, the story points will also change. 3.Velocity is defined as the average work done (Total Work Done/ Number of Sprints) by a team over a series of Sprints 4.Velocity is used to decide the strategy for Fixed Date release ans Scope based release 5. Skill based training reduces the team velocity so team estimation should strategize on how resource allocation needs to be adjusted and how the cost of training will be accounted 6.Skill based training during a sprint will reduce team velocity in short term but will improve or speed up velocity in later sprints.

[@curvirao7059]

Key Takeaways - 1. Storypoint is a relative size estimation technique 2. Velocity helps in identifying total amount of work that can be done in a fixed time strategy OR number of sprints needed in a fixed scope strategy 3. Adding skills development to sprint backlog may decrease amount of total story points delivered in a Sprint, but doesn't affect velocity as much and should be considered a part of continuous improvement

[@rahulkr27]

Very useful.

[@NaveenNanjundappa]

Glad it was helpful!

[@williampoletto9518]

Key takeaway: story points as a means of calculating time efforts, which is negotiated within the team, and velocity as the average speed of completing tasks (always to be taken in context and for reference only)

[@unnatimistry4590]

Unnati Mistry CSM batch 29_30 April 2023 Keytakeaways 1.Story point is unit of size estimation technique for whole team.It is specific to team and reference techniques. 2. Velocity is the total work done by total team members.It gives average work done by the team. Average =Total work done÷ Total number of sprints 3. Relationship between velocity and forecasting depends on future like how mu h work team will do in future. 4.It Management statergy is wrong or misunderstood the team will be stretched,stressed,confused and may have over estimation of size of story points.

[@TheWanderingPrince]

Key Takeaway: Understood how the technique of comparison works in practicality. Also learnt how Velocity (run rate) can be used when planning or predicting the velocity of the upcoming Sprint.

[@bijunija2345]

Take Away 1) Story pointing 2) Velocity 3) Impact on team velocity

[@Manibhardwajj]

Great Video, thanks

[@NaveenNanjundappa]

Thank you

[@ashwiniponnachan4977]

Points given to a story , estimate of a size of story. Story points or T shirt size-- Complexity of work. In Stacey , ""complex zone"" - effort is not possible so we use story points. Technique of comparison is used, with a reference. Velocity = Total work done/ Total number of sprints If focus is short term , then velocity is used as a guideline for planning

[@skhadse]

Key Takeaway: Story point estimation, technique of comparison and understanding how velocity if properly used can help in accurate prediction of release. Also use velocity only as a guideline in case of short term planning. At end of the sprint, actual work DONE is only considered while calculating Velocity.

[@efrelyndavid3729]

Key Takeaways: Velocity is equal to the work done of the team and estimation average depends in each team member perspective

[@priyadarshinilakshminaraya747]

Story points are relative estimation size of Complexity and they differ from team to team. When estimating a Story, The whole team has to come to a common estimation point. Velocity is the historical average that the team effectively achieved and it includes all the stories that are in Done .

[@aafreenqureshi8153]

Key Takeaways 1- Explanation of Story point and velocity and their impact. 2- Technique of comparison and calculation of velocity

[@ShrutiAmritphale]

Takeaway: How story sizing can be done by reference comparison, relatively..velocity calculation, how it helps in release or as a guideline for sprint planning for short term focus.

[@alpsrajput6243]

3 Key Takeaways: 1) story points is also called Tshirt sizing and is determined based on the complexity of the user story 2) Velocity is used to estimate how much could do and is calculated by past history 3) It’s a myth that ST is unproductive, if the last sprint total points delivered by the team was less than calculated velocity.

[@sunainanaina2820]

Key Takeaways : How story points given and Velocity determine long term planning of the deliverables.

[@abuprasad5586]

Good to know... but these reference points... how does that get set? Who sets it? - Abu Prasad

[@NaveenNanjundappa]

The reference points are mutually agreed by Scrum Team

[@seshuvutukuri6450]

Story point is a relative size estimation technique

[@NaveenNanjundappa]

Yes, it's relative and one should have a reference scale without which there is no way one can use Story Point

[@jignalodaya4515]

Key takeaway - During the Sprint identify the work conducted during each sprint and measure it in units to calculate the velocity. The average number we get helps to define the amount work can be completed in each sprint.

[@manchalikulkarni5054]

Key Takeaway: Story point are the estimation for a specific story which is decided with a reference value and discussed in the team. Velocity is the average units that the team can implement in a given Sprint. This is helpful in a long term planning and not for immediate or short term planning.

[@vikaskannan3160]

Key takeaway- How sprint planning can be done with the understanding of story points and velocity

[@dominic1969]

useful

[@NaveenNanjundappa]

Thank you

[@AnandKulkarni-mw8rf]

Key takeaway : 1.Importance of Velocity in long term 2. Story Points is estimation of size based on reference points

[@anupmc77]

Understanding the below terms: 1. Story point 2. Sprint velocity 3. Run rate

[@ashrithashetty-ch9fd]

Key Takeaways :Concepts of story points and velocity based on fixed time/scope.

[@nigamabhishek001]

Key Takeaway: Arriving to mutually agreed Story Points; importance of including New skills or continuous learning in the S.Backlog.

[@iaskalbert3891]

Key take aways: Estimation using different techniques. Velocity, planning & run rate relationship each sprint

[@karthikarumugam6155]

Key takeaway: Velocity can be used as a measure to track to the efficiency and effectiveness of the team and tools and techniques

[@baser40]

Key Takeaways: Story points can be represented by complexity of work plotted on stacey diagram. Velocity calculation in proportion of total sprints to work done in a sprint. Velocity is not significant for short term goals.

[@rajithamarapally9184]

Velocity indicates how much work the team has finished in a Sprint.

[@sukarnaacharya9615]

Is not Units of Work (in Velocity) same as Story Points?

[@NaveenNanjundappa]

Story points are unit of "Size" measurement While Velocity is the Average amount of work done. Look at them as Runs & Runrate (velocity) in cricket !