We all have overextended sometime in our life.
But what about projects that overextend, due to a lack of a true intrespect of the magnitude of what is to be accomplished, the likely workforce and time to accomplish the objectives, and the maintenance and information needed to prefrom the feat.
I believe for the most part, one has seen this throughout the emu development (at least for UOX, and at least Wolfpack in its early years, and perhaps others).
Lets say one wants do do a new emu. What all should it do?
Once that list is established, develop what all is needed data wise to accomplish that. Is all the data known and readabily available. Is the data known, but not documented (thus requireing a documentation effort to support maintainablity as the work force changes)? What is a realistic estimate of the CONTINUED workforce available to the problem?
Now take those answers and compare it to the list. Is the list still feasible ? Can some features be delayed through proper design, to be addressed later? Are some desires just to do something the now "standard" way, but not necessarly pressing or significatnly better (and thus can be delayed)?
One rarely sees emus do baby steps, and ensure they can be accomplished, debugged, and stable, before moving to the next logical transistion.
Overextending...
Moderator: punt