![]() |
![]() |
![]() |
||||||
|
||||||||
edit 6210 participation2003.11.06T3 Design Team MeetingThe agenda for this team meeting consisted of a report of a meeting between some members of the team and the client, the introduction of a new section to the project, some specific concerns about the current version of the project, and planning the evaluation stage of the project. Arising from the meeting with the client were some concerns the team had about using consistant terminology across the scope of the project and in the class room whrere the project will come into play. This wound up being a very painstaking process, with the entire team walking through what seemed to be a very small section of their work, to keep them all on the same page. The team eventually worked through the issues to their satisfaction. Next, Greg introduced the new section of the project that the client brought up in their meetings Monday and Tuesday. This new section is to be called "Wood ID," will consist of a dynamically generated flow chart. This seemed to me like a very late point to be changing the scope of the project. Finally, the team discussed the evaluation stage of the project. They had already selected a group of 4 people to use as pilot testers. The pre- and post-test were used as evaluation tools. The tests consisted of multiple choice, drag and drop, and fill in the blank questions, and learning will be determined by the differences in answers from the pre-test to the post-test. The sample size of 4 is too small to be statistically significant, but will help in determining whether any learning is taking place. It was arrainged during the meeting with the client earlier in the week that the evaluation would take place November 18th-19th. The largest problem I witnessed during the team meeting was an obvious lack of communication. There seemed to be problems in team-team communication (for example, the team didn't seem to be on the same page as far as terminology is concerned), team-client communication (the additional section this late in the project), and team-consultant communication (the dates and times for evaluation agreed to by the team directly conflicted with many of the consultants' jobs or other commitments, and the consultants were expected to be a large part of the evaluation stage). It seems to me that any other problems that this team had likely stemmed from a lack of communication. |
![]() |
contact: michael at lodick.com | ![]() |