A Constructivist Approach to Teaching Software Processes
ICSE '07 Proceedings of the 29th international conference on Software Engineering
A framework to support the evaluation, adoption and improvement of agile methods in practice
Journal of Systems and Software
Identifying some important success factors in adopting agile software development practices
Journal of Systems and Software
Scope management in agile versus traditional software development methods
NSEC '10 Proceedings of the 2010 National Software Engineering Conference
Early experience with agile methodology in a model-driven approach
Proceedings of the 14th international conference on Model driven engineering languages and systems
ICCSA'06 Proceedings of the 2006 international conference on Computational Science and Its Applications - Volume Part III
| Hi-index | 0.00 |
Agile development methodologies promise highercustomer satisfaction, lower defect rates, fasterdevelopment times and a solution to rapidly changingrequirements. Plan-driven approaches promisepredictability, stability, and high assurance. However,both approaches have shortcomings that, if leftunaddressed, can lead to project failure. The challengeis to balance the two approaches to take advantage oftheir strengths and compensate for their weaknesses. Webelieve this can be accomplished using a risk-basedapproach for structuring projects to incorporate bothagile and disciplined approaches in proportion to aproject's needs.This paper presents six observations drawn from ourefforts to develop such an approach. We follow thoseobservations with some practical advice to organizationsseeking to integrate agile and plan-driven methods intheir development process. The material presented hereis drawn from our book Balancing Agility andDiscipline: A Guide to the Perplexed (Addison Wesley,2003).