3 ms·

This sounds more like a problem of scope creep than unexpected complexity

• adorton 5y ago
  Scope creep happens when you discover new requirements after defining a project scope and delivering an estimate. The type of analysis outlined in the article is helpful to define a sane and reasonable scope upfront, to hopefully avoid creep down the line.
  • Jensson 5y ago
    > Scope creep happens when you discover new requirements after defining a project scope and delivering an estimate. The author defined project scope. Student discussed and came up with 4 hour estimate. Then after that estimate was made the author added a lot of requirements and said the student estimate was too low.
• ClosedPistachio 5y ago
  It's in the article: > The goal isn't to fall into a feature rabbit hole, but rather to understand your assumptions about the project. If I don't do this exercise and I try to build it, then I will often run into two or three crux issues that I could have easily known about from the start. Don't go implement every feature idea you come up with from this exercise!
• alasdair_ 5y ago
  This is only true if you believe software development to be the practice of slavishly implementing ill-defined requirements regardless of what the user actually wants.
  • rockstep 5y ago
    I prefer to think of it as pushing out minimum viable products as soon as possible and implementing finer details afterwards. I think that's a principle of being agile.