SPI Versus SCI

by Jim Highsmith

I was recently asked to give a talk to a group of Irish software companies about software process improvement (SPI). As I thought about the topic, I realized that to most people, SPI conveys expectations such as deterministic, comprehensive early planning; a detailed process focus; waterfall (serial) lifecycle (planning, requirements, design, etc.); extensive documentation deliverables to show progress; and internal metrics. My comment on this traditional view of SPI was that it would leave your company well prepared to compete in 1985.

Password Protected Cutter Consortium clients, please log in:


This document is available to Cutter Consortium Resource Center clients only. Retrieve your password.
If you would like further information about how to become a client, please contact us at +1 781 648 8700 or sales@cutter.com, or you can Request Guest Access.
SPI Versus SCIThu Jun 08 16:30:14 CDT 2006

Become a Member

Research and inquiry privileges, plus regular strategy meetings with Cutter's pioneers and leaders in the Agile movement, are just some of the perks! Talk to Cutter today about trial membership, including access to research, webinars, podcasts, white papers and more.

Request trial membership