ISO 9000 versus CMM: standardization and certification of IS development
Information and Management
Power, politics, and MIS implementation
Communications of the ACM
To Improve Your Process: Keep It Simple
IEEE Software
Does Organizational Maturity Improve Quality?
IEEE Software
Telcordia Technologies: The Journey to High Maturity
IEEE Software
Looking for the human factors in software quality management
SEEP '96 Proceedings of the 1996 International Conference on Software Engineering: Education and Practice (SE:EP '96)
The Process Workshop: A Tool to Define Electronic Process Guides in Small Software Companies
ASWEC '04 Proceedings of the 2004 Australian Software Engineering Conference
METRICS '04 Proceedings of the Software Metrics, 10th International Symposium
The Impact of Process Workshop Involvement on the Use of an Electronic Process Guide: A Case Study
EUROMICRO '05 Proceedings of the 31st EUROMICRO Conference on Software Engineering and Advanced Applications
A case study: coordination practices in global software development
PROFES'05 Proceedings of the 6th international conference on Product Focused Software Process Improvement
A framework for overcoming supplier related threats in global projects
EuroSPI'06 Proceedings of the 13th European conference on Software Process Improvement
Hi-index | 0.00 |
In order to survive in a strong competition software houses need to design high-quality software. To achieve this some companies try to certify their software development processes in accordance with well-known industrial standards. Through a case study we investigated what characterizes the use of a quality system among developers and project managers in a large software company that has successfully achieved an ISO 9001:2000 certification. We found that certification not always indicates that the company successfully uses the practices in accordance with quality standards. This caused serious problems, such as projects that follow outdated practices, project managers faking quality documentation before audits, resources wasted by producing documents no one needs, problems created for new employees since they cannot find descriptions of the processes people are working in accordance with, and an expensive system no one uses.