The DoD recently mandated shorter release cycles for software programs, as covered in a Fed News Radio piece (http://www.federalnewsradio.com/?sid=2264122&nid=35). Five decades of IT best practice finally makes it onto the radar. Hooray, kudos, congrats. But, we still have a long way to go, judging by the magnitude and number of misconceptions communicated in this short piece. Here is a classic:
Service oriented architecture is about the tooling? Wrong. The heavy lifting is determining the services within your portfolio, and then making them act as services, which often involves significant organizational change (both human & procedure). Tooling helps, but this tools-first practice just feeds the billion dollar disaster parade of: buy first, figure out what to do with it later. For a review of mile markers on this trail of tears, see http://www.whitehouse.gov/omb/blog/10/06/28/Cutting-Waste-by-Reforming-IT.
And another widespread misunderstanding is highlighted by these statements:
And the problem with IT projects is acquisition? Federal IT acquisition is buying $80B/year of services and products, but not getting $80B of value for that purchase. Where are the program staff who know how to run an IT project? ...who know how to make a business case? ...who know how to build a roadmap to generate steady results? ...who value the people and skill part of the equation?
Framing IT problems as acquisition problems ensures that we will continue to see large COTS purchases that fail to deploy. Well, perhaps they'll fail faster.