Kaiser Permanente's Rx for Better ProjectsBy Doug Bartholomew | Posted 08-11-2006
For most organizations, software development is seldom easy. Projects are often fraught with miscommunication between the information-technology department and the business units. Key requirements may get short shrift or be omitted altogether until the last minute, when both costs and tempers are likely to soar.
Now, one of the nation's largest health maintenance organizations is revamping the front end of its development process to ensure a tighter alignment with its business goals. As part of a sweeping overhaul of its software development setup, Kaiser Permanente, the $31.1 billion HMO, has installed new software and processes for defining the business requirements of new systems.
About 700 of the Oakland, Calif., company's 2,000 software developers will be using the development system, which is based on a requirements definition and management package from Borland Software.
Ultimately, Kaiser's initiative will tackle not only software design, testing and change management, but also how costs and project length are estimated and the process is measured.
"If there is a change in a project's scope, we want to know the impact down to the dollar," says Aaron Schleifer, project manager for requirements development management at the HMO.
The company's goal is to reduce errors and speed project development by standardizing the way the organization's developers outline corporate needs for new systems.
At Kaiser, which serves 8.4 million members through 30 medical centers staffed by 12,000 physicians, there are a few hundred development projects underway at any given time. It's no surprise, then, that the payoff of a streamlined process with fewer errors and reduced rework can be huge.
Read the full story on eWEEK.com: Kaiser Permanente's Rx for Better Projects