Student Resources > CMPT 275 > assignment schedule > client meetings

This is the schedule of client demonstration times for the 2015 summer semester.

• Two client demonstration meetings will be scheduled for each team soon after teams have been formed.
• Appointments will be assigned based on the information provided by each team.
• Appointments will be placed in the timetable below before 5:30 PM May 15th 2014
• 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.
• It is your responsibility to update the instructor if your course schedule changes so that rescheduling of your iteration review meetings is needed.
• After week 6 of the term changes to the schedule will be made only in exceptional circumstances.

Time	Thu. Jul. 16 TA	Thu. Jul. 16	Tue. Jul. 28 TA	Tue. Jul. 28
2:20-2:45	group 4	group 10	group 9	XXXXXXX
3:00-3:25	group 5	group 6	group 2	group 7
3:40-4:05	group 1	group 3	group 6	group 5
4:20-4:45	group 7	group 9	group 3	group 1
5:00-5:25	group 8	group 2	group 10	group 4
5:40-6:05	.	group 11	group 11	group 8

Iteration 1 and 2 Client Demonstrations

Before meeting with the client, make sure a working copy of your software for the iteration is available for demonstration on any one of the WINDOWS workstations in the CSIL lab.
Your team will have a chance to present your partially completed product to the client. The client will expect to see the features you promised in your implementation plan for the particular iteration. The "client" (the instructor in disguise) will review your software you present and give feedback. The client will ask to try the features you demonstrate. All members of your team must attend and take part in at least one of the two demonstrations. Any team member may attend one or both demonstrations.

Pointers

The following are a few pointers to help your client iteration review meetings be a success:

• Remember your primary audience; your client is not a computing science professional. Your client is an expert in another area of specialization who has contracted to have you build an application to fulfill their needs.
• Prepare for the meetings. The demonstrations are only 25 minutes long (maximum) so be ready and be sure you have planned which features you are demonstrating and you know how long they take to demonstrate. Allow a time for the client to try each feature.
• Plan your meeting so you can demonstrate each of the requirements of the system for the completed iteration that has been met.
• Be honest with the client; indicate which features expected in this iteration are not yet available.
• Be thorough in your system testing, you will lose fewer points for missing features than for a system that crashes and needs to be restarted during the demonstration

Some Rules for the Iteration 1 and 2 Client Demonstrations

At least 1/2 of your team members must attend each iteration review. At least 1/2 of the members of your team must demonstrate features during each iteration review meeting. All members of your team must be present and demonstrate features at at least one of the two iteration demonstrations. . Any student that misses both their team's Iteration 1 Client Demonstration and thier team's Iteration 2 Client Demonstrations (or does not present features at one of the iteration review meetings) will receive a grade of 0 for both the client iteration demonstration meetings.
The duration of each meeting will be up to 25 minutes. Your team's mark is not dependent on the length of your meeting. A better planned meeting with more concise demonstrations will give you a chance to demonstrate more features and will result in a higher grade

Marking Scheme - out of 20

The instructor or TA will evaluate each Iteration review according to the criteria listed below.

• Level of client satisfaction: how closely your software system satisfies the client's requirements.
• Stability and robustness of the system,
  You will receive a higher grade for some stable functional features than for having all features in an unstable system or a system that repeatedly crashes
• Completeness, number of promised requirements met
• At least 1/2 team members present at the iteration review. At least 1/2 of team members demonstrated features at the iteration review.
• Clarity and conciseness of explanations and demonstrations