Managing the software process
Software Process Evolution at the SEL
IEEE Software
Software process improvement: practical guidelines for business susccess
Software process improvement: practical guidelines for business susccess
Software engineering: theory and practice
Software engineering: theory and practice
Applied software architecture
Experimentation in software engineering: an introduction
Experimentation in software engineering: an introduction
Software engineering (6th ed.)
Software engineering (6th ed.)
An empirical study on the utility of formal routines to transfer knowledge and experience
Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering
Documenting Software Architectures: Views and Beyond
Documenting Software Architectures: Views and Beyond
Assessing Attitude Towards, Knowledge of, and Ability to Apply, Software Development Process
CSEET '03 Proceedings of the 16th Conference on Software Engineering Education and Training
Software Process Improvement: Blueprints versus Recipes
IEEE Software
IEEE Software
A Study on Agreement Between Participants in an Architecture Assessment
ISESE '03 Proceedings of the 2003 International Symposium on Empirical Software Engineering
De-motivators for software process improvement: an analysis of practitioners' views
Journal of Systems and Software
An Evaluation of k-Nearest Neighbour Imputation Using Likert Data
METRICS '04 Proceedings of the Software Metrics, 10th International Symposium
Benchmarking k-nearest neighbour imputation with homogeneous Likert data
Empirical Software Engineering
Who tested my software? Testing as an organizationally cross-cutting activity
Software Quality Control
| Hi-index | 0.00 |
In response to the increasingly challenging task of developing software, many companies turn to Software Process Improvement (SPI). One of many factors that SPI depends on is user (staff) involvement, which is complicated by the fact that process users may differ in viewpoints and priorities. In this paper, we present a case study in which we performed a pre-SPI examination of process users' viewpoints and priorities with respect to their roles. The study was conducted by the means of a questionnaire sent out to the process users. The analysis reveals differences among roles regarding priorities, in particular for product managers and designers, but not regarding viewpoints. This indicates that further research should investigate in which situations roles are likely to differ and in which they are likely to be similar. Moreover, since we initially expected both viewpoints and priorities to differ, it indicates that it is important to cover these aspects in SPI, and not only rely on expectations.