DocumentCode
1367639
Title
Software process impediment
Author
Pressman, R.
Author_Institution
Pressman Assoc. Inc., Orange, CT
Volume
13
Issue
5
fYear
1996
fDate
9/1/1996 12:00:00 AM
Firstpage
16
Lastpage
17
Abstract
I´ve been involved on software people and process improvement consulting for more than 15 technology to years. Along the way, I´ve noticed a significant change in people´s perception of the worth of software engineering practices. But remarkably, relatively little has changed in how companies approach SPI. For all the debate about content and appropriateness, the SEI´s Capability Maturity Model has been well defined. Unfortunately, it represents a destination, not a road map. Too often, organizations that take the SPI journey are looking for a magic route: a single, one-size-fits-all strategy that guarantees higher process-maturity levels. In reality, dozens of possible strategies will get the organization to its goal
Keywords
software development management; capability maturity model; process-maturity levels; software engineering practices; software process impediment; software process improvement; Acoustical engineering; Capability maturity model; Impedance; Knowledge management; Project management; Quality management; Roads; Software engineering; Software maintenance; Software quality; Software testing;
fLanguage
English
Journal_Title
Software, IEEE
Publisher
ieee
ISSN
0740-7459
Type
jour
DOI
10.1109/52.536453
Filename
536453
Link To Document