Remove velocity-measure-predictability-not-productivity
article thumbnail

Velocity – Measure of Predictability and not Productivity

Agilemania

Note: I have written this article assuming the reader has working experience in Agile and know the concept of Velocity. In the Agile world, the Velocity means “The amount of work (Units or Value or Work Items) that was delivered to create a potentially releasable Increment in a Sprint.”

article thumbnail

“Cashing In” on Undone Work

Scrum.org

Velocity is a complementary practice many Scrum teams use to plan future work. Every Sprint, the team adds up points for each Product Backlog item (PBI) that meets the Definition of Done by the end of the Sprint. Velocity can be a helpful metric. But Velocity is also problematic because it is often misused.

2024 186
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

The Illusion of Velocity

Scrum.org

TL; DR: The Illusion of Velocity In this article, I explore the pitfalls of ‘The Illusion of Velocity’ in agile contexts, peeling back the layers of traditional metrics as leadership tools. Moreover, get an idea of how to start flipping outdated hierarchies and embrace the natural rhythm of productivity and innovation. ?

article thumbnail

5 Common Misconceptions about Scrum

Scrum.org

During Sprint Planning, the Scrum Team choses a Sprint Goal, selects Product Backlog items they believe will best accomplish the Sprint Goal, and creates a plan for delivering the selected Product Backlog items. For example, if the team is building a new software product, they may find that certain features take longer than expected.

SCRUM 249
article thumbnail

Deciphering the Enigma of Story Points Across Teams

Scrum.org

However, they shouldn't be the primary metric for comparing teams or predicting future deliverables. While they might offer a vague direction, they're often misused in planning and measuring. There are better choices for teams aiming to optimise their value delivery than relying solely on Story Points and Velocity.

article thumbnail

Exploring Estimation Approaches: What is the Right Fit for Scrum Teams!

Scrum.org

Estimation is a complementary practice Scrum Teams use in Product D evelopment. The purpose of estimation is to provide a rough idea of how much effort, time, and budget are needed to complete specific features or PBI- Product Backlog Item of the product. This approach generally be least useful for complex product development.

Estimate 177
article thumbnail

Myth: Velocity is Productivity

Scrum.org

One of our goals is to increase velocities across all our teams by X%. A company known for developing “Agile” products surveyed more 18,000 customers and Software development professionals, which is what they discovered. . Velocity is just a Complementary & Optional Practice in Scrum. What is Velocity then?