Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

13
  • 2
    What would you consider efficient? If you're talking about a project with ten million lines of code involving multiple organizational structures, you may need all this infrastructure. If it's just 100,000 lines, not so much. Commented Jun 10, 2014 at 16:38
  • @RobertHarvey < 10k LOC per release here. 99% of the work is onboarding systems to ETL processes, absorbing changes from upstream systems and requests from downstream systems, and creating SSRS reports. Wondering why a process like I've mentioned in the last 2 lines isnt used in the industry Commented Jun 10, 2014 at 16:40
  • 1
    Looks like a system where, when the product is done, they know beforehand the features they will get, and that it will stable... it is way more efficient than letting the programmers guess what is needed, and asking the stakeholders about it after finishing the modifications. Commented Jun 10, 2014 at 16:47
  • 11
    You're complaining about waterfall, go read about it and realize everybody else recognizes it's terrible inefficient too. That said it's still used because for all it's inefficiency, in a variety of cases given the correct set of constraints, it actually works to the point of getting well-functioning IT products and services to business users. While it's unarguably inefficient, sometimes the inefficiency is worth it for the decreased risk waterfall has in the right scenario. It sounds like it's working well at your place, even if frustratingly overbearing... Commented Jun 10, 2014 at 17:13
  • 2
    Agreed that this sounds like waterfall development. I'd suggest you contrast against methodologies like Extreme Programming, Agile, and DevOps. Sometimes waterfall is the right answer (e.g. NASA can't iteratively launch a rocket), but usually it is frowned upon in general software development. Commented Jun 10, 2014 at 19:30