0 views collected around this technical thread.
This article traces the three major evolutions of software engineering—from the 1970s waterfall model, through the 1990s rise of agile and iterative methods, to the 2010s DevOps and continuous delivery movement—highlighting how delivery roles have expanded and how organizations can overcome adoption plateaus.
The article shares a chief architect’s experience designing a hybrid “big waterfall + small agile” delivery approach, microservice architecture, BFF layer, and team organization principles such as Conway’s law to address application boundary challenges in a massive state‑owned enterprise project.
The article explains the distinction between defined and high‑uncertainty work, outlines traditional waterfall planning versus adaptive agile approaches, compares their processes, costs, and success rates, and presents data from the Standish Group showing agile projects outperform waterfall ones.
This article explains the three major software development models—Waterfall, Agile, and DevOps—detailing their origins, characteristics, advantages, and challenges, and shows how they evolved to meet the fast‑changing demands of modern internet enterprises.
This article compares the traditional Waterfall development model with the Agile Scrum approach, outlining each method's strengths and weaknesses, describing Scrum roles and workflow, and offering practical insights on when and how to apply either model in software projects.
This article compares the traditional Waterfall development model with Agile methodologies, outlines Scrum roles and workflow, highlights each approach's strengths and weaknesses, and emphasizes the importance of team consensus for effective software project management.
This article explains the distinction between well‑defined and high‑uncertainty project work, compares traditional waterfall planning with modern Agile practices, and presents data showing Agile’s higher success rates while also providing practical guidance for teams transitioning to more exploratory development approaches.
This article compares the traditional Waterfall development model with Agile methodologies, outlines Scrum roles and processes, and discusses how teams can balance documentation‑heavy and people‑centric approaches to improve software project efficiency and adaptability.
This article introduces four major software development models—Waterfall, Iterative (RUP), Spiral, and Agile—detailing their origins, core concepts, advantages, and disadvantages, helping readers understand how each approach structures project phases, manages risk, and adapts to changing requirements.
This article traces the historical shift in software development practices, comparing the linear Waterfall model with Agile, Kanban, Scrum, and Lean approaches, highlighting how each methodology improves flexibility, transparency, and efficiency by borrowing principles from automotive production systems.
The article critically explores whether agile development truly outperforms waterfall, highlighting that each methodology has distinct strengths and limitations depending on project requirements, team stability, and organizational context, and argues for choosing the most suitable approach rather than blindly favoring one over the other.
This article analyzes the rapid construction of Huoshenshan and Leishenshan hospitals, using it as a case study to compare waterfall, spiral, iterative, and Scrum development models, discuss the shift toward agile practices, and outline quality‑built operations principles for complex, time‑critical projects.
The article presents a lively debate at the annual "Zuo Chan Lun Dao" conference where seasoned practitioners contrast the Waterfall and Agile development models, discussing requirements management, quality control, and process management to illustrate the strengths and trade‑offs of each approach.
The article dramatizes a debate between the Waterfall and Agile development approaches, illustrating their differing philosophies on requirements, quality control, and process management, and concludes that each method has unique strengths, urging teams to select the most suitable practice based on project needs.
The article clarifies common misconceptions about waterfall and agile, explaining that both approaches require thoughtful planning, adaptability, and value‑driven delivery rather than merely executing a fixed plan or abandoning planning altogether.
The article examines why traditional waterfall planning remains essential for banking software projects while selectively adopting agile practices, highlighting the differences between consumer‑focused (To C) products and business‑focused (To B) initiatives, the limits of MVP, and a hybrid delivery model that satisfies both speed and contractual certainty.
The article argues that software development is a continuous design activity rather than a repeatable manufacturing process, using car production and cooking analogies to illustrate why traditional waterfall management fails and why developers should be seen as designers, not assembly line workers.