Advertisement
*
Reproduction permitted for personal use only. For reprints and reprint permission, contact reprints@wistechnology.com.

Technology audit rips poor planning and oversight

Madison, Wis. - Problematic state information technology projects largely are the result of inadequate planning, a lack of oversight, and inadequate collaboration between the Department of Administration and executive branch agencies, according to a long-awaited report from the state Legislative Audit Bureau.

The audit report, which was a full year in the making, was ordered after concerns were raised about large information technology projects in several state agencies, including the Departments of Transportation and Revenue, and the University of Wisconsin System.

The Audit Bureau identified 184 information technology projects that state agencies have begun or completed between 2004 and 2006 - projects that currently are expected to cost a total of $291.7 million. The Bureau said most problems occur in planning for complex, high-risk projects, and the report made several recommendations to improve project planning, monitoring, and oversight.

"It constantly amazes me how we could blow that much money and not put in place mechanisms to prevent it from happening," said State Sen. Robert Cowles, R-Green Bay, a member of the Joint Legislative Audit Committee.

The audit review focused on software customization and development projects of executive branch agencies and the DOA's efforts to consolidate the state's IT resources.
Advertisement
In particular, six on-going projects have experienced difficulties and delays, with a combined cost of $122.7 million at completion. A seventh project, the Department of Workforce Development's customization of software for its Enhanced Automated Benefits and Legal Enterprise System (EnABLES), was suspended in February of 2007 after five years and a cost of $23.6 million.

One of the downfalls cited in the report is a failing to adequately define a project's final functions. For example, the DWD failed to identify the functions that would be included in the state Unemployment Insurance Tax Enterprise System (SUITES), a project that is four years behind schedule and $18.7 million over budget.

Also among the failings cited in the report is the underestimating of project complexity. The report said a Department of Revenue contractor underestimated the complexity of adapting the sales and use tax software component of the department's Integrated Tax System. As a result, significant programming errors ensued, increasing costs by $5.7 million and comprising the accuracy of sales and use tax distributions to counties and professional sports districts.

The audit report also said two of the three DOA projects that involve statewide consolidation of IT resources - the consolidation of server hardware and software and e-mail consolidation - have been hindered by poor planning. A third consolidation project, the Integrated Business Information System, benefited from early planning efforts, but revisions in the project's anticipated costs and benefits will require close monitoring.

Recommendations

The report noted that DOA has broad responsibility to monitor and control the IT projects of executive branch agencies, and that responsibility includes the establishment of performance measures for evaluating progress. However, because the department's management efforts have focused on is own troubled e-mail and server consolidation projects, its role in collaborating with agencies on large, high-risk projects has been inadequate.

The report recommended agencies to report by Oct. 1, 2007 to the Joint Legislative Audit Committee on seven of the large, high-risk projects the Audit Bureau reviewed. In addition, it recommended that DOA report to the committee on its own progress in selecting a prescribed format for agencies' annual strategic plans for IT and a methodology for identifying high-risk programs.

Another recommendation for the DOA is to report on progress toward establishing planning standards for large, high-risk projects, enhancing project monitoring, and establishing policies for the use and monitoring of the state's master lease program to fund IT system costs.

"The DOA has to be the point agency on this," Cowles said. "They are entrusted with managing these systems."

Legislatively, the report also recommends reactivating the Joint Committee on Information Policy and Technology and the IT Management Board. Cowles, who last month expressed hope that the report would include recommendations for the Legislature, offered support for the Audit Bureau's legislative recommendations.

Cowles also said that he would be very cautious about authorizing additional requested funds, including $35 million more for a new data center that is behind schedule. He said both the Legislature and the Doyle Administration have become enamored with information technology projects, and probably had too much going on at once.

"This [information technology] is a big part of our budget, suddenly, and we need to pay more attention to it," he said.

State Rep. Phil Montgomery, R-Green Bay, chairman of the Assembly Speaker's IT Projects Task Force, said the task force would carefully consider the Audit Bureau's suggestions to reactivate the Joint Committee on Information Policy and Technology and the IT Management Board, as well as require more frequent reporting during "all IT implementation projects."

Corrective actions

Some agencies already have drawn lessons from their failures. The University of Wisconsin System, which spent $26 million before abandoning a project involving the implementation of appointment, payroll, and benefits software by Lawson, is among those that already have taken corrective steps.

Ed Meachen, associate vice president of learning and information technology for the UW System, has said the Lawson debacle was due in part to a lack of communication between an executive steering committee and the system's executive leadership. On large projects, he said the system now will engage executive leadership across the system, as well as a subset of the UW Board of Regents.

Meachen also said the system has directed a Common Systems Group to monitor the spend rate on projects, and it now mandates project management experience or certification on large IT endeavors.

“This incredible disaster got us to think through the executive leadership role in this, so we will not forget that one,” he told WTN late in 2006, “and I think all the literature on implementing these enterprise systems talks about that.”

Related stories

State of Wisconsin dumps another tech project

Oskar Anderson to succeed Miszewski as head of state technology division

GOP lawmaker faults Doyle for IT problems

State IT failures are not inevitable

Comments

Robert Merrill responded 2 years ago: #1

Nothing in the report really surprised me. These projects seemed to get in trouble for the usual reasons. Maybe that's what's so frustrating.

I'm skeptical of calls for more oversight. In its article on the audit, the WI State Journal also said that a well-regarded senior project manager just left because she was "very, very tired" of fighting "interference from her superiors." So instead of more oversight, we need better oversight--wiser and more informed.

Whenever a project goes over schedule and budget, we tend to blame the project and not the schedule and budget. But unless you are rigorous and impartial, underestimating is all too easy.

All projects have a lot of uncertainty at the evaluation and funding stage. People want to get projects funded or win bids, and they tend to confuse uncertainty for negotiating room. So scope gets driven up and cost and schedule driven down, leading to a set of expectations that can only be met if everything goes perfectly. Murphy takes it from there.

Quality IT Oversight responded 2 years ago: #2

Quality IT oversight is hard to find. It requires a commitment of both high quality business management and IT professionals from the business areas. Who has time? If all you are going to do is make political appointments, it will fail. It probably is no accident that the oversight boards the LAB audit mentions disbanded: they probably felt ineffective and didn't want to make the effort necessary to gain the low level detail knowledge of state institutions necessary to be effective. Of course, the best example is Matt Miszewski, the previous CIO and political appointee. Well, you did not have such waste of IT resources and budget under anyone else's watch as you had under his. If you want quality IT oversight, let's put together a board of business management and IT management from the agencies themselves, give them a clear mandate of authority and direction, rather than making a bunch of political appointments (connected people just wanting to make a name for themselves).

Patricia Cusma responded 2 years ago: #3

I am outraged that, in a time when all Wisconsinites at both the state and local level, are making VERY hard decisions on appropriate spending of resources, that this level of incompetence has been allowed to play out over an extended period of time. Issues identified by the audit appear to be basic project management competencies, and I do not find any acceptable excuses for this poor performance.

Carol Stotts responded 2 years ago: #4

The fact that it took a year to come to these conclusions is as detached from the speed of business as are these government lead projects. Looking at the monies spent vs. value earned, I cannot help wonder what measures define the true status of each project and who is accountable to achieve that value. When a project starts to go south, what are the expectations? Does anyone demand corrective action, or is the acceptable practice to toss responsibility “over the fence,” so to speak, for someone else? I call it the fictitious "they syndrome" - if “they” would just do something. I can see how team leaders and members could become frustrated working in an environment without effective governance or risk management practices. The state of Wisconsin seems to have separated professional performance from performance results. These failures reflect poorly on the entire IT profession. Governance, risk management, and value-based delivery linked to time and cost should be required in future ventures.

kay plantes responded 2 years ago: #5

I would love to know how often the "lowest price bidder" won the contract for the failed projects. All too often, government is penny-wise and pound-foolish because of an RFP process that rewards the lowest price bidder, not the firm that will get to the right answer on time and on budget.

Tim Nuckles responded 2 years ago: #6

All good comments. More is not always better. We don't simply need more oversight, we need better oversight.

Cheaper is not always better, and especially so with technology projects. I would certainly hope that the Department of Administration and the various state agencies have not been buying technology products and serices on a "lowest bidder" basis.

Tim Nuckles
www.nuckleslaw.com

-Add Your Comment

Name:
E-mail:

Comment Policy: WTN News accepts comments that are on-topic and do not contain advertisements, profanity or personal attacks. Comments represent the views of the individuals who post them and do not necessarily represent the views of WTN Media or our partners, advertisers, or sources. Comments are moderated and not immediately posted. Your email address will not be posted.

WTN Media cannot accept liability for the content of comments posted here or verify their accuracy. If you believe this comment section is being abused, contact edit@wistechnology.com.

Advertisement
Advertisement

-More Stories

WTN Media Presents