DEV Community

Discussion on: Cost of delay: simultaneous feature development

Collapse
 
bosepchuk profile image
Blaine Osepchuk

Oh man, I'm not qualified to answer that question.

Imagine that software development is like flying a modern jet. You've got hundreds of dials, knobs, and switches in the cockpit. And depending on what you're trying to get the jet to do, you would set those dials, knobs, and switches to different settings. The correct setting of any particular knob for landing might destroy the plane if you use that setting in the event of an engine fire. Context is important.

I have no idea what your company is trying to achieve or even what kind of jet they are flying (to continue the analogy). I just wrote a blog post that pointed out a particular knob and tried to describe what turning it might do to the profitability of a hypothetical company. It's up to you (or the senior people in your company) to figure out the best setting for that knob and all the other knobs for your company to achieve its goals.

Best of luck.

Collapse
 
renannobile profile image
Renan Lourençoni Nobile

Thanks for your insight, it really helps. I'll talk to my team about this. I don't think we'll change the way we're working at this point, but maybe, we can improve some aspects becoming more productive.

Thread Thread
 
bosepchuk profile image
Blaine Osepchuk

You're welcome.