Abstract
Agile software development has been established over the last 15 years as a popular development approach. In a time when speed of change is of utmost importance, agile approaches are often the most appropriate roads to success. They do not only change the way development is performed, but they also impact other parties involved in development projects, in particular the software product manager. Software companies are faced with the question how software product management and agile development can work together in an optimal way. Who is responsible for requirements? Is the software product manager automatically the designated “product owner” (Scrum)? Or is “product owner” a new and separate role? Does he/she replace the software product manager?
The Software Product Management Framework which has been developed by the International Software Product Management Association (ISPMA e.V., www.ispma.org) provides orientation. It can be used as a helpful tool to make the change process towards agile development successful.
Special thanks to Gerald Heller for inspiring discussions in the preparation of our joint invited talk on “Software Product Management and Agility” at the International Workshop on Software Product Management (IWSPM) 2012 in Essen, Germany.
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
References
Beck, K. (1999). eXtreme programming explained – Embrace change. Upper Saddle River: Addison-Wesley.
Beck, K. (2004). eXtreme programming explained – Embrace change (2nd ed.). Upper Saddle River: Addison-Wesley.
Beck, K., et al. (2001). Manifesto for agile software development. http://agilemanifesto.org/
Cockburn, A. (2004). Crystal clear. Upper Saddle River: Addison-Wesley.
Davis, M. (2011). Will software engineering ever be engineering? CACM, 54(11), 32–34.
de Waard, D., van Solingen, R., & Sutherland, J. (2011). Scrum in sales: How to improve account management and sales processes. Agile conference 2011, Salt Lake City.
Fowler, M. (2005). The new methodology. http://martinfowler.com/articles/newMethodology.html
Fricker, S. A. (2012). Software product management, in this book.
ISPMA. (2012a). Software product management reference framework V.1.1. www.ispma.org
ISPMA. (2012b). Software product management – Foundation level syllabus V.1.1. www.ispma.org
Kittlaus, H.-B. (2003). Software Engineering und Software Fabrik – vom Nutzen und Schaden der Metapher in der Informatik. In: Informatik-Spektrum 26: pp. 8–12 and 291–292.
Kittlaus, H.-B., & Clough, P. C. (2009). Software product management and pricing – Key success factors for all software organizations. Heidelberg: Springer.
Leffingwell, D. (2011). Agile software requirements. Upper Saddle River: Addison-Wesley.
Pichler, R. (2010). Agile product management with scrum. Upper Saddle River: Addison-Wesley.
Schwaber, K. (2004). Agile project management with scrum. Redmond: Microsoft Press.
Schwaber, K. (2007). The enterprise and scrum. Redmond: Microsoft Press.
Schwaber, K., & Beedle, M. (2001). Agile software development with scrum. Upper Saddle River: Prentice Hall.
Schwaber, K., & Sutherland, J. (2011). The scrum guide. http://www.scrum.org/storage/scrumguides/Scrum_Guide.pdf
Sutherland, A., Sutherland, J., & Hegarty, C. (2009). Scrum in church: Saving the world one team at a time. Agile conference 2009, Chicago.
Theuns, M., Vlaanderen, K., & Brinkkemper, S. (2012). Exploring the relationship between scrum and release planning activities, in this book.
VersionOne. (2011). State of agile survey 2011. http://www.versionone.com/state_of_agile_development_survey/11/
Vlaanderen, K., Jansen, S., Brinkkemper, S., & Jaspers, E. (2011). The agile requirements refinery: Applying SCRUM principles to software product management. Information and Software Technology, 53(2011), 58–70.
Vlaanderen, K., van Steen, P., Brinkkemper, S., & van de Weerd, I. (2012). Growing into agility: Process implementation paths for SCRUM from an SPM perspective. Proceedings of the 13th International Conference on Product-Focused Software Process Improvement, Heidelberg/New York, NY: Springer.
West, D., & Grant, T. (2010). Agile development: Mainstream adoption has changed agility. Cambridge, MA: Forrester Research.
White, J., & Simons, B. (2002). ACM’s position on the licencing of software engineers. CACM, 45(11), 91.
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2012 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Kittlaus, HB. (2012). Software Product Management and Agile Software Development: Conflicts and Solutions. In: Maedche, A., Botzenhardt, A., Neer, L. (eds) Software for People. Management for Professionals. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-31371-4_5
Download citation
DOI: https://doi.org/10.1007/978-3-642-31371-4_5
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-31370-7
Online ISBN: 978-3-642-31371-4
eBook Packages: Business and EconomicsBusiness and Management (R0)