Abstract
Very little has been written to date on how to prioritize and sequence the development of new features and capabilities on an agile software development project. Agile product managers have been advised to prioritize based on “business value.” While this seems an appropriate goal, it is vague and provides little specific guidance. Our approach to optimizing “business value” uses tactics to minimize costs and maximize benefits through strategic learning. In order to provide specific and actionable advice to agile product managers, we present two guidelines. These guidelines are meant to provide a set of considerations and a process by which an agile product manager can achieve the goal of optimizing “business value” while recognizing that different product managers will vary in their notions of what “business value” is.
This is a preview of subscription content, log in via an institution to check access.
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
Schwaber, K., Beedle, M.: Agile Software Development with Scrum. Prentice-Hall, Upper Saddle River (2001)
Beck, K.: Extreme Programming Explained: Embrace change. Addison-Wesley, Upper Saddle River (1999)
Palmer, S.R., Felsing, J.M.: A Practical Guide to Feature-Driven Development. Addison-Wesley, Upper Saddle River (2002)
Stapleton, J.: DSDM: Business-Focused Development, 2nd edn. Pearson Education, Upper Saddle River (2003)
Cohn, M.: User Stories Applied for Agile Software Development. Addison-Wesley, Upper Saddle River (2004)
Poppendieck, T.: The Agile Customer’s Toolkit at, www.poppendieck.com
Andrea, J.: An Agile Request For Proposal (RFP) Process. In: Proceedings of the Agile Development Conference, Salt Lake City, UT, pp. 152–161 (2003)
Augustine, S.: Great COTS! Implementing Packaged Software With Agility. In: Presentation at Agile Development Conference, Sydney, Australia (2004)
Harris, R.S., Cohn, M.: The Role of Learning and Expected Cost of Change in Prioritizing Features on Agile Projects, Ms (2006), Available at: www.moutaingoatsoftware.com
Hayak, F.A.: The Use of Knowledge in Society. American Economic Review XXXV(4), 519–530 (1945)
Jensen, M.C., Meckling, W.H., Baker, G.P., Wruck, K.H.: Coordination, Control, and the Management of Organizations: Course Notes, pp. 98–098. Harvard Business School Working Paper (1999)
Jensen, M.C., Meckling, W.H.: Specific and General Knowledge, and Organizational Structure. In Werin, L., Wijkander, H. (eds.) Contract Economics. Blackwell, Oxford (1992); Also published in Journal of Applied Corporate Finance (Fall 1995); Jensen, M.C.: Foundations of Organizational Strategy. Harvard University Press, Boston (1998)
Schuler, D., Namioka, A. (eds.): Participatory Design: Principles and practice. Erlbaum, Hillsdale (1993)
Constantine, L.L., Lockwood, L.A.D.: Software for Use. Addison-Wesley, Reading (1999)
Karlsson, J., Ryan, K.: A Cost-Value Approach for Prioritizing Requirements. IEEE Software 14(5), 67–74 (1997)
Saaty, T.L.: The Analytic Hierarchy Process. McGraw-Hill, New York (1980)
Karlsson, J., Wohlin, C., Regnell, B.: An Evaluation of Methods for Prioritizing Software Requirements. Journal of Information and Software Technology 39(14–15), 939–947 (1998)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2006 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Harris, R.S., Cohn, M. (2006). Incorporating Learning and Expected Cost of Change in Prioritizing Features on Agile Projects. In: Abrahamsson, P., Marchesi, M., Succi, G. (eds) Extreme Programming and Agile Processes in Software Engineering. XP 2006. Lecture Notes in Computer Science, vol 4044. Springer, Berlin, Heidelberg. https://doi.org/10.1007/11774129_19
Download citation
DOI: https://doi.org/10.1007/11774129_19
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-35094-1
Online ISBN: 978-3-540-35095-8
eBook Packages: Computer ScienceComputer Science (R0)