Projects: Integration - Baseline
Home arrow Projects: Integration arrow Page 3 - Requirements Management: Kaiser Permanente's Rx for Better Projects













Renew Your Subscription

Projects: Integration



Requirements Management: Kaiser Permanente's Rx for Better Projects



By Doug Bartholomew

  Table of Contents:
  1. Requirements Management: Kaiser Permanente's Rx for Better Projects
  2. ' Defining Requirements '
  3. ' Kaiser Permanente Base Case '

HMO Kaiser Permanente needed tighter alignment between its software developers and its business goals. A new requirements management system proved to be strong, but effective, medicine.

Rate This Article:
Add This Article To:

Requirements Management: Kaiser Permanente's Rx for Better Projects - ' Kaiser Permanente Base Case '


( Page 3 of 3 )

Kaiser Permanente Base Case

Headquarters: 300 Lakeside Drive, Oakland, CA 94612
Phone: (510) 271-5910
Business: Health maintenance organization providing medical plans and comprehensive medical services.
Vice President of Applications Delivery: Kelly Cannon
Financials in 2005: $31.1 billion revenue; $1 billion profit.
Challenge: Improve and standardize the software requirements development process.

BASELINE GOALS:
  • Expand KP HealthConnect from an internal network used by 12,000 physicians, to allow 8.5 million members to obtain patient records, make appointments and check lab results online.
  • Build 7 new hospitals, in addition to 30 now in service, by 2012.
  • Expand 19 existing hospitals to accommodate growth, including 13 under the company's seismic replacement program, as part of a $20 billion construction campaign.

    THE PRICE OF POOR PRACTICES

    70% TO 85% OF ALL PROJECT REWORK COSTS are due to errors in requirements, says a 1997 article in American Programmer.
    30% TO 50% OF THE TOTAL EFFORT EXPENDED on a software project comes from rework, according to an estimate by Borland Software.
    ALMOST 50% OF DEFECTS IN SOFTWARE PROJECTS can be traced to errors in requirements, Borland says.
    71% OF FAILED SOFTWARE PROJECTS suffer from poor requirements management, according to a paper presented at the 1999 Applications of Software Measurement Conference.



     
     
    >>> More Projects: Integration Articles          >>> More By Doug Bartholomew
     


  • Sponsored Links
  • Get up and running in as quickly as 30 days with BI. Learn how today.

  • FREE Securing Smartphones & Tablets for Dummies Book from Sophos
  • 5 New Technologies That Will Change Enterprise ITAdvertisement
  • Build an IT Infrastructure That Delivers the Future
     
  •  
    FEATURED SPONSORED ARTICLES

    FEATURED SPONSORED VIDEOS

     



    LATEST STORIES


     

     


    Advertisement
    rss graphic
           Baseline Newsletters