Still, a lack of a strict methodology doesn't necessarily make it waterfall.
Then, that whole steaming pile was thrown over the fence to QA which tried to figure out heads from tails and developers started fixing the issues they already knew about but had to leave in so that they would make their deadline.
THEN came user acceptance testing, where people actually looked at the product at the first time. This is when people realized what the miscommunications 6-12 months ago, and the change request process started.
Finally, over budget and after everyone was finally exhausted and tired of fighting, it was released to users with promises of changes after the release.
From this world, SCRUM and the manifesto makes sense.