Managing the software process
The state of software engineering practice
ICSE '89 Proceedings of the 11th international conference on Software engineering
The capability maturity model: guidelines for improving the software process
The capability maturity model: guidelines for improving the software process
A systematic survey of CMM experience and results
Proceedings of the 18th international conference on Software engineering
Software process maturity: is level five enough?
Proceedings of the 21st international conference on Software engineering
Validating the ISO/IEC 15504 Measure of Software Requirements Analysis Process Capability
IEEE Transactions on Software Engineering
Modeling Software Measurement Data
IEEE Transactions on Software Engineering
Software Engineering Economics
Software Engineering Economics
Requirements Engineering: A Good Practice Guide
Requirements Engineering: A Good Practice Guide
An Instrument for Measuring the Key Factors of Successin Software Process Improvement
Empirical Software Engineering
How Software Process Improvement Helped Motorola
IEEE Software
Telcordia Technologies: The Journey to High Maturity
IEEE Software
A quantitative and qualitative analysis of factors affecting software processes
Journal of Systems and Software
De-motivators for software process improvement: an analysis of practitioners' views
Journal of Systems and Software
Studying Software Engineers: Data Collection Techniques for Software Field Studies
Empirical Software Engineering
Using an expert panel to validate a requirements process improvement model
Journal of Systems and Software
Defining a Requirements Process Improvement Model
Software Quality Control
Establishing and maintaining trust in software outsourcing relationships: An empirical investigation
Journal of Systems and Software
A measurement framework for assessing the maturity of requirements engineering process
Software Quality Control
A practitioner's guide to light weight software process assessment and improvement planning
Journal of Systems and Software
A Model for Requirements Change Management: Implementation of CMMI Level 2 Specific Practice
PROFES '08 Proceedings of the 9th international conference on Product-Focused Software Process Improvement
An Empirical Study Identifying High Perceived Value Practices of CMMI Level 2
PROFES '08 Proceedings of the 9th international conference on Product-Focused Software Process Improvement
Issues in the implementation of software process improvement project in Malaysia
WSEAS Transactions on Information Science and Applications
Identifying high perceived value practices of CMMI level 2: An empirical study
Information and Software Technology
Empirical evaluation of selected best practices in implementation of software process improvement
Information and Software Technology
Empirical validation of the Classic Change Curve on a software technology change project
Information and Software Technology
QoSA'07 Proceedings of the Quality of software architectures 3rd international conference on Software architectures, components, and applications
Software Process Improvement barriers: A cross-cultural comparison
Information and Software Technology
Assessing and improving the front end activities of software development
International Journal of Business Information Systems
A study on the distribution and cost prediction of requirements changes in the software life-cycle
SPW'05 Proceedings of the 2005 international conference on Unifying the Software Process Spectrum
Analysis of bug fixing processes using program slicing metrics
PROFES'10 Proceedings of the 11th international conference on Product-Focused Software Process Improvement
Critical success factors for offshore software development outsourcing vendors: an empirical study
PROFES'10 Proceedings of the 11th international conference on Product-Focused Software Process Improvement
Field study on requirements engineering artefacts and patterns
EASE'10 Proceedings of the 14th international conference on Evaluation and Assessment in Software Engineering
Trust in software outsourcing relationships: an analysis of vietnamese practitioners' views
EASE'06 Proceedings of the 10th international conference on Evaluation and Assessment in Software Engineering
Motivators of software process improvement: an analysis of vietnamese practitioners' views
EASE'07 Proceedings of the 11th international conference on Evaluation and Assessment in Software Engineering
De-motivators of software process improvement: an analysis of vietnamese practitioners' views
PROFES'07 Proceedings of the 8th international conference on Product-Focused Software Process Improvement
Proceedings of the 17th International Conference on Evaluation and Assessment in Software Engineering
Forecasting software development project characteristics using meta-modeling
Proceedings of the 9th Central & Eastern European Software Engineering Conference in Russia
Critical success factors taxonomy for software process deployment
Software Quality Control
Hi-index | 0.00 |
In this paper we discuss our study of the problems 12 software companies experienced in software development. In total we present qualitative data collected from 45 focus groups that involved over 200 software staff. We look at how different practitioner groups respond to software process improvement problems. We show our classification and analysis of this data using correspondence analysis. Correspondence analysis is a graphical data representation method new to software development research. The aim of the work we present is to develop a more holistic understanding of the problems practitioners are experiencing in their attempts to improve their software processes. Our main finding is that there is an association between a company’s capability maturity and patterns of reported problems. Organizational problems are more associated with high maturity companies than with low maturity companies. Low maturity companies are closely linked to problems relating directly to projects such as documentation, timescales, tools and technology. Our findings also confirm differences in practitioner group problems. Senior managers cite problems with goals, culture and politics. Project managers are concerned with timescales, change management, budgets and estimates. Developers are experiencing problems with requirements, testing, documentation, communication, tools and technology. These associations are displayed graphically through correspondence analysis maps.