AgileLiquid is described as agile. Liquid is also defined as requiring: well defined specifications and well defined parameters on what constitutes a successful outcome. The latter is pretty much a text book definition of a waterfall method. That is further confirmed by a description of how the project architect uses Liquid to first generate the design specifications and then uses another Liquid contest to generate the implementation. The timescales are too short and the communication mechanisms are too short to permit anything other than a command-and-control, full waterfall, throw the design over the wall methodology.
Qualified DevelopersThe Liquid Players can be motivated by the opportunity to
- Exercise skills just learned in class.
- Prove themselves in pursuit of a new career opportunity.
ScalabilityIt is claimed that the developer community has unlimited size, with the following benefits:
- Project leader can start work sooner.
- More work done in parallel.
- Reduced development cycle times
The Mythical Man Month , written in 1975, describes how such benefits are unlikely to materialize.