A study of enabling factors for rapid fielding combined practices to balance speed and stability

Proceedings - International Conference on Software Engineering

Volumn , Issue , 2013, Pages 982-991

  Bellomo, Stephany ^a   Nord, Robert L ^a   Ozkaya, Ipek ^a  

^a CARNEGIE MELLON UNIVERSITY   (United States)

Author keywords

agile software development; architecture; rapid fielding; software development practices; speed; stability

Indexed keywords

AGILE SOFTWARE DEVELOPMENT; FLEXIBLE PRODUCT ARCHITECTURE; INCREMENTAL DEVELOPMENT; INITIAL VELOCITIES; PRODUCT STABILITY; RAPID FIELDING; SOFTWARE DEVELOPMENT PRACTICES; STABILITY PROBLEM;

ARCHITECTURE; CONVERGENCE OF NUMERICAL METHODS; SOFTWARE DESIGN; SPEED;

STABILITY;

EID: 84886395834     PISSN: 02705257     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ICSE.2013.6606648     Document Type: Conference Paper

References (18)

1. M. Hotle, D. Norton, and N. Wilson, "The end of the waterfall as we know it," Gartner Research, August 2012.
2. Director of Defense Research and Engineering, "Rapicapability fielding toolbox study," Final Report, March 2010. http://www. cogility. com/Documents/Rapid-Capability-Fielding-Public-Release. pdf
3. M. Denne and J. Cleland-Huang, Software by Numbers. Upper Saddle River, NJ: Prentice Hall, 2003.
4. F. Bachmann, R. L. Nord, and I. Ozkaya, "Architectural Tactics to support rapid and agile stability. " CrossTalk: The Journal of Defense Software Engineering, Special Issue on Rapid and Agile Stability, May/June 2012.
5. A. Martini, L. Pareto, and J. Bosch, "Enablers and inhibitors for speed with reuse," Proceedings of the 16th Software Product Line Conference, ACM, New York, v. 1, pp. 116-125, September 2012.
6. L. Bass, P. Clements, R. Kazman, Software Architecture in Practice, 3rd ed. Boston, MA: Addison-Wesley, 2012
7. T. Grant, "Navigate the Future of Agile and Lean. " Forrester Research, January 2012.
8. B. Dick, "Grounded theory: a thumbnail sketch," http://www. uq. net. au/action-research/arp/grounded. html (2005).
9. G. Barney, "A look at grounded theory: 1984-1994," in Grounded Theory 1984-1994, ed., vol. I, Glaser, Barney G., Mill Valley, CA: Sociology Press, 1995, pp. 3-17.
10. J. Corbin and A. Strauss, Basics of Qualitative Research-Techniques and Procedures for Developing Grounded Theory, 3rd ed. Thousand Oaks, CA: Sage Publications, 2008.
11. S. Adolf, W. Hall, and P. Kruchten, "A methodological leg to stand on: using grounded theory to study the experience of software development," Vancouver, BC: University of British Columbia, January 2011.
12. D. Leffingwell, Scaling Software Agility. Upper Saddle River, NJ: Addison-Wesley, 2007.
13. B. Glaser, The Grounded Theory Perspective: Conceptualization Contrasted with Description. Mill Valley, CA: Sociology Press, 2001.
14. K. Schwaber and J. Sutherland, "Scrum guidebook," Scrum. org and Scrum Inc., 2011.
15. Keith H. Bennett and T. Rajlich, "Software maintenance and evolution: a roadmap," in Proceedings of the Conference on The Future of Software Engineering (ICSE 2000). New York: ACM, 2000, pp. 73-87.
16. P. Kruchten, R. L. Nord, and I. Ozkaya, "Technical debt: from metaphor to theory and practice," IEEE Software, 2012, pp. 18-21.
17. K. Schwaber, (blog) "Telling it like it is," April 2012. http://kenschwaber. wordpress. com/2012/04/05/scrum-but replaced-by-scrum-and
18. L. Williams, G. Brown, A. Melzer, N. Naggappan, "Scrum + Engineering Practices: Experiences of Three Microsoft Teams", ICSE 2013.