As aforementioned, there was an apparent lack of communication between the Supplier and Customer groups - there were points were the Customer group apparently had specified certain features to be implemented that the Supplier group didn't - due to a lack of communication and being unable to find the requests in any of the specification documents given to the Supplier group, misunderstandings resulted. Furthermore, although a lot of emphasis during the design assignment was placed on documentation, not enough time was allotted to allow the coding team to develop a fully refined prototype (let alone the actual product). More time should be given to develop the product, so that the testing team can test the product under less stressful (and therefore rushed) conditions.

Furthermore, this apparent "rush" at the end of the Supplier project places unneeded stress upon the coding and testing teams, who must work closely together in tandem in order to succeed. Unfortunately, the documentation team was also placed under unnecessary pressure as deadlines approached - they also needed to work closely with the coding and testing teams in order to produce effective documentation for the product. While Squidsoft's teams managed to co-ordinate their actions, other groups may find this a point of contention. As a result of this "rush", less emphasis is placed on the test plan, and actual implementation portions of the design process. As members of our customer group were involved in their own supplier groups themselves, it was difficult to keep the channels of communication open (for feedback on the developing prototype) despite our efforts (having two group members act as representatives) to counteract such problems.

Also, it might prove useful to other groups, if the source code for the projects were also put up on the web, to act as coding tutorials for those familiar in the language(s) used.

Find Button  

Demo Script  
Source Code  

Main Page