4 ms·
As someone going through this right now, here's some things I do to make the process easier. 1. Put together a ~medium detailed listing of what work needs to b
by arcticbull 7y ago
As someone going through this right now, here's some things I do to make the process easier.
1. Put together a ~medium detailed listing of what work needs to be done, broken down into sub-tasks.
2. Include estimates for how long each sub-task will take.
3. Roll that up into a gantt chart with dependencies reflected.
4. Identify opportunities for parallelization so you can answer the question of "will adding more folks make things go faster?"
5. Identify and be prepared to speak to which portions of the schedule represent padding, and explain why it was padded in that way. Share your thinking in the trade-off you made and be open to adjusting -- and de-risking the schedule in other ways.
6. Realize this is a bit of a negotiation, not necessarily you vs. them but more you and them vs. what you can deliver. In a negotiation it's important to not appear intractable. Have things you can give away.
7. At the end of the day the engineers are writing the software. If you're not actively dragging your feet, what you say does go, so it's a question of where you're spending your time, and on what. With that in mind, your boss has a job to do too, so help give them the tools they need to do so.
8. Don't burn bridges, y'all have to work together.
- suchire 7y agoI think another rule of thumb I would add, which other commenters have mentioned in passing, is to negotiate scope, quality, and likelihood of success, not estimates. Negotiating estimates is where people start questioning each others’ expert judgment, which leads to a breakdown in trust.
- JamesBarney 7y agoI haven't found gantt chats very useful in software. I've never been found a project that was delayed due to a critical path error. I'm sure it's happened but I've seen far more delays due to gold plating, over-architecting , or bad estimates.
- gregmac 7y agoHow does a "bad estimate" cause a project to be delayed? I think this type of wording is part of what causes animosity in the industry about this topic. Estimates are not called "promises" for a reason, and any attempt at treating them that way will result in failure. Software estimates are notoriously hard to get right and it's not uncommon for them to be wrong by several orders of magnitude, and this effect is magnified for bigger estimates/work. Any decent project plan needs to assume this is the case, and it needs to be continually refined as work progresses and the accuracy of "estimated remaining work" gets higher as the problem is better understood. The worst project plans are the ones that take the initial estimates and use those as delivery dates, but I'd classify that as a "bad plan", not "bad estimate".
- JamesBarney 7y agoA bad estimate causes a delay to the project schedule (in the sense the schedule is delayed, not in the sense the software takes longer to write) . It's not the same kind of delay, but to many stakeholders it's perceived as the same kind of delay. > Estimates are not called "promises" for a reason, and any attempt at treating them that way will result in failure. So management 95% of the time treats estimates as commitments. What they are going to do with the numbers you give them is promise upper management or clients "feature x will be done by y". As engineers we have two options, scream until we're blue in the face "that was an estimate not a commitment" or just give them a commitment and call it an estimate. You're right software estimation is hard, but the really bad estimates I've seen (> 100% over) were due to a combination of dysfunctional organizations, lack of estimating skill, and an organization that didn't put effort into making sure it's estimates were right.
- thr0w__4w4y 7y ago> Software estimates are notoriously hard to get right and it's not uncommon for them to be wrong by several orders of magnitude OK now hold on there just a sec... I've seen estimates off by 20%, 50%, even 100%. I'm sure there are estimates that have been off by 500% (I'd hate to dig into why). But "several orders of magnitude" is something like 10,000x -100,000x. Hopefully that is just extreme hyperbole, but honestly in the context of discussing estimates, it seems particularly out of place.
- arcticbull 7y agoBad estimates can cause shipping delays when cross-functional or inter-dependent work ends up in day-for-day slip because not all work is parallizable. The only time a bad estimate doesn't cause a delay is when it's "single-threaded" and the long pole.
- dchuk 7y agoGantt charts are incompatible with software development
- arcticbull 7y agoI've had a lot of success with Asana's timeline and also with TeamGantt. It's my go-to for project management, and for what it's worth, I and by extension my teams are known for nailing our deadlines come hell or high water (without burning out my team). It's a tool in the chest, it's not for everyone, but it's by no means incompatible. Depends how you slice your work to be done :)
- anthonybennis 7y agoI find them useful for large projects with multiple teams with inter dependencies.