Student Resources > CMPT 275 > assignment schedule > client meetings

This is the schedule of available Client meeting times for the 2015 Summer semester.

• Each team will be assigned a client requirements review meeting appointment soon after teams have been formed.
• It is your responsibility to assure that the instructor has received an email from your team containing an ordered list (in order highest preference to lowest preference) of five meeting times selected from the available times in the schedule below by Friday May 15 at 5:30PM
• Appointments will be assigned based on the information provided by each team.
• Appointments will be placed in the timetable below before 8:30AM May 17 2015
• Appointments will be changed only in cases of conflict with another class (scheduled lecture or lab), conflicts with an academic, medical, or employment commitment made prior to scheduling of appointments, or other exceptional reasons. It is your responsibility to request such changes as soon as possible after the schedule is posted.
• No changes to the schedule will be considered after May 19, 2015
• All meetings, except where otherwise indicated in the table below, will be held in TASC1 9408

NOTE: Slots marked ------- are not available

Client Requirements Gathering Meeting

During the Client Requirements Gathering meeting you will meet with the "client" (the instructor in disguise). Your team will have a chance to ask questions to help you to clarify the requirements of your project. The following are a few pointers to help you prepare for a successful meeting:

• Remember your audience; your client is not a computing science professional. Your client is an expert in the application area who has contracted to have you build an application to fulfill their needs.
• Prepare for the meeting by reviewing the project content specification, and crafting questions to help you clarify any unclear aspects of that specification.
  • Discuss the contents of the specification with the other members of your team.
  • Consider common scenarios that must be handled by the system. Use these scenarios to help you identify which parts of the specification are clear to the entire team, which parts were interpreted differently by different team member (a sure sign that clarification is needed), and which parts are unclear to your entire team.
  • Design questions to clarify the scenarios with unclear details and extract the additional needed information from the client
  • Remember to also summarize the scenarios that are clear to your entire group when you speak with the client. It is possible that you have missed something or share a common misconception that the client can clarify.
  • When you to summarize your understanding using a scenario, to set the stage for a question, or to verify a scenario you think you understand, be clear and concise.
• The meeting will be held in an office with no audio visual support. Any visual aids you wish to use should be brought to the meeting on paper. Be sure text on any visual aids you bring is large enough to be easily read and is clear and legible. Do not overuse visual aids.
• Be flexible; remember that the answers to some questions may make other prepared questions irrelevant or inappropriate. Omit prepared questions that are no longer relevant and be ready to craft addition questions on the spot when it becomes necessary.

Some Rules for the Client Requirements Gathering Meeting

• All members of your team must be present at the meeting. If you miss your team's client meeting you will receive a grade of 0 for the client meeting
• All members of the team must participate by asking questions during the meeting.
• The duration of the meeting will be between 45 and 55 minutes. If your meeting is not completed in 55 minutes marks will be deducted.
• Your team's mark is not dependent on the length of your meeting (unless you exceed 55 min). A better planned and organized meeting will result not only in a higher grade but also in a clearer understanding of the requirements of the project.

Submission for Requirements Gathering Meeting:

The submission for this deliverable consists of one PDF file. The PDF file will contain a list of your team members and their chosen (or assigned) management duties. Completing a large project requires organization and leadership. In class, management and phase management roles for the term project were discussed. Your submitted PDF document should list the roles taken by each of your team members. In particular your PDF document must contain

• The full name of the team member (as it appears in COURSESYS)
• The management role that team member has chosen or been assigned
• The phases (deliverables, including UAT, final submission, iteration reviews, etc) that that team member will be managing

Marking Scheme - out of 50

A maximum of 46 points can be earned during the Requirements Gathering Meeting. Each team's presentation will be evaluated according to the criteria listed below.

• All team members present at the meeting asked questions and participated equally in the meeting
• Questions and summaries of the team's understanding were clear and concise
• Coverage of questions, clarifications, and discussions (summaries) was complete (covered all aspects of the project)
• Questions were divided in logical groups to provide continuity and flow in the meeting, organization of questions was logical
• Team members were able to pursue and clarify newly discovered ideas/requirements with additional unplanned questions.
• The team made good use of time (e. g. meeting lasted between 45 and 55 minutes, team discovered new requirements and clarified unclear requirements)

A maximum of 4 points can be earned for your team's submission.