4 ms·
The entire concept of a sprint to me always felt wrong. Development work can't be split up into time slices. And trying to divvy up tasks based on an estimate
by Sohcahtoa82 8y ago
The entire concept of a sprint to me always felt wrong. Development work can't be split up into time slices. And trying to divvy up tasks based on an estimate of how long it'll take to complete each one is just a waste of time.
I remember being in a standup, being told to bump a high-priority task into the next sprint and complete a couple low-priority tasks instead because I already had too many points assigned to me for that sprint and just thinking...really? If I don't complete the second high-priority task before the end of the sprint, so what? I still made progress on it.
It just felt like so much time was being wasted. We estimated the amount of time each task would take, assigned it points based on that, and we'd fill our task list in such a way to try to make the estimation close 40 hours of work. If you had 30 hours worth of tasks assigned to you already, and there was a 20-hour high-priority task in the queue, it'd get bumped to the next sprint with 10 points of low-priority tasks assigned instead. It was more important to them to get precisely an estimated 40 hours of tasks completed, rather than getting supposedly high-priority tasks done.
Obviously, this frequently resulted in priority inversion, not to mention the problems from poor estimations of task time.
Management was often clueless. You only earned the points when you completed the task. So if you took on two 20-hour tasks, and just barely didn't finish the second one before the end of the week, but then completed that plus 40 hours the next week, they'd question why your productivity swings so much because you only got 20 hours done one week, but 60 hours the next!
And of course, as mentioned, these "hours" were all estimated hours, not the actual hours done. People started overestimating the hours needed for tasks, but management was apparently smart enough to catch on to that when they noticed everyone was getting 50-60 hours worth of work done, despite everyone only working about 40 hours per week.
I've rambled a bit, but you get the idea. I think the author is spot on. Just use your task tracker.
- aphextron 8y ago>The entire concept of a sprint to me always felt wrong. Development work can't be split up into time slices. And trying to divvy up tasks based on an estimate of how long it'll take to complete each one is just a waste of time. That's because sprints weren't designed for us. They're designed for management. Product managers and VPs need to be able to think of their "resources" in manageable, discrete chunks. Vagaries are an absolute antithesis to their world view. Small boutique firms can avoid this, but mass production means the need for mass conformity.
- deleted 8y ago[deleted]
- bunderbunder 8y agoThey should be designed for us. The idea is supposed to be that there are limited times that developers are negotiating with the outside world about what exactly they are working on. The rest of the time, nobody gets to interrupt and demand that they drop everything and jump on to their latest crazy idea. But yeah. I currently have to wear both the PO and dev hats, and, when I'm wearing the PO hat, I also see advantages: It means that I get to have a rhythmic schedule that I can set my calendar to. That makes all the orchestration crap so much easier. Which, incidentally, I also like from a developer perspective. The less time I have to spend on that stuff, or get randomly interrupted by that stuff, or randomly interrupt people with that stuff, the more time I get to spend on actually building stuff.
- Shaanie 8y agoWhy are you estimating things in hours? Why is management tracking the amount of story points every developer completes in a sprint? Why are you not working on the highest prio stuff in the sprint? Of course sprints look useless if you're doing them like that. Do you even have a clear sprint goal you're working towards?
- Sohcahtoa82 8y ago> Why are you estimating things in hours? Because anything else is completely arbitrary. I mean, we ARE measuring things in "points", but with the understanding that 1 point ~ 1 hour of work. > Why is management tracking the amount of story points every developer completes in a sprint? Because they want metrics on productivity. I don't entirely blame them. > Why are you not working on the highest prio stuff in the sprint? As mentioned, because management really wanted to see us complete 40 hours of work every week, and getting close to 40 hours done per week was more important than priorities. If something couldn't be finished before the end of the sprint, they thought it was better to push it to the next sprint, rather than leave something incomplete at the end of a sprint. > Of course sprints look useless if you're doing them like that. Do you even have a clear sprint goal you're working towards? I was on a QA team writing test code. I specifically was writing security tests, while others wrote functionality or stability tests. Each sprint goal was effectively just "Write these tests".
- ApolloFortyNine 8y agoPeople always say not to estimate in hours and instead to estimate in "points", but at the same time teams tend to plan around how many points they're taking into a sprint. If you have 40 points but usually take only 30, you'll be asked to bump something out. And once you agree on a number of points to do in 2 weeks, it's not rocket science to figure out an estimated number of hours per point.
- brazzy 8y agoThe point (heh) is not that there is no mapping between story points and time, the point is that it helps us acknowledge that these are estimates, not promises that signify failure if broken. No individual estimate is expected to be exact, but we hope that deviations from the estimate average out across the stories in a sprint. And most importantly, story points make it easy to base our sprint commitment on the available evidence from previous sprints. We say that we can do 40 story points in a sprint, because we know that is roughly what we managed to do in the last few sprints. The conversion factor can change over time as the team gains experience, or the team changes, or the nature of the work changes. It's much harder to do such adjustments when you directly estimate hours.
- darkr 8y ago> We estimated the amount of time each task would take, assigned it points based on that, and we'd fill our task list in such a way to try to make the estimation close 40 hours of work. The concept of story points was invented as an attempt to solve the problem of developers reliably estimating the amount of time a given task will take. If you're directly equating story points to time then you're doing it wrong.
- t0mbstone 8y agoAnd yet, story points are used to estimate how much work a team can get done in a sprint, which is a time measurement... and they are used to track velocity, which is used by management to figure out when a project might be completed (also a measurement of time). "Oh, story points are just about the complexity" Oh really? Why does complexity matter, if not to function as an indicator of how long something might take to finish? Anyone who is telling you that story points aren't directly related to time estimation is either confused, or lying.
- darkr 8y agoAbsolutely, story points are used as a component in the estimation of time. Story points on their own are useless though; they are an abstract thing that only means anything to the team and it’s velocity. A good analogy is that they are an estimate of distance. Knowing roughly how far something is away does not tell you how soon you will get there. You can only do this by working with an average of how fast the team can go. If the team is terrible at estimating distance, then the velocity will reflect that and gradually self-correct.
- t0mbstone 8y agoJust because you swapped the word "time" with "distance" doesn't mean you aren't still talking about time. Distance from what? How far it is from now until when the work will be done. You are still talking about time. I feel that swapping out the term with one that is more vague is, at worst, disingenuous, and at best, counter-productive.
- 8y ago
- gnarcoregrizz 8y agoI've noticed similar things. One of the things that bugs me the most in my organization is that managers (product owners, non-very-technical VPs) there's a push to split larger items into bite-sized chunks which can be neatly distributed amongst developers and neatly tracked by PMs. These smaller items are now inter-dependent, which result in a lot of context switches and cache misses, even on an individual scale, not to mention they are often misestimated, and sometimes flat out wrong since they come out of planning meetings rather than thoughtful, careful research.
- ozim 8y agoI am upvoting because that is totally pathological example of how it should not be. If I end up in place like this I just quit as soon as possible. Maybe they heard something about "Responding to change instead of following plan" and implemented it...
- kevsim 8y agoCould not agree more. This coupled with the feeling of being "defeated" when you need to move cards from this sprint to the next sprint just because you didn't get it completed is why my team went away from sprints.