Abstract
So let us now get to the point: The introduction of Scrum into an enterprise. Before we get to the “how” of the implementation, we should first look at the “why.” The reasons listed here could possibly help you in elaborating the topic with your management. “Stakeholder management” is also briefly discussed in this chapter. Finally you will learn for which products you should consider Scrum—and for which ones you should not.
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
Notes
- 1.
My thanks go to Scrum.org, who helped me here.
- 2.
A “Death March” in this context means a project doomed to failure due to insufficient personnel, a fundamentally flawed schedule, inadequate funding, and/or unrealistic requirements. As a consequence, these projects are usually managed with massive pressure and driven into a wall. Edward Yourdon wrote a book on the topic (Yourdon 2003).
- 3.
You do not believe this? Then you should check out your spreadsheet program. When clicking through the menu bar, try to remember which of these functions you use regularly and which you have pretty much neglected so far.
- 4.
You can learn more about risk management from “Waltzing With Bears” by DeMarco and Lister (2003).
- 5.
For example, this could be the integration of a new, already integration-tested machine or the rollout of standard software after the pilot testing is complete.
- 6.
This list is not conclusive. It is quite possible that there are other processes and methods that work well in certain contexts. However, my personal experience taught me that the approaches listed work very well in the situations mentioned.
- 7.
One place where you can learn more about Kanban is Henrik Kniberg’s book “Kanban and Scrum—making the most of both”. The book is free to download at http://www.infoq.com/minibooks/kanban-scrum-minibook (Kniberg 2010).
References
DeMarco, T., & Lister, T. (2003). Waltzing with bears: Managing risk on software projects. Dorset House: Paperback edition.
Kniberg, H. (2010). Kanban and Scrum – making the most of both. Paperback. Lulu.com
Ries, E. (2011). The lean startup. New York: Crown Business.
Schwaber, K., & Beedle, M. (2002). Agile software development with scrum (Pearson Internationalth ed.). Upper Saddle River: Prentice Hall.
Stacey, R. D. (1996). Strategic management & organisational dynamics: The challenge of complexity (2nd ed.). London: Financial Times Management.
Yourdon, E. (2003). Death March (2nd ed.). Upper Saddle River: Prentice Hall.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2015 Springer International Publishing Switzerland
About this chapter
Cite this chapter
Maximini, D. (2015). Considerations for Scrum Introductions. In: The Scrum Culture. Management for Professionals. Springer, Cham. https://doi.org/10.1007/978-3-319-11827-7_8
Download citation
DOI: https://doi.org/10.1007/978-3-319-11827-7_8
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-11826-0
Online ISBN: 978-3-319-11827-7
eBook Packages: Business and EconomicsBusiness and Management (R0)