Using Risk to Balance Agile and Plan-Driven Methods
By Barry W. Boehm, R. Turner. Computer, 2003
458 citations recorded by the source corpus.
Subfields: Information Systems, Software
View Paper: https://www.semanticscholar.org/paper/794bb1b88310836efc76b3350e09360627deaa53
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Information Systems
- Dac-Buu Cao
- Outi Salo
- Jukka Haikara
- Pekka Abrahamsson
- Jari Still
- Tsun Chow
- Minna Pikkarainen
- Paul L. Bannerman
In Software
Citations in the corpus
- The impact of agile practices on communication in software development (2008, methodology): “Furthermore, it has been claimed that the use of agile software development methods can increase the chasm among the actors in software development organizations and even lead to project failure (Boehm and Turner 2003).”
- A survey study of critical success factors in agile software projects (2008, background): “In the context of the present study, the CSF’s can be defined as the factors that must be present for the Agile project to be successful.”
- Risk and risk management in software projects: A reassessment (2008, methodology): “For example, planned functionality might be ‘de-scoped’ to remove a highly uncertain feature to a separate phase or project in which more agile development methods might be applied to determine the requirement (Boehm and Turner, 2003).”