Reply to thread

Message: <blockquote data-quote="Dausuul" data-source="post: 6420398" data-attributes="member: 58197">Well, just because you can build an enterprise-scale product doesn't mean you will. The rate of failure in IT projects is very, very high, and the bigger the project the higher the chance of failure. There are a whole lot of things that can go wrong. I stressed the need for good management because this is very often what's lacking, but there's plenty of room for the devs to screw up, too.That is indeed exactly what it looks like. We call that "scope creep," and it's the devil whispering in the ears of developers and managers alike. Management wants more features to show to the higher-ups and advertise to the end user. Developers want to add bells and whistles and do cool fun stuff instead of workaday, "Today I will build a login page" tasks. And every new feature adds complexity and slows down the project.It's one of the reasons a prototype is so valuable: It gives you a working design, a set of features that you can legitimately call complete. When someone proposes a new feature, it's easier to say, "No, we're not going to build that yet. It's nice but it's not essential. Put it off until we have our scaled-up prototype working."</blockquote>