1997
DOI: 10.1109/2.589907
|View full text |Cite
|
Sign up to set email alerts
|

Results of applying the Personal Software Process

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
23
0
4

Year Published

2002
2002
2011
2011

Publication Types

Select...
6
4

Relationship

0
10

Authors

Journals

citations
Cited by 75 publications
(27 citation statements)
references
References 5 publications
0
23
0
4
Order By: Relevance
“…Results of PSP applications on industrial projects have been positive (Ferguson, Humphrey, Khajenoori, Macke, & Matvya, 1997). Data from three industrial case studies demonstrate that PSP training substantially improves estimating and planning abilities of developers while significantly reducing defects in software products.…”
Section: Software Development Process Innovation: the Personal Softwamentioning
confidence: 97%
“…Results of PSP applications on industrial projects have been positive (Ferguson, Humphrey, Khajenoori, Macke, & Matvya, 1997). Data from three industrial case studies demonstrate that PSP training substantially improves estimating and planning abilities of developers while significantly reducing defects in software products.…”
Section: Software Development Process Innovation: the Personal Softwamentioning
confidence: 97%
“…The need for creativity does not, however, excuse the need for guidelines on how to model (Evans, 1992). Ferguson et al (1997), writing about software development, point out that in 'most professions, competent work requires the disciplined use of established practices. It is not a matter of creativity versus discipline, but one of bringing discipline to the work so creativity can happen.…”
Section: Figure 3 Simulation Model Complexity and Accuracy (Based Onmentioning
confidence: 99%
“…Rows 2 and 3 represent the data on the application that were developed by our team for the person-toperson voice call, and person-to-person video conference respectively. To estimate the development time by a trained programmer, we used the study of Ferguson et al (1997), whose findings reveal approximately 2500 lines of code per month per programmer.…”
Section: Prototype Evaluationmentioning
confidence: 99%