3 ms·

> make a total reset for version 2.0 and redo v 1.0 correctly. That's how I usually work (in personal projects). I wonder what it would take to convince manage

• aahortwwy 5y ago
  > I wonder what it would take to convince management to do the same. Build the redo time into your estimates. Non-technical management has no concept of what's involved in building software. They don't need or particularly want to know. They care about things being "done." You don't need to convince them of anything, you just need to consistently and reliably show progress in a way that they can comprehend. It's very irritating to see no progress for a month, then see a demo of something that appears to do everything you asked for, then hear that it won't be "ready" (whatever that means) for another month because the whole thing needs to be redone. It's very reassuring to see demos every two weeks, each one showing an obviously incomplete product, but with clear progress between each demo culminating in a completed and delightful product after two months. The actual development process for the two scenarios above can be exactly the same, it's just how they're messaged. This is "managing up."