In the corporate world determining the scope of work that produces the minimum feature set to solve the need is so important when you are seeking approval from the higher-ups on your project.
For every project or feature-add I determine the minimum needed to make it usable, start making money from it, or realize the benefit. I pitch it like: this much effort will get us to here, we can launch, then bang the rest out with continuous releases until complete. If the fully-completed project takes more than a couple months it may get cancelled halfway through because priorities shifted, so bite-sized chucks are important.
Finance wants to start depreciating the capital hours ASAP, execs want to see benefits ASAP, and customers want to see progress on their feature ASAP.
Now with that first release you can gather feedback and maybe the features you planned aren't really needed, the basic features are good enough and priorities have changed, or customers want something different than they thought they did. You haven't wasted 6 months working to be feature-complete to find that out.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
In the corporate world determining the scope of work that produces the minimum feature set to solve the need is so important when you are seeking approval from the higher-ups on your project.
For every project or feature-add I determine the minimum needed to make it usable, start making money from it, or realize the benefit. I pitch it like: this much effort will get us to here, we can launch, then bang the rest out with continuous releases until complete. If the fully-completed project takes more than a couple months it may get cancelled halfway through because priorities shifted, so bite-sized chucks are important.
Finance wants to start depreciating the capital hours ASAP, execs want to see benefits ASAP, and customers want to see progress on their feature ASAP.
Now with that first release you can gather feedback and maybe the features you planned aren't really needed, the basic features are good enough and priorities have changed, or customers want something different than they thought they did. You haven't wasted 6 months working to be feature-complete to find that out.