Before diving into the details, it’s worth clarifying the purpose of this exercise.
This was not about finding a “correct” number. It was about understanding how realistic constraints, experience gaps, and risk factors compound in real software projects and why top-down plans often fail once those factors are made explicit.