6 IT fads you should warn your customers about
There are many good information technology innovations, but not all the current fads are good for government IT. Some trends are bad in general, and some are very bad for government IT managers in particular.
There are many good information technology innovations, but not all the current fads are good for government IT. Some trends are bad in general, and some are very bad for government IT managers in particular. Others are good for some uses but not others. Let’s examine a few of the IT industry fads that make bad matches for government IT, and why they are bad.
1. Cloud computing is a red herring. Chasing this fad now, before standards are in place and security concerns are dealt with, is a complete waste of time. Also, it still needs to be sorted out whether cloud computing is primarily a utility-based hosting solution, a new application-development model, or both. Although Web 2.0 start-ups can afford the risk associated with these desired IT cost savings, the government should take a wait-and-see attitude.
2. Web 2.0 is not pixie dust. Anyone who has witnessed a crazed mob of sports fans on an alcohol-induced rampage would agree that crowds are not always wise. In the same way, Web 2.0 technologies are not a panacea nor should they be the No. 1 priority for government IT. Web 2.0 should be relegated to areas that tap its strength, which is primarily nonattributed commentary and workgroup collaboration.
3. Agile development is a programmer’s fantasy and a manager’s nightmare. In my more than 20 years of software development experience, I have never met a government program manager who is available on a daily or even weekly basis to help design an application on the fly. Extreme iteration and pair programming are almost exclusively programmer perks and not in the best interests of government IT. Please don’t build the next space shuttle that way.
4. Data standards cannot be market-driven. Although the government sponsors many emerging marketplaces, such as green energy, a standards marketplace should not be one of them. I have said this many times before, and I will now say it again: Data standards are not amenable to competition. Instead, government data standardization should be seen as one of those “inherently governmental” activities. Stay away from any standards development organization with a business plan.
5. Service-oriented architecture has not yet convincingly addressed older applications. SOA is absolutely the right approach for new application development, but its Achilles’ heel is its failure to come up with a workable transition strategy for existing applications. Thus, SOA pilots get pigeonholed into a “nice dream” limbo or a “maybe someday” wistfulness. Finally, the coarse-grained “just wrap it” approach rings hollow when the devil delivers the details.
The key to understanding these six warnings is to understand that government IT operates as a mission multiplier and not as a cost center. Just as there are inherently governmental business functions, there are inherently governmental IT practices. Government can no longer dictate the IT landscape — as evidenced by the failure of Ada — but government IT managers must still be keenly aware of the unique requirements for government IT systems. The latest IT fad might be well-suited for businesses but ill-suited for the government.
NEXT STORY: New IBM unit will extend public-sector solutions