Group Meeting Day

The classroom will be open at our normal class time (9:25 - 10:40) on 4/24, but I will not be there. I do want your group to complete this pair programming activity. You can choose to do this hour and 15 minute activity during the normal class or at another time. Your entire group has to agree to a different date and time or come to the normal classtime. If you cannot reach your group to make arrangements, assume that you will meet your group in the classroom.

Your Sprint #1 should be fully coded and your Sprint #2 should be fully designed. You are in the coding stage and plan to have much of it done by 4/29, with the project completely tested by 5/6.

Pair programming is a feature of Extreme Programming. Practice pair programming for about an hour. One person will look over the shoulder of the typing programmer for 25 minutes. While you are looking over the shoulder, also write junit tests for the class being coded or improve the diagrams for the sprint. After 25 minutes, switch places. (If you have 3 members in class, make the time periods smaller.) It may not be the most productive, but you may also experience some benefits you did not expect. See here for the junit presentation

At the end of class, give your group 15 minutes to report for the burn down chart and then talk about whether the release should be trimmed down. Your burn down chart will give you an idea of whether trimming is needed. If you trim the release the user acceptance tests must change.

You can submit your burn down chart and partially coded project with at least one junit test today, or you can wait until 4/29.

Each person should submit a paragraph (on moodle's pair programming impression item) to discuss the following:
Having practiced pair programming a very little bit, tell me who you paired with and your impression of your short pair programming experience. Did more work get produced than normal? Was the work a higher quality than normal? Was it more or less frustrating to code with someone at your shoulder?