All information contained in this book has been presented to the best of our knowledge and
belief and has been checked several times. Nevertheless, there is always a residual risk that
either an error has crept in. Neither the author nor the publisher can be held liable for this.
Impressum
PREFERENTIAL NOTES
Professional Scrum Master ™ (PSM ™) and Professional Scrum Product Owner ™ (PSPO ™) and Professional Scrum Developer ™ (PSD ™) are trademarks of Scrum.org.
This book does not claim any rights to the mentioned trademarks, nor can any guarantees be given for the correctness of the book content. The information provided has been compiled to the best of our knowledge and belief, based on the current state of knowledge. For better readability, the ™ references in the book text have been omitted. However, they are always included.
Bibliografische Information der Deutschen Nationalbibliothek:
Die Deutsche Nationalbibliothek verzeichnet diese Publikation in der
Deutschen Nationalbibliografie; detaillierte bibliografische Daten sind im
Internet über www.dnb.de abrufbar.
© 2020 Markus Marfurt
Herstellung und Verlag: BoD – Books on Demand GmbH, Norderstedt, Germany
ISBN: 978-3-7431-2907-8
In most cases, project management is based on the waterfall model (or a comparable approach). This means that before the start of the project or at the beginning of the project, a plan is drawn up for the entire implementation as complete as possible. All conceivable obstacles are taken into account and possible risks are minimized as far as possible. As soon as the project plan is completely prepared, the implementation can begin. In this context, the goal is that the project result predominantly corresponds to what was specified in the underlying planning and the associated requirements documents. The customer (whether internal or external) receives the developed product at the end.
It is an everyday experience that this development approach is associated with considerable risks, especially in the case of projects of longer duration or those with a higher degree of complexity. On the one hand, there is always a certain basic risk as to whether what was originally specified corresponds to what is really needed. Furthermore, there is a risk that the team that has to implement a requirement may understand it in a completely different way than what the client intended. Other challenges include the fact that requirements can change during the course of the project (because the customer needs something else or because certain conditions have changed).
The major weakness of such a development approach is that the customer's involvement during the development period is very low. His knowledge and expertise as a future user are hardly integrated.
Scrum has a completely different approach here. The framework, developed by Ken Schwaber and Jeff Sutherland and first presented at the OOPSLA conference in 1995, is based on constant interaction with the customer and his feedback. Since it is based on the exchange and gain of experience through this feedback, it is also called empirical1.
The advantages of such an approach are risk and cost reduction.
1 Empirical = based on experience.
Agile is based on the Agile Manifesto, which can be found at (www.agilemanifest.org).
Manifesto for Agile Software Development
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on