DEV Community

loading...

Discussion on: What's Common Between Opera Houses And Software Projects, or 10 Reasons Software Developers Go Overtime

Collapse
mason_james2 profile image
James

I enjoyed this article a lot. Firstly, I liked the idea of comparing software protects to building opera houses, instead of just houses. This makes so much sense, and is definitely something I'm going to incorporate into my behavior going forward.

I would add to the optimism category, that project managers sometimes forget that new features take more money AND time. I was leading a small project and promised our customer we could deliver more features they wanted, if they gave us more money. I completely forgot to adjust our deadline, and realized my error much later (thankfully, overtime was approved and we still delivered on time). The lesson: always remember that new stuff costs both money and additional time; it seems obvious, I know.

Collapse
ice_lenor profile image
Elena Author

Thank you, James!
At least you didn't forget the money :))

Collapse
ice_lenor profile image
Elena Author

Forgot to mention - I feel like your situation is happening quite often, so I have the whole section dedicated to it: "Reason 3: Changing Requirements".

Collapse
mason_james2 profile image
James

Yeah, requirements change a LOT. Luckily, the project I'm referring to had very few requirements change when I was running it. Others in my office haven't been so lucky and deal with changing requirements on a constant basis.

As you said in your other comment: at least I remembered the money though.

Forem Open with the Forem app