The rapid pace of digitalisation is not only affecting our everyday lives, but also the world of work. The advantage of digitalization in the industry is seen as the fourth industrial revolution and called “Industry 4.0”. This industrial revolution started at the end of the 20th century and facilitated the intelligent monitoring and decision processes and is still evolving. With the great benefits for companies, it does also bring major restructuring and challenges. The industrial processes develop increasingly agile and complex. To manage such complex structures, new methods were needed. The new demands on project management were speed, flexibility, dynamism, and customer proximity. With rising software demands these projects were very difficult to manage with the hitherto prevailing plan-driven management methods, due to the complexity and uncertainty during these project processes. To still be able to handle such complex and uncertain projects, different agile project management methods were developed. The approaches are classified if they meet specific requirements.
The term agile management is an umbrella term for different approaches that meet specific requirements like the values and principles of the agile manifesto. One of the agile approaches is the scrum method, developed by Ken Schwaber and Jeff Sutherland in the 80s. This method has its name origin in the sport of rugby. Scrum in rugby is a situation, which is formed, when the forwards of both teams are in a tight formation and try to dominate the possession of the ball. To win the ball possession, the forwards of a team must work agile and, in a team, to get their goal. The process of scrum project management is used as a framework, in which the team has to functions self-organized to reach their goal. This framework is characteristic for its iterative process making it suitable for projects in which many unforeseen changes may occur.
The goal of this case study is to explain the scrum method and plan-driven method more in detail and analyse the importance and advantages of the agile management method with the help of an exemplary project and lastly compare the agile method with a plan-driven management method.
Table of Contents
1. Introduction
2. Exemplar project
3. Scrum in a nutshell
3.1. Product owner
3.2. Scrum Team
3.3. Scrum master
4. Agile Manifesto
5. Plan-driven method in a nutshell
6. Conclusion
Research Objectives and Core Themes
This case study aims to analyze the efficacy of agile project management, specifically the Scrum framework, in contrast to traditional plan-driven methodologies within the context of complex software development projects.
- Comparison of Scrum and Waterfall (plan-driven) methodologies
- Handling high-uncertainty tasks in software engineering
- Practical application of the Agile Manifesto values and principles
- Analysis of self-organized teams vs. traditional management structures
- Integration of client feedback loops for iterative product improvement
Excerpt from the Book
1. Introduction
The rapid pace of digitalisation is not only affecting our everyday lives, but also the world of work. The advantage of digitalization in the industry is seen as the fourth industrial revolution and called “Industry 4.0”. This industrial revolution started at the end of the 20th century and facilitated the intelligent monitoring and decision processes and is still evolving [1]. With the great benefits for companies, it does also bring major restructuring and challenges. The industrial processes develop increasingly agile and complex. To manage such complex structures, new methods were needed.
The new demands on project management were speed, flexibility, dynamism, and customer proximity. With rising software demands these projects were very difficult to manage with the hitherto prevailing plan-driven management methods, due to the complexity and uncertainty during these project processes. To still be able to handle such complex and uncertain projects, different agile project management methods were developed. The approaches are classified if they meet specific requirements. The term agile management is an umbrella term for different approaches that meet specific requirements like the values and principles of the agile manifesto [2, 3]. One of the agile approaches is the scrum method, developed by Ken Schwaber and Jeff Sutherland in the 80s. This method has its name origin in the sport of rugby. Scrum in rugby is a situation, which is formed, when the forwards of both teams are in a tight formation and try to dominate the possession of the ball [4]. To win the ball possession, the forwards of a team must work agile and, in a team, to get their goal. The process of scrum project management is used as a framework, in which the team has to functions self-organized to reach their goal. This framework is characteristic for its iterative process making it suitable for projects in which many unforeseen changes may occur.
Summary of Chapters
1. Introduction: Discusses the rise of digitalization and the necessity for agile management methods due to the complexity of modern software projects.
2. Exemplar project: Introduces a fictive job-portal app scenario to illustrate the challenges of high-uncertainty tasks and the limitations of traditional management.
3. Scrum in a nutshell: Outlines the Scrum framework and defines the core roles of Product Owner, Scrum Team, and Scrum Master.
4. Agile Manifesto: Examines the values and principles of the Agile Manifesto through the lens of the job-portal app project.
5. Plan-driven method in a nutshell: Describes the traditional waterfall methodology, emphasizing its linear phase structure and its approach to software development.
6. Conclusion: Summarizes the advantages of iterative processes over rigid systems and suggests a hybrid approach as the most effective solution for software development.
Keywords
Agile Management, Scrum, Waterfall Method, Plan-driven, Software Development, Industry 4.0, Iterative Process, Product Owner, Sprint, Agile Manifesto, Uncertainty, Project Management, Customer Collaboration, Self-organization, System Development
Frequently Asked Questions
What is the primary focus of this work?
The paper examines the differences between agile and plan-driven project management methods in the context of modern, complex software development.
What are the central themes discussed?
The core themes include the management of project uncertainty, the Scrum framework, the values of the Agile Manifesto, and the linear structure of the waterfall method.
What is the main goal of the study?
The objective is to explain both agile and plan-driven methods in detail and to analyze their respective advantages using an exemplary job-portal app project.
Which scientific methodology is applied?
The author utilizes a case study approach, applying theoretical concepts to a fictive software project to visualize practical implications.
What does the main body cover?
It provides an in-depth explanation of Scrum roles and rituals, the principles of the Agile Manifesto, and the distinct phases of the waterfall/plan-driven model.
What are the key terms defining this work?
Key terms include Scrum, Agile, Waterfall, Project Management, Uncertainty, and Software Development.
How does the author view the role of the client in Scrum?
The client is viewed as an active participant who provides feedback after each sprint, which facilitates continuous improvement but may require high client availability.
Why is a hybrid management approach suggested in the conclusion?
A hybrid approach is proposed to combine the predictability of plan-driven schedules with the flexibility and responsiveness of agile methods at the operational level.
- Citation du texte
- Stonia Thorand (Auteur), 2022, Principles of Agility Used in Modern Software Development, Munich, GRIN Verlag, https://www.grin.com/document/1192570
