Agile vs Waterfall, Measured on Real Builds
Two network simulators, two methodologies, one comparison
Instead of arguing methodology in the abstract, this study built two working Mininet-WiFi simulators under different process models. A satellite orbit simulator was developed Agile across four sub-goals. A concurrent network performance tester was developed Waterfall through full SRS and design documents. The resulting code structures diverged in ways the process literature predicts but rarely demonstrates.
Results
01The setup
Problem A was a satellite access point orbiting two ground stations through 15 generated 3D positions, measuring latency, bandwidth, and packet loss as distance changes. It went to Agile on the theory that interconnected features benefit from iterative refinement and independent testing before integration.
Problem B was a concurrent performance tester across wired, wireless, and mixed topologies, with 20 hosts and threaded execution. It went to Waterfall, since the requirements were stable enough to design fully upfront through an SRS and a four-layer design document.
02What it showed
Both delivered functional software and both passed their test suites. The difference was in the shape of the work. Agile absorbed the unknowns in orbital mechanics and 3D positioning by discovering them one sub-goal at a time. Waterfall's upfront architecture paid off on the tester, where the thread-pool and result-queue design had to be right before implementation started.