Member-only story
Pure Agile Software Development is Not the Solution for Most Software Projects
Why You might need to Design Your Own Hybrid Project Management Method
Table of Contents
· Preface
· Agile Software Development
∘ What is Agile Software Development?
∘ Why is the Focus on Discovery?
∘ Extremistan
· The Importance of long-term Planning
· Phased Scrum — A possible Solution for most Software Projects
∘ Initial Planning Phase
∘ Scrum-Based Phase Execution
· Conclusion
Preface
Nowadays, it seems that projects can only distinguish between two methodologies. Either you work “agile” or you do not. If questions are asked about the process model, it is frequently argued that “agile” or “not agile” is used and therefore things are done the way they are done. In short, it appears that there are only two exclusive types of project management in software development— “agile” (often Scrum) and the contrast “not agile” (often waterfall or V-model). Let’s see why this is not true and why it is more important to understand the methodologies in order to set up project-specific management. At the end, I will outline a proposed solution that should fit most software projects (Phased Scrum).
Agile Software Development
Even before the COVID-19 pandemic, agile software development was a hot topic. Numerous concepts based on agility have emerged. The most famous are extreme programming, Scrum, Scrumban, and (Biz)DevOps.
But, what does agile software development really mean?
What is Agile Software Development?
Agile was popularized by the 2001 Manifesto for Agile Software Development. If we read the manifesto carefully and categorize the content, we can identify the following main points:
- Find out what to solve or serve.
