Everyone in IT is familiar with cost explosions. Here is the implosion scenario:
- Step 1: Take a $200,000,000.00 ERP.
- Step 2: Optimize convoluted business logic - at least 50% scope reduction.
- Step 3: 90% reduction of the remaining code - retiring the tedious CRUD plumbing that hasn't changed since the 1970s relational database invention.
Impossible with conventional technology.
- Step 4: 75% code reduction - eliminating "user-friendly" DIY administrative UI to tweak thousands of system features - never touched by
the end users. This step is impossible w/o Step 3 - freeing engineers to instantly implement customer-requested features.
- Step 5: Fewer engineers communicate faster and require fewer coordinators. Near-perfect collaboration doubles the productivity - meaning another 50%.
- Step 6: Fewer well-paid and adequately motivated programmers make fewer mistakes. They start to care instead of throwing code over the
fence to QA. Reducing expensive bug-fixing cycles results in another 50% productivity boost. Not to mention the quality impact on the priceless customer
- Result: $750K, which is 0.3% of the original $200M cost.
Facilitation of collaboration, "teamwork" poster motivation, or another managerial wizardry?
No, the technology doing the heavy lifting, and programmers writing 100x less code.