16 ms·
"Who is going to do it?" is always my first question whenever I am asked to estimate a piece of work. PMs/EMs are usually taken aback by the response, as if we
by paxys 5y ago
"Who is going to do it?" is always my first question whenever I am asked to estimate a piece of work. PMs/EMs are usually taken aback by the response, as if we are all supposed to pretend that all dev "resources" are equal. Yet reality doesn't fit into neat planning spreadsheets or burndown graphs, so often gets ignored.
- jseban 5y agoThe best teams I've ever worked with, that were the most productive and also had the best team work and team spirit, was when we assigned tasks in planning. And gave the tasks to whoever was most suitable to work on it. Unfortunately we were never allowed to do that, because of Scrum, and were only able to do it on the low down for a short time until management cracked down on it and enforced "anyone who happens to be free works on whatever is on top of the backlog".
- autarch 5y agoI "enforced" this as a manager at my last position. But I quoted the word "enforced" because this wasn't something I had to argue with anyone. I understood that it meant things might take a little longer, but it also meant that everyone on the team (which was small) would get exposed to all of the code we worked on. Specialization means speed, but it also means a lower bus factor.
- Viliam1234 5y ago> Unfortunately we were never allowed to do that, because of Scrum, and were only able to do it on the low down for a short time until management cracked down on it and enforced "anyone who happens to be free works on whatever is on top of the backlog". Ironically, this (what the management did) is completely against the rules of Scrum... in theory. But it is what management typically does when they are doing "Scrum".
- badtension 5y agoIn my experience it still makes sense to estimate together using the same story points (or T-shirts) when there are people ranging from almost no experience to very senior ones working on a project. 1 SP for a senior may take 1h of his time and for a junior that would be 2-3 days but it's still 1 SP - a relatively simple task. This is in contrast to a fallacy of recalculating SPs to time-based units cause if we do that we might as well just estimate in hours/days. It's about agreeing on some baseline first (what does 1, 2, 5 SP task look like?) and going on from that. We just need to remember that velocity will be different for different people so team capacity calculation is going to be all over the place but I think this approach can be useful.
- ZainRiz 5y agoWhenever I ask an expert how long it'll take someone new to the their code base to add feature Y, I mentally double whatever estimate they give and share _that_ instead. I haven't overshot the estimate yet.
- odshoifsdhfs 5y agoI got around this, specially around 'planning poker' when I got to be lead in these scenarios that forced you to do it. Whenever there is a discussing on how long something should take, whoever says the least amount, is tasked with the job. After 1-2 of these meetings, amazingly, all estimates started to come back quite higher than before. I still believe that whoever takes the task, should be the one deciding how long it will take, and only after understanding the scope of the work. Planning poker is the most useless piece of shit I ever seen, and still, it is used all around by idiots. If I am asked to estimate something, I will always give the highest possible value and justify with "I don't know enough about it to estimate". If I am managing and I have a top down force pushing for this, I will always make sure that the stupid process is obvious how fucking broken it is.
- Viliam1234 5y agoThe original idea was that "planning poker" should estimate the tasks in "story points", which are absolutely NOT supposed to correspond to days. It is just a way of saying "it seems like the task X will require twice as much work as task Y". Some teams do not use numbers at all, and estimate stories in "t-shirt sizes": S, M, L, XL, XXL. But of course, most companies want to have their Scrum and micromanage it too. So they estimate in days, and call them "story points". Or sometimes they don't even bother to pretend, and estimate directly in days. (So, how can you estimate how much gets done during the sprint, when all you have is the "story points"? You keep the records from previous sprints, and see how many "story points" got done back then. Adjust the number if someone takes a vacation, etc. This is self-correcting in long term: if someone starts pushing developers to estimate low story points, you will see that fewer story points get done per sprint, so your estimates of how much work gets done will remain correct.)
- exolymph 5y agoIt's not even necessarily about skill, could easily be that someone is already spearheading a higher priority or whatever.
- Swizec 5y agoDevs: there are no 10x engineers!! Orgs: okay you are indistinguishable cogs and we will treat you as cattle Devs: no wait not like that Truth is everyone knows that who or which teams takes a task matters immensely. We know that if Bob leads it’s gonna suck and if Alice does it’s gonna rock and finish on time. Managers know this also. But we’ve constructed a corporate culture where this is not allowed to be said. So we bend over backwards to pretend everyone is equal and capable of the same things in all areas. Then we secretly make sure somehow by magic the truly critical projects are routed to the people and teams with more reliable outcomes.
- MrPatan 5y agoWhat you cannot say is that there are 0.1x engineers.
- visarga 5y agoMaybe a mix of x0.3 and x3 engineers.
- jseban 5y agoIn my experience there are plenty of -10x engineers.
- zweifuss 5y ago1x is defined as the least productive engineer in a team. But I know what you mean. Sometimes a team can be more productive with fewer people.
- astrange 5y agoThat's acceptable if they're interns/juniors. If you only hire the best people for the job, you're never going to get any new people.
- deleted 5y ago[deleted]
- john_moscow 5y ago
- dpweb 5y agoIn my manager days I simply assigned a factor to each team member based on the type of work, so one person may be baseline hrs * 1 and another hrs *.8 This had to be accurate, as it’s consulting, if the hours are wrong we lose money. But only a direct line manager can do this, anyone else won’t have the knowledge of the staffs capabilities.
- dijit 5y agoit's even more complicated by knowledge/experience in certain areas. Fire me into some unknown terraform and I'll be able to orient myself faster than someone who only does C# every day. Send me into my own terraform and I'll be faster still. Not all things are equal.
- Kalium 5y agoI got a harsh lesson about this in one of my very first jobs. A senior engineer on my team had built a rather complicated system. He was accordingly intimately familiar with all aspects of it. So when he estimated something on that system, it came with nearly all the discovery work already done. The PM proceeded to take an estimate from this person, hand it to a brand new hire, and expect them to deliver on that. Needless to say it could have gone better for me.
- onion2k 5y agoThe PM proceeded to take an estimate from this person, hand it to a brand new hire, and expect them to deliver on that. Needless to say it could have gone better for me. This is a really good thing to learn from, although I doubt it felt like it at the time. The key thing that every junior dev needs to take from it is that it's fine if things don't take however long the estimate is so long as you're regularly communicating with the PM. PMs hate surprises. They need to know exactly what the state of the project is at any given moment. For them to think that a story is progressing on track when it's not is very, very bad (in their minds; it doesn't actually matter most of the time.) If you work on a story that's estimated to take 3 days and come back after 3 days saying "It's not done yet. I'm only half way through. I had to learn a ton of stuff!" then that knocks out loads of other things, and people get pissed off. If you work on a story that's estimated to take 3 days, and in the stand up on day 2 you say "I think I'm going quite slowly because I'm having to learn a lot, and I don't think I'll deliver this in 3 days" then your PM will (...should?) respect that you're keeping them informed. The senior might even step up to help you get there faster. Practically all the actual work a PM does is communication. If you're not communicating with them then you're blocking them. No one likes that.
- lifeisstillgood 5y ago>>> Practically all the actual work a PM does is communication. Practically all the actual work a PM does can be replaced with a script and dashboard
- onion2k 5y ago
- chairmanwow1 5y agoThis comment made me laugh because it’s so delightfully insightful. You are absolutely right and I’ve never thought to pose the question.
- Agentlien 5y agoIt may be a culture thing, but across the three companies I've worked at every estimate has been explicitly assuming a specific person handles it. Sometimes we've even given several estimates for the same task depending on who it gets assigned to. No one has ever found this odd. It's just obvious that different people have different skills and familiarity with different technologies or parts of the project.
- rramadass 5y agoThis is how planning should be done. Gauge people's expertise, put them on the path they can be most effective and then ask for their estimates. Take that to upper management and negotiate.
- dspillett 5y agoOne problem with that is sometimes the estimates are done long before the work starts so when that item eventually gets to the top of the priority stack the person estimated for is working on something else instead. At this point things need to be re-estimated which can cause friction if the new estimate is longer (“but last time, you said…” or “when we asked Bob, he said…”). What I've done in the past is give an estimate based on what a “standard” dev can be expected to do (everyone understands a junior is expected to be slower as they are new, that is why they are currently a junior and when they get up to speed they'll be promoted) with a comment on the ticket that the expected time will reduce by × if a named resource, or one of a group, is available to work on it. That way, medium term planning can be done on the basis of a “reasonable case” scenario and if the right people are available things will go better (and if there are multiple items in that state, short term planning will include deciding which ones being sped up, by using that person's time, confers most extra value).
- rramadass 5y agoRight, things are always probabilistic when it comes to us Humans :-) I like to think of it like Algorithm Analysis; Best-Case (estimate by the expert mentioned above), Worst-Case (estimate by Noob who just joined the project) and Avg-Case (estimate by person who is already part of the project but is not responsible for that module). Add a fudge factor based on your reading of the circumstances and then haggle with Management. You now have a band with a upper bound and lower bound which can be realistic. PS: You may find Douglas Hubbard's How to Measure Anything: Finding the Value of Intangibles in Business useful in this regard.