4 ms·
This story being about a marketing department might seem like it's not applicable to a software company, but when it comes down to it, we still break down our w
by coding123 10y ago
This story being about a marketing department might seem like it's not applicable to a software company, but when it comes down to it, we still break down our work into bite-sized stories that can/should be accomplished in a timeframe that's estimated ahead of time. Some shops have more nebulous tasks because they've never done something before, I get that. But for the build the thing we know how to stuff? We should be able to deliver consistently. It comes down to your ability to break down the work into small enough pieces such that you know how long it will take. If you don't know how long it will take, it's not broken down enough.
Now to play devils advocate - I'm generally in favor of carrot not stick.
- SomeStupidPoint 10y agoCould you elaborate what you mean by your last line? I think firing someone for it once is on the harsh side, but if someone repeatedly doesn't share key information, how can you keep working with them?
- Sorreah 10y agoI believe this just isn't possible for a whole lot of projects. Codebases tend to grow so large, and people tend to come and go, so people don't really know most parts of the code, so then a lot of the time estimates are inaccurate to the point of being useless.