4 citations found. Retrieving documents...
Humphrey W. Introduction to software process improvement. Technical Report CMU/SEI-94-TR-007,Software Engineering Institute, Carnegie Mellon University, Pittsburgh PA, August 1992. (Revised version, August 1993.)

 Home/Search   Document Details and Download   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Development of Management Commitment to Software Process.. - Abrahamsson, Jokela (2000)   (Correct)

.... market, under tight time and cost constraints (Cugola and Ghezzi, 1998) As an answer to these business and market needs, organizations have started to undertake software process improvement (SPI) initiatives aimed at increasing the maturity and quality of their software processes (Humphrey, 1989; Humphrey, 1992; Zahran, 1998; Grady, 1997) Investment in process improvement has had significant business benefits such as improving the product quality, reducing time to market, resulted in better productivity (Zahran, 1998) increased organizational flexibility and customer satisfaction (Florac et al. ....

.... (Zahran, 1998) increased organizational flexibility and customer satisfaction (Florac et al. 1997) Literature is rife with statements arguing that that in order for any type of change initiative to be successful, one needs to establish a solid top management commitment (Humphrey, 1989; Humphrey, 1992; Grady, 1997; Stelzer and Mellis, 1998; Wohlwend and S. 1994; Zahran, 1998; Diaz and Sligo, 1997) Humphrey (1989) argues that all major changes to the software process must start at the top and ultimately everyone must be involved in the change process. Wiegers (1998) argues that the lack of ....

Humphrey, W. S. (1992) Introduction to software process improvement, Carnegie Mellon University Software Engineering Institute, Pittsburgh, Pa.


Borland Software Craftsmanship: A New Look at Process.. - James Coplien Software   (Correct)

....from our memories of the ineffectiveness of our meetings, not from their frequency. At the First International Workshop on Software Process, I polled several process luminaries with the following question: Suppose I am among the most mature software organizations in the world (a CMM Level 5) [9] How much of my time do I spend in meetings Responses from Vic Basilli, Watts Humphrey, and Bary Boehm ranged from 30 to 50 . Project communication, a shared vision, and meetings are important and productive if meetings are properly conducted. 2. Development takes place on two levels: ....

Humphrey, W. "Introduction to Software Process Improvement." Pittsburgh, Pa: Carnegie Mellon University, Software Engineering Institute, 1992.


Empirical Investigation on the Innovation Diffusion in a.. - Tortorella, Visaggio   (Correct)

....developers define the processes they will adopt. 1. Introduction In order to be able to improve the software products of an organization, it is necessary to improve its software development processes. To continuously improve a software process, it is necessary to introduce frequently innovations [11, 13, 16, 17, 18]. This can be obtained if the developers of the organization use a process that is definite, repeatable, manageable, and optimizable [12, 14] in a word, improvable. This can be pursued if the organization adopts one or more predefined software process models among which its developers, ....

W.S. Humphrey, Introduction to Software Process Improvement, Technical Report CMU/SEI-92-TR-7, ESC-TR-92-007, June 1992, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pennsylvania;


Latitudinal and Longitudinal Process Diversity - Siebel, Cook, Satpathy.. (2003)   (Correct)

No context found.

Humphrey W. Introduction to software process improvement. Technical Report CMU/SEI-94-TR-007,Software Engineering Institute, Carnegie Mellon University, Pittsburgh PA, August 1992. (Revised version, August 1993.)

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC