?
Crisis Management for Software Development and Knowledge Transfer
Crisis is a burning issue; this is not a phenomenon, which can be conquered forever. Current approach to crisis is an optimized collaboration, which allows for manageable, measurable and predictable software development. Crisis is a new reality to live and work with. The current software development crisis dates back to the 1960s. The root cause of crisis is misbalance between resources and options. Understanding the nature of crisis helps to understand the reasons for the future crises.
This book is a navigator in lifecycle models, methodologies, principles and practices for predictable and efficient software development in crisis, i.e. under rapid requirement changes, resource deficit and other uncertainties. Therefore, the starting chapters suggest the major approaches to software development and their applicability in crisis. Further narration is case-based; it involves large-scale software implementations in different industries and knowledge transfer processes in IT education. The book suggests a set of principles that potentially marry the client’s and the developer’s views of the future software product in order to avoid or to mitigate the crisis.
The book will be helpful for students, postdocs, theorists and practitioners in software development. It suggests approved principles and practices of crisis management for software development.