At the University of Pretoria we had two teams develop the same project - the one using a waterfall based development method and the other using Scrum as an agile development process. The project was to add client based secure group chat functionality to the Linphone chat application without making any changes to the server -- i.e. the server did not have any group chat functionality itself. The result was interesting. The waterfall team committed more thought into the software architecture and came up with a distributed architecture without a single point of failure - even if the group creator./owner went off-line, the remaining group members could still continue with the group chat. In the Scrum based project all communication for a group went via the group owner node and hence there was a single point of failure. On the other hand, the Scrum based project came up with a more intuitive and more usable user interface for the application, most probably due to the short client feedback cycles.