One More Thing

<p>"One more thing". &nbsp;We <strong>always </strong>have one more thing to do in software development -- whether our customer asks us for one more feature, or we task ourselves with going beyond the requirements, the challenge remains: <strong>how much is enough</strong>?</p> <p>What is overengineering? &nbsp;How do we know when our software is ready to launch? &nbsp;When customers can always come back to us with more work -- one more thing -- when do we know when to stop adding more features? &nbsp;How can we reduce scope creep in our projects while still overdelivering? &nbsp;Does it even make sense to overdeliver? &nbsp;What "one more thing"s make sense as developers, and what does overengineering even look like?</p>