Prescription for a Healthy IT Project (Post 3 of 6)

job-interviewIn my last two posts I’ve been using the problems with the newly launched federal health insurance website as the jumping off point for a broader discussion of how to engage and work with vendors who can meet your expectations. Just like the process of hiring employees, engaging an IT vendor should involve a rigorous interview process. Always take the time to review the firm’s past work and to meet the actual people who will be involved with your project. As I describe in my book, Building a Winning Business, it’s also wise to think about the following points during the interview:

  • Do they ask questions? To create a solution, they’ll need to understand the problem. Asking questions shows they care and that they’re prepared.
  • Do they seem too good to be true? For example, if you’re considering five firms for a project and four of the five have stated that your delivery date is unrealistic but one firm can, somehow, hit your deadline, it’s highly possible they just may be telling you what you want to hear to get your business. In this scenario, it’s also highly possible that they will disappoint you by missing the deadline once you’ve signed on the dotted line.
  • Do they pay attention to the details? In the sales process, you’re most likely going to see the best side of the firm. If they’re late or don’t follow through on small details in the bidding process, it won’t get better once you’ve engaged them.
  • Look for a fit on a cultural level. Similar to having employees who fit the culture of your company, look for a cultural fit with your outside provider.

The bottom line: hiring a vendor should be undertaken with the same level of preparation and scrutiny given to hiring a new employee. Ask tough questions and pay close attention to what is said – and left unsaid – by all vendors that you consider.

Next time: how to get your new vendor relationship off to the best start!

$10K Training Sweepstakes, Free Pi Workshops, Scholarship, Free Book

Building-a-Winning-Business-BookAs we enter 2014, Intertech and I have free learning opportunities and some new support programs for students:

  1. With Intertech’s training sweepstakes, we’re giving away $10,000 worth of training for a team of up to four IT professionals.  Throw your hat in the ring and register today!
  2. Thanks to Jim White, my business partner, you can learn Raspberry Pi development in a series of 10 Raspberry Pi programming workshops on Intertech’s blog.
  3. If have a kid involved in a Lego or Robotics League in Minnesota, watch Intertech’s website for our upcoming announcement of our support program for up to 50 teams.  In addition, we are going to help sponsor the Minnesota First Regional competition in March ’14 at the University of Minnesota.
  4. Watch our website for the announcement of our upcoming scholarship.  Offered to an undergraduate computer science or STEM student, the Intertech Foundation will be awarding $2,500 to an undergrad student in ’14.
  5. Finally, for everyone (no application or sweepstakes required), I’m giving away a copy of my book Building a Winning Business.  Feel free to share this post or the link to the PDF.

Let’s make it a great ’14!

Tom

Prescription for a Healthy IT Project (Post 2 of 6)

intervewing-as-a-team“It would have been better to have more time,” Cheryl Campbell, a senior vice president at CGI Federal, the site designer, told the House Energy and Commerce Committee during a recent hearing on why the new federal health website has performed so poorly since its debut on October 1.

Ms. Campbell’s comment makes me wonder about the planning process (or lack thereof) behind this colossal project.  In my book, “Building a Winning Business,” I discuss the key role that planning plays in solid project execution. According to Gartner Group, 75 percent of software projects fail due to lack of technical consideration or poor planning.

How could a project of such magnitude been approved without a well-planned approach and realistic implementation timeline? Did CGI group agree to an unreasonable timeline in the beginning in order to win the contract? Is it possible no one from the government asked CGI the tough questions during the vendor interview process?

No matter how impressive a vendor may appear to be on paper, it all comes down to the specific people assigned to your project and their ability to get the job done. In Building a Winning Business, I dedicate an entire section to hiring and working with vendors. Rule number one: take the time to pick a good provider! This means looking at a firm’s long-term track record and the team who will be handling your work. It all begins with the vendor interview process, which I’ll explore in my next post in this series.

Prescription for a Healthy IT Project (Post 1 of 6)

healthcare-websiteOver $600 million! That’s how much the federal government has reported spending – so far – on information technology for the federal health insurance website HealthCare.gov.  From errors to long waits, it’s been a debacle.

Lack of adequate testing by the IT vendor, CGI, also has been blamed for the site’s navigational difficulties and extremely slow load times. In case you’re not familiar with it, CGI is the world’s fifth-largest information technology services company and the largest IT company in Canada, where it is headquartered.

As of Oct. 25, 700,000 U.S. citizens had filed applications for health insurance. The nagging tech issues must be resolved, and soon, if the predicted seven million interested Americans are going to be able to sign up for coverage through the exchanges by the end of the six-month enrollment period on March 31, 2014.

As the owner of an IT consulting business, I feel for the folks at CGI. Managing a project of this scale involving the federal government no doubt was beyond challenging. Still, when I heard that complete end-to-end testing had not taken place until mid-September, I had to scratch my head. With so much on the line, comprehensive testing tied to established milestones should have been happening early and often throughout the development process.

How could such an obviously world-class IT vendor overlook such a basic software development principle? I’m not going to speculate since I was not on the team, but I do think this very public software development fiasco creates an opportunity to dust off some of the time-tested software development principles described in my book, “Building a Winning Business.”  I will discuss those principles in my next five posts and hope that by the time I’m finished with this series of posts, the new federal health care website finally will be working efficiently!