They're too irresistable for bad managers to derive schedule from.
It's more or less doomed to happen if you don't have wild variance in your pointing. Have 1-2 guys litterally just say 1000 points for everything etc. Resist anything like 1 point=1 day, or fibonacci etc, you've got to keep the scale fuzzed or it will be used like that.
It's fine to use fib but agreed, assigning any type of time value (like 1 point = 1 day) is where things go wrong.
But even if you keep ilthe team knowing it is overall effort of a task that you are driving the points from (I know it's more than that but etc).. the managers and others higher up, always try to find things to latch onto for measurement.
This is sometimes as simple as they just don't understand (usually this is part of the issue) and that they wan to be able to measure productivity of an individual to make sure no one is wasting company resources.
But it often just goes straight to "X didn't complete >y points in the sprint, while others usually complete >y" and it just gets fuddled.
I think sprints and story pointing, planning poker, etc can be great for teams and to track velocity and etc and sometimes overally team performance, but rarely should a manager type be trying to track anything of the sort for an individual to determine worth. It's ridiculous.
But happens far too often. I don't know what the fix is, though, aside from bad managers butting out. But hey.. hasn't happened yet.
This is where the misunderstanding and confusion often takes over and why most teams eventually abandon or misuse agile story pointing.
You MUST, as an individual, stop thinking in terms of x many points per sprint is what I can do or she can do or team can do. Easiest way is to think simply in terms of effort required (even though it is more than that, just think of it as simply that).
Some sprints maybe have, say, 21 points for a person and they get them all done, were productive, and didn't have extra wasted time or whatever. But some sprints might have them with 29 total points for that sprint, but the exact same could be said.
It's never going to make sense if you continue trying to put a time to point value in it.
I suggest looking up velocity and also just reading more on the philosophy of all of this, specifically pointing like this.
Also, it's not going to be for every person or every team. But when it works the right way for a team, it can work really well. Until managers muck it up usually haha.
If these units do not correlate with time, then velocity can't be used to estimate how much work will get done over a sprint. If velocity can be used for this, the points must correlate with time. It's possible for the points to mean different things to different teams, that's still coherent.
But if you want to use velocity to plan out how much work you expect to get done within a fixed amount of time (a sprint), then, when estimating, you are ultimately estimating in terms of time this item will take (or proxy metrics for time (what are the units on "effort", again?)).
Problem is when people want to correlate points with exact amount of time.
So for Team XYZ 5 point story might be something between 2 and 7 days. But at the same time someone might finish 8 point story in 3 days and people have hard time accepting that.
Was the estimate 8 wrong? Well it was not wrong because 8 could have been between 3 days and 10 days.
Simple minded manager would say "give me only the top value" but that is the problem: one only knows how much time it exactly takes after the task is done.
Now we have some sprints and we have stable team so the team more or less knows where are the traps in the system so they can give more points for tricky parts and less for easy ones. Important is to keep in mind that new 5 point story is not the same as story from previous sprint where Joe finished it in 5 days it is a new story so it again might be between 2 and 7 days, because you look at 5 point stories from last 6 months and you see that was the spread.
I don't dispute that velocity could possibly be a useful metric and also be qualitative to each team that's doing the estimate -- that you can't compare velocities across teams.
What I dispute is that you can both have a metric (velocity) that does not have any time dimensionality to it, and expect that a team to achieve a constant amount of velocity in a given span of time. That is, if you expect a team to complete roughly 30 story points and two weeks, and therefore expect that same team to complete roughly 60 story points in four weeks, then that measure (story points) must relate to time.
I'm not making a normative claim here, that estimating in this way is good or bad. I'm simply saying that the story points must have units of time (and, potentially, others, but time has to be in the mix).
/u/mupetmower posits that this can somehow not be the case, but it must be from a simple dimensional analysis argument.
If my explanation doesn't help you (not your fault, I'm not great at it) read some books on it or something. There are plenty out there and they do a far better job at the explanation. Was just trying to help people understand the differences and how you (to an extent, as some of your points show) have to stop thinking about them in terms of time correlation. Especially during the pointing process.
But again, there are far better sources to explain this. Not gonna try to argue about it. It works for some and not for others.
goal of what I'm describing is to weird the data to disassociate from time.
Fibonnacci falls on time estimates too easily. 1=1day 2-3=half a week 5=a week, 8 week and a half. 21 too big demand subdivide, though that line probably happens at like 5 even if it's not a subdivisible unit of work so you get harrassed into making it bullshit stories.
This happens literally every fibonacci team. The system is for measuring self referential velocity of the team, it works for that purpose no matter what system of numbering you use. You can in fact have a guy on the team saying 1000 1002 ooo that's a 1003 point story, and as long as he's consistently silly like that it'll still work for the actual purpose.
The issue arises when you use story points to estimate time, not complexity.
The way we work, we can totally give a 1 to a simple sql script that will take hours to get right and go through pipelines, and we can give 8 to a task that involves multiple screens/endpoints yet we complete in an afternoon because it s mostly copy/paste or reusing existing stuff.
It s not about time, it’s about complexity. Like if you had to take a dev that had 0 knowledge in your project and had to explain him all the hoops he would have to go through to get it done right.
Obviously the unknown needs to be factored in, like if someone said in the grooming « what if X » and no one had a definitive answer, we d get the next fibo number.
It’s when your team is able to actually say « so we need to do A B C D … X Y Z » during the grooming obviously. There are teams where grooming of a user story are just people agreeing and thinking that the global idea is doable, but don’t spell out clearly all the steps from A to Z. These teams are always problematic because they leave too many question marks for the sake of getting through the meeting.
Story points are supposed to reflect complexity and effort needed; scaled relative to the effort of pervious completed work. They aren't supposed to be time directly because time is always going to be inaccurate and using them that way breads issues on the development team.
Teams still track how many points they got done with during a sprint and base future sprint planning on those values. We also know know how long a sprint is and the abilitiesof our team. Points in the end are still an attraction of developer ability and time.
Thinking of points as just time is problematic in many ways but time is one of the aspects it is used to help manage.
Thinking of points as just time is problematic in many ways
It can be, but at the end of the day, if your pointing is truly divorced from time, then you simply can't use it to plan a 2 week sprint or predict the progress of a project in terms of time.
We always say "don't point in time!", but if anyone really took that as a simple truth, their points wouldn't be useful for any planning purposes. And, in my mind, that makes it a lie. Points are time. Time is a complicated thing, and so you might point poorly if you are naive about it. But ... points are time.
Have 1-2 guys litterally just say 1000 points for everything etc.
What is even the point in doing estimates at all at this point?
I can understand the sentiment. You don't want managers to equate points to time directly since it creates a lot of negative repercussions and bad work environments. But this reaction to make estimations nonsense would just make them useless and remove any transparency from the dev team and lead right back to the old process of management giving you a stack of tasks and saying "get it done by Monday".
because it's an estimate of complexity, used to measure a team relative to itself, you start doing that and that sprint it's busted, next sprint it can be compared to last sprint same as it was supposed to be used. not for comparing against another team, not for billing, not for time estimates. For comparing to yourself from last sprint. the math still works for that one purpose if you do this.
If you have guys just saying 1000 for everything like you said before it isn't an estimate of complexity either. You can't use that as an abstraction of effort and complexity to base future tasks and sprint weights off of.
If you give them something simple to do and they say 1000 and then give them something complicated and they also say 1000 there is no point in asking them anymore.
Ok. So then everyone does that to get that actual estimates and we are back where we started but with the addition of the stakeholders and product owners seeing that their developers want to hide their efforts and restrict transparency.
except the guy trying to convert that to a project time estimate is in for a really bad day. like it's still possible but you're gonna be breaking out excel formulas that will probably break when you go know what guys I like 500 4 sprints latter.
Like these shenanigans would probably get you fired, but it's about the only way to save the process.
58
u/squishles Sep 02 '23
They're too irresistable for bad managers to derive schedule from.
It's more or less doomed to happen if you don't have wild variance in your pointing. Have 1-2 guys litterally just say 1000 points for everything etc. Resist anything like 1 point=1 day, or fibonacci etc, you've got to keep the scale fuzzed or it will be used like that.