Waterfall 2.0

 

When looking around the internet, I found that there was waterfall 2.0 version of the waterfall software development methodology that we learned at start of class. After I saw the article, I found out that even the most established practices can transform to meet the demands of new era. Therefore, I chose this article as it provides basic summarization of waterfall 2.0 and the difference between traditional waterfall model. As we talked about why waterfall method was being replaced by agile and scrum, I thought there will be some people who will try to improve and use the old working method so using this article showed me how waterfall transformed to adopt need of current workflow. Therefore, I decided to look into it as a background for finding out about the improved version as it revives the dying method into a new form.

             This article uses baking as an example to illustrate the principles of waterfall 2.0. It describes the steps on planning, mixing, baking, decorating and enjoying trying to explain how they work. For example, for planning, allowing adjustments to the cake showing adaptability, mixing; showing collaboration with others, baking; showing continuous monitoring, making sure the cake does not burn or become too dry etc. This shows how the 2.0 fixed many problems of waterfall. In the end, these changes try to solve the problem of traditional waterfall model that was not able to adopt to constantly changing environment and unexpected changes to the requirements and need of the program.

             Reading this article reminded me why the waterfall model is being replaced by agile or scrum, not able to meet the industry’s demand in changing environment. Using cake to explain the new waterfall made the concept more understandable and memorable. The example clearly showed what the 2.0 version tries to do in order to survive. The concept of Waterfall 2.0 was particularly impactful because it demonstrated that no methodology is entirely outdated. If they have the right adjustments, even traditional approaches can remain relevant in the changing world. In the future, I thought I might use waterfall methodology in a short and brief project that what I had to do was very clear. However, finding out waterfall 2.0 I can try to use it for future project. For example, it could be useful in projects with fixed deadlines and regulatory requirements, where a hybrid approach ensures adaptability and flexibility.

Link https://de.celoxis.com/article/waterfall-is-dead-long-live-waterfall-2-0

 

Comments

Post a Comment

Popular posts from this blog

Is Agile going to fail?

  This article by Jeff Gothelf asks the question “Is Agile finally over?” after 20+ years of implementation to tech field. He argues that even though Agile’s widespread adaptation hasn’t got the result that Agile was intended for. Many companies claimed to be “Agile” as they copy each other, but the implementation of it was shallow or almost non-existent to make changes according to it. Therefore, he says that agile does not seems working as companies try to make employee follow set of rules instead of working in following the basic principles of Agile. He concluded that organizations need to focus on true organizational agility rather than rigid framework adoption. This article caught my attention while searching through the internet as it criticizes Agile’s current status in the business world as ideal of agile does not really fit in reality in organization experience. The vague promises and core ideas are often overlooked to the ‘wants’ of either customer or the organization...
Read more

Introductory Blog Post

 Hello my Name is Sung Jin Kim doing my major of Computer Science for Bachelor's degree. In this blog, i will be talking about Software Process management and how it is related to real life.  I am hoping to meet everyone and those in the comment to share any of their experience.
Read more

Clean code and reality.

  The article examines the question, “is clean code by Robert Martin still matters?” From author’s 16-year coding experience, he writes about reality in writing clean code and its criticism. He acknowledges that t in the end meeting the deadline with functional and bug free code is more important then elegant code following the principle of clean code. However, he argues in the end as a developer, trying to integrate small aspects of clean code into your code base is going to make your skill improve as an engineer in the long run even if many people will not care about it. I selected this article as it addresses some uncertainty that I had with clean code. All the code I have written feels like I got pressure to deliver functional code as quickly as possible and now I’m supposed to write elegant, maintainable code so I wanted to see the real live example from experience if clean code was that necessary. The author’s real-world experience and practical approach toward the subjec...
Read more