Managing the software process
IEEE Software
Bootstrap: Fine-Tuning Process Assessment
IEEE Software
Software quality and the Capability Maturity Model
Communications of the ACM
Successful software process improvement
Successful software process improvement
Software process improvement: practical guidelines for business susccess
Software process improvement: practical guidelines for business susccess
Participatory Design: Principles and Practices
Participatory Design: Principles and Practices
Design at Work: Cooperative Design of Computer Systems
Design at Work: Cooperative Design of Computer Systems
Software Process Improvement at Hughes Aircraft
IEEE Software
A Critical Look at Software Capability Evaluations
IEEE Software
Software Process Improvement At Raytheon
IEEE Software
How Software Process Improvement Helped Motorola
IEEE Software
Social networks in software process improvement
Journal of Software Maintenance and Evolution: Research and Practice
Software Process Improvement as organizational change: A metaphorical analysis of the literature
Journal of Systems and Software
Troubleshooting large-scale new product development embedded software projects
PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement
A Vertical Approach to Knowledge Management: Codification and Personalization in Software Processes
International Journal of Human Capital and Information Technology Professionals
Hi-index | 0.00 |
This paper reports on action research undertaken to understand and to improve the problems with software processes of a medium-sized Danish company. It is argued that, in order to understand what the specific problems are, we may, on the one hand, rely on normative process models like CMM or Bootstrap. On the other hand, we may also see the specific and unique features of software processes in a company through what we call "problem diagnosis." Problem diagnosis deals with eliciting problems perceived by software professionals and with forming commitment to enable software process improvement to effectively take place. A central purpose of problem diagnosis is to base the SPI project on the software developers' own perceptions of software process problems and suggestions for improvement rather than on the prescriptions and norms of a maturity model.