Operations 17 min read

DevOps Case Study: Rapid Construction of Huoshenshan and Leishenshan Hospitals

This article analyzes the ten‑day, large‑scale construction of Huoshenshan and Leishenshan hospitals from a DevOps perspective, detailing the "small team‑big backend" organization, parallel value streams, modular building techniques, cloud‑native analogies, waterfall versus agile models, quality‑in‑built practices, and the operational challenges faced by the medical teams.

DevOps
DevOps
DevOps
DevOps Case Study: Rapid Construction of Huoshenshan and Leishenshan Hospitals

The DevOps case study, originally part of the fourth issue of the DevOps Deep‑Dive series, examines how the Chinese government and multiple industry partners built the Huoshenshan and Leishenshan emergency hospitals in just ten days, highlighting the lessons that software teams can draw from this effort.

1. "Small team‑big backend" organization – The project used a flat, network‑style structure where a strong governmental core provided massive resource backing (the "big backend") while dozens of specialized construction, telecom, IT, and logistics teams acted as autonomous front‑line units. Analogies were made to modern military units and Alibaba’s "small front‑end + large middle‑platform" model.

2. Value‑stream mapping – A day‑by‑day timeline (Day 1 to Day 10) shows parallel and serial activities such as design, power grid installation, 5G base‑station deployment, modular container assembly, and medical‑system integration, illustrating how critical path reduction and concurrent work accelerated delivery.

3. Site selection and modular construction – Three architectural options (stadium conversion, hotel conversion, new‑site construction) were evaluated, with the new‑site modular approach chosen. Prefabricated “box‑type” modules were produced off‑site and assembled on‑site, mirroring software containerization.

4. Cloud‑native analogy – The modular, decoupled construction mirrors micro‑service architecture: containers package standardized units, while the overall process aligns with IaaS, PaaS, SaaS, CaaS, and FaaS layers of cloud computing.

5. Waterfall vs. agile – The hospital build followed a classic waterfall schedule (clear phases, strict hand‑offs, limited change), yet incorporated agile practices such as rapid feedback loops, small‑team autonomy, and continuous integration of subsystems. The article discusses when each model is appropriate.

6. Quality‑in‑built three‑act – From "doing the right thing" to "doing things right" and finally minimizing quality cost, the study outlines quality management across design, implementation, acceptance, and operation phases.

7. Operational challenges for medical teams – Four major difficulties are identified: urgent business with incomplete delivery, new clinical workflows with limited training, ad‑hoc team formation lacking cohesion, and high infection risk requiring strict personal protection.

Overall, the rapid, high‑quality construction demonstrates how strong leadership, modular design, parallel value streams, and a blend of waterfall planning with agile execution can achieve "Chinese speed" in both physical infrastructure and software development.

cloud-nativeproject managementDevOpsquality managementAgileconstruction
DevOps
Written by

DevOps

Share premium content and events on trends, applications, and practices in development efficiency, AI and related technologies. The IDCF International DevOps Coach Federation trains end‑to‑end development‑efficiency talent, linking high‑performance organizations and individuals to achieve excellence.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.