1. Feb. 6, 2001CSci 250 - Clark University1 CSci 250 Software Design & Development Lecture #7 Tuesday, Feb. 6, 2001

2. Feb. 6, 2001CSci 250 - Clark University2 Class Format for Today §Turn in: Requirements Document l Reminder: Student Evaluations due Thursday §Questions §Brief lecture on Chapter 3 §Communications Exercise    For Thursday: Don’t leave today without getting Functional Specifications handout

3. Feb. 6, 2001CSci 250 - Clark University3 Questions? §From last class - UML §About Content Index §Anything else?

4. Feb. 6, 2001CSci 250 - Clark University4 Chapter 3 Project Communication

5. Feb. 6, 2001CSci 250 - Clark University5 Running a successful meeting §What is the purpose of holding a meeting? §What are the elements of a good meeting? l What are the roles? l What do you need to prepare? l What should you take away? §What are some common things that go wrong in meetings?

6. Feb. 6, 2001CSci 250 - Clark University6 Meeting Purpose §Enable a number of participants to: l Share ideas within a team l Get input from outside the team l Brainstorming - coming up with new ideas l Schedule a project or phase of development l Review status of work completed so far l Bring up & discuss current problems l Negotiate & resolve issues

7. Feb. 6, 2001CSci 250 - Clark University7 Successful Meeting Elements §Meeting facilitator - responsible for: l Organizing, scheduling l Creating an agenda l Keeping the meeting on track §Minute taker - responsible for: l Taking notes to record discussion l Capturing open issues l Distributing minutes after the meeting

8. Feb. 6, 2001CSci 250 - Clark University8 What participants should do §Help facilitator to keep the meeting on track l Everyone has the responsibility for making a meeting successful §Prepare in advance l You have an agenda, know what you need to say §Be a good listener l When someone else is speaking, don’t interrupt

9. Feb. 6, 2001CSci 250 - Clark University9 What sometimes goes wrong? §Scheduling difficulties, inappropriate attendance §Facilitator isn’t prepared and/or is disorganized §Discussion gets too detailed or gets off track §Obstructions to effective communication: l Interruptions, taking things out of context, defensiveness, finger pointing, etc. §No effective follow-up: l No minutes, or nothing done with minutes

10. Feb. 6, 2001CSci 250 - Clark University10 Communications Exercise Project Meeting (Role Playing)

11. Feb. 6, 2001CSci 250 - Clark University11 For Next Time: Functional Specifications