The Software Customization Pyramidposted by Anna Mar, April 04, 2011
Businesses tend to over-customize software. Ideally, businesses should only customize software that represents a competitive advantage.
Competitive AdvantageSoftware that represents a competitive advantage:
- improves revenue or cuts costs
- is more advanced than any COTS package with comparable functionality
- is a core competency of the business
It is a sign of healthy IT planning when a business spends most of its software customization budget in areas of competitive advantage.
Examples: Algorithmic trading systems (investment banking)
Tactical SolutionsTactical solutions — software that is recognized as non-strategic but is necessary to keep the business going.
Tactical solutions are a waste of money and are a sign that IT planning has gone wrong. Nevertheless, customization is often warranted to avoid business problems.
Examples: legacy software that would be too expensive to replace but requires constant customization to keep up with business change.
Standard SolutionsAreas where highly optimized COTS packages are available — packages that would be tough to beat with a custom solution.
Businesses should endeavour to leverage COTS packages for standard solutions when possible. The only exception to this rule is when the software is so expensive that it is unlikely to have a reasonable payback.
Customization of standard solutions should be kept to a bare minimum.
Examples: ERP, CRM, Billing, ESB, BPM etc....
Vanilla ToolsVanilla tools implement such generic functionality that it would be foolish to customize them.
Examples: office productivity, wikis, blog software, unified communications, web servers etc...
This is the way to prove to your stakeholders that your recommendations are not just whims. |
Learn about the 10 most important patterns for SOA success.|
Understanding your vulnerabilities is the first step to managing risk.|
The exciting world of ITIL metrics.|