What's the point in a story point?

Part 1: talking of the point
















 Story points are estimates of effort as influenced by the amount of work, complexity, risk and uncertainty (https://www.mountaingoatsoftware.com/blog/what-are-story-points). When we estimate with story points, we assign a point value to each item. The raw values we assign are unimportant. What matters is the relative values. A story that is assigned a 2 should be twice as much as a story that is assigned a 1. It should also be two-thirds of a story that is estimated as 3 story points.

Not delving into the details of how to estimate and what these numbers should be (linear vs. non-linear series or Fibonacci numbers), the focus of this post is to discuss how these points affect the life of a scrum team (development team, scrum master & product owner).

A story adds “value” by delivering functionality that the business has asked for, and can/will use depending on whether the story is a part of potentially shippable product increment (and whether the business has requested the increment to be made available in production or not). Product backlog, a collection of stories in turn, delivers the “value as a whole” or “the product” to the market to get the business returns on their investment.

So the point here is, that a story point is “some value” to business in terms of functionality.

and the question is – What is the perception of our stakeholders about these points? And how does it affect the life of a scrum master/development team? My next post deals with these questions – so stay tuned!
Best,
Jasdev Singh (PMI-ACP, CSM)

https://in.linkedin.com/in/singhjasdev

Comments

Post a Comment

Popular posts from this blog

Increasing your Agile Team's Outcome Predictability

Image
Understanding Predictability in Agile Team Outcomes   "Understanding Predictability in Agile Team Outcomes" refers to the study or analysis of how consistent and reliable the results or achievements of a team practicing agile methodologies can be. This involves examining the factors that contribute to the team's ability to deliver on time and within scope, as well as identifying potential challenges or obstacles that may impact their predictability. By understanding these dynamics, organizations can better manage and optimize their agile teams for more consistent and successful outcomes. In today's rapidly changing world, the significance of accurate weather forecasts cannot be overstated. Similarly, in the world of software development, predictability is crucial for Agile teams. The ability to deliver outcomes predictably is a key factor in Agile team success. Achieving predictability can be challenging for Agile teams due to various factors such as capacity planning
Read more

Stop starting, start finishing.

Image
Limiting WIP & reasons for high WIP My first post on Kanban  deserved a sequel for sure! While it isn’t possible to have literally no work in progress, the overall goal of a project team is to finish as many things as they can, and not be in a state of continually starting. Having too much #WIP makes this goal even more difficult.  The impact of too much WIP on efficiency and throughput is one of the reasons it is often regarded as a concern. According to studies, the cost of context change is frequently far more than people anticipate. It is evident that dropping one object and taking up another cannot be done in such a way that no time or energy is spent between the two. However, there is sufficient evidence to suggest that the loss is rarely worth the gain. These apparent consequences of having too much going on are easy to identify once you know what you're looking at. Looking around the team, you'll notice that there are many tasks open, few of which are done, and many
Read more

Mastering the Daily Scrum

Image
- A Key Ingredient for Agile Success Introduction: In the fast-paced world of software development and project management, staying on top of tasks, priorities, and progress is essential. The Daily Scrum, often referred to as the Daily Standup, is a cornerstone of the Agile methodology. It's a brief, focused meeting that empowers teams to synchronize, collaborate, and make data-driven decisions. In this blog post, we'll dive into the what, why, and how of the Daily Scrum to help you harness its potential for your agile projects. What is the Daily Scrum/Daily Stand-up? The Daily Scrum is a daily ritual (a scrum event) that brings the entire team together for a brief, time-boxed catch up. Its primary objectives are: Synchronization: Ensure that everyone is on the same page regarding the sprint goal and knows what to work upon given the priority. Collaboration: Encourage open communication among team members. Identify and Remove Obstacles: Highlight any impediments that need res
Read more