Former Homeland Security CIO Richard Spires says the main to running big IT programs — and recovering once they fail — is first-class program management.
Few CIOs understand the scope of disciplines had to manage large-scale IT projects quite like Richard Spires. He led probably the most largest business IT modernization efforts ever undertaken by the government. This eventually landing him the pinnacle IT spot on the IRS, and later, a deputy commissioner role accountable for operations.
The lessons he learned on the IRS (particularly the significance of program and project management capabilities) were sharpened when he became CIO of the dept of Homeland Security — a position he held for just about four years before leaving this year to begin his own consulting firm.
For Spires, the core principles for recovering from an IT project failure are the identical ones he would use for shepherding a major IT project within the first place: having the correct program management talent and talents in place.
“I’m still a believer, nothing replaces the correct of management discipline” on large IT projects, Spires told us. When a manager is stressed, “you are inclined to like to shortcut the discipline to get the functionality in place. You cannot take shortcuts and expect things to head any faster.”
[ For one more federal IT exec’s perspective on effective project management and recovery, see Lessons For HealthCare.gov: Project Crash Recovery. ]
“It is usually been my experience that it’s better to take a bit more time and get [the IT development] right than it really is to continue to hurry to get the subsequent release into production for users — since you don’t need to disappoint them a second time.”
In a recovery, just as with an IT project rollout, Spires stressed the desire for a powerful development and build process, hopefully moving to an automatic build process so that you can cycle-build faster, particularly if you end up attempting to get over a failure. Similarly, you wish to automate and accelerate testing.
He also emphasized taking stock of the location, understanding where the true issues are, and picking a plan. “i think for those engaged on HealthCare.gov site” developed by the Centers for Medicare and Medicaid Services. “There’s tremendous pressure from above to get things fixed. It takes strong program management to make the case that announces, ‘This is what we have to do to repair this’ after which follow those guns.”
Spires recognizes there are occasions when bringing outside help could make sense to hurry up the recovery process. Outside experts can assist in the event that they are the proper of folks inside the technical areas where assistance is needed most. “You should be careful bringing in too many new people, though, because their learning curve can decelerate the remainder of the team. It is a tradeoff.”
It’s equally important to reassess the rigor of your management disciplines and make adjustments. “What I’ve seen in government too often is you could have organizations that just should not have much experience delivering large-scale IT programs. They do not understand the complexity level; they do not understand the discipline you should bear.” A few of that’s an ignorance issue. In other cases, it is a cultural issue where agencies fail to devote the mandatory talent and disciplines to managing large-scale IT projects.
Should an IT project with the choice of issues HealthCare.gov has faced simply be taken down and repaired offline? The truth that the positioning had 400 software bugs that required fixing over the last two months speaks to the truth that it just wasn’t able to be launched — and to the underlying loss of effective program management. “Given the collection of problems… if politics wasn’t a controversy, i’d have immediately shut it down.”
Keeping a website up helps you locate new things, but it surely takes precious energy to run the location while making repairs. Best-practices would like taking the positioning down, making needed repairs, and relaunching it in a pilot mode with a small set of users. Meanwhile, a recovery team would do rigorous performance testing behind the curtain.
Another facet in a recovery is communication — both internal and external. Contained in the operation, it’s crucial to have daily status reviews. Team leaders “have to have the heartbeat on what is going on” and feature a forum to find and jump on issues. Communicating outwardly is often more complicated, especially in a heated political environment. From a best-practice perspective, Spires is large believer in transparency. “It doesn’t suggest you will want communicate daily.”
When he ran the IRS Business Systems Modernization program, “we might have monthly program reviews, and that i would send the result of the reviews to all our stakeholders, including as much as the Hill.” The key is to inform it find it irresistible is. This builds trust and rapport together with your stakeholders. But perhaps the largest communication effort a CIO could make is to coach senior leaders of a company at the institutional importance of establishing a culture that values program management capabilities and disciplines.
There’s no single migration route to the subsequent generation of enterprise communications and collaboration systems and services, and Enterprise Connect delivers what you should evaluate all of the options. Register today and find out about the total range of platforms, services, and applications that comprise modern communications and collaboration systems. Register with code MPIWK and save $200 at the entire event and Tuesday-Thursday conference passes or for a Free Expo pass. It happens in Orlando, Fla., March 17-19.
More Insights