Abstract
In these days of rapid change, many organizations find that their current balance between using agile and disciplined methods is not what it should be. (We realize that “disciplined” is not the opposite of “agile,” but it is our working label here for methods relying more on explicit documented knowledge than on tacit interpersonal knowledge). In a forthcoming book [1], we have analyzed many organizations’ experiences with agile and disciplined methods, and have elaborated our previous characterization [2] of the “home grounds” in which agile and disciplined methods have been most successful. This analysis has enabled us to determine five critical decision factors that organizations and projects can use to determine whether they are in either the agile or disciplined home grounds, or somewhere in between. These five decision factors are size, criticality, personnel, dynamism, and culture. In this paper, we set the context by characterizing the agile and disciplined home grounds. We then define the five decision factors and their rating scales; provide a stepwise approach for assessing your organization’s or project’s location in the decision space and developing a strategy for rebalancing its agility and discipline; and illustrate its use with a representative organizational example.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Boehm, B., Turner, R.: Balancing Agility and Discipline: A Guide for the Perplexed. Addison Wesley, Reading (2003) (to appear)
Boehm, B.: Get Ready for Agile Methods, With Care, IEEE Computer, pp. 64–69 (January 2002)
Cockburn, A.: Agile Software Development. Addison Wesley, Reading (2002)
Highsmith, J.: Agile Software Development Ecosystems. Addison-Wesley, Reading (2002)
Elssamadisy, A., Schalliol, G.: Recognizing and Responding to ‘Bad Smells’ in Extreme Programming. In: Proceedings, ICSE 2002, pp. 617–622 (2002)
Elssamadisy, A.: XP on a large Project: A Developer’s View. In: Marchesi, et al. (eds.) Extreme Programming Perspectives, pp. 387–397. Addison Wesley, Reading (2003)
Schalliol, G.: Challenges for Analysts on a Large XP Project. In: Marchesi, et al. (eds.) Extreme Programming Perspectives, pp. 375–385. Addison Wesley, Reading (2003)
Curtis, B., Hefley, W., Miller, S.: The People Capability Maturity Model. Addison Wesley, Reading (2002)
Boehm, B.: Value-Based Software Engineering. ACM Software Engineering Notes (March 2003)
Boehm, B., Huang, L.: Value-Based Software Engineering: A Case Study, IEEE Computer, pp. 21–29 (March 2003)
Kaplan, R., Norton, D.: The Balanced Scorecard: Translating Strategy into Action. Harvard Business School Press, Boston (1996)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2003 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Boehm, B., Turner, R. (2003). Rebalancing Your Organization’s Agility and Discipline. In: Maurer, F., Wells, D. (eds) Extreme Programming and Agile Methods - XP/Agile Universe 2003. XP/Agile Universe 2003. Lecture Notes in Computer Science, vol 2753. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-45122-8_1
Download citation
DOI: https://doi.org/10.1007/978-3-540-45122-8_1
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-40662-4
Online ISBN: 978-3-540-45122-8
eBook Packages: Springer Book Archive