Improving software quality: an insider's guide to TQM
Improving software quality: an insider's guide to TQM
Software quality: a framework for success in software development and support
Software quality: a framework for success in software development and support
How ISO 9001 Fits Into the Software World
IEEE Software
The capability maturity model: guidelines for improving the software process
The capability maturity model: guidelines for improving the software process
The role of software development methodologies: past, present, and future
Proceedings of the 18th international conference on Software engineering
The quality approach: is it delivering?
Communications of the ACM
Software quality and the Capability Maturity Model
Communications of the ACM
Successful software process improvement
Successful software process improvement
Microsoft Secrets: How the World's Most Powerful Software Company Creates Technology, Shapes Markets, and Manages People
Going soft on quality?: Process management in the Scottish software industry
Software Quality Control
A Critical Look at Software Capability Evaluations
IEEE Software
IEEE Software
Level 6: Why We Can't Get There from Here
IEEE Software
Optimizing software process control
ACM SIGSOFT Software Engineering Notes
Software Process Improvement Problems in Twelve Software Companies: An Empirical Analysis
Empirical Software Engineering
Communication: the neglected technical skill?
Proceedings of the 2007 ACM SIGMIS CPR conference on Computer personnel research: The global information technology workforce
Concurrent Engineering and the Dynaxity Approach. How to Benefit from Multidisciplinarity
Proceedings of the 2006 conference on Leading the Web in Concurrent Engineering: Next Generation Concurrent Engineering
How to steer an embedded software project: tactics for selecting the software process model
Information and Software Technology
Hi-index | 0.00 |
There is a widely accepted paradigm of successful software development, called process oriented software quality management (PSQM). The proponents of PSQM claim that it has a significant impact on some essential parameters of a software producer's competitiveness. However, case studies of some well known software producers reveal a rather different management style. Since the management style is a means to influence the essential parameters of a company's competitiveness, which are influenced by the competitive conditions, two questions arise. 1. Do the investigated software producers employ a different management style by accident or is their management style an appropriate answer to their specific competitive conditions? 2. If their management style is an appropriate answer to their competitive conditions, what is specific about these conditions and about the appropriate management style? It is argued, that their management style is a form of concurrent engineering, which rather conforms the needs of a software producer in a turbulent environment, while PSQM on the other hand rather conforms the needs of a software producer in a placid environment. This means, there is no universal process management and environmental dynamics is a contingency factor to be considered in the configuration of process management.