1. COMP3615,5615 Capstone Projects Week 2 2015

2. Overview of the semester Website tour – XP and roles – Assessment – note especially the individual mark operating as a cap on your final mark – Tools The role of the tutorial – Tutor to assist the group – Tutor to provide feedback – Group to meet and plan and co-ordinate and discuss progress The role of the assessments – Week 5/6 formative

3. Priorities for this week Decide roles, starting with Week 2 Manager and Tracker Decide on regular meeting times outside class Decide on group contract Create your Bitbucket site – Front page has key information for group to co-ordinate and links to rest – A personal page for each team member: who will record personal goals for the coming week, then record reflection on them at the end of the week – A page for the group contract – A page for minutes of the meetings in each lab, and in between – Link every claim to evidence

4. Client interaction Whole group may meet once early on Client interaction role then allocated and that person meets the client The person responsible for this role must record all discussion on the wiki Communicate with client - check client agrees with your record of key decisions

5. Group contract Policy on meetings – time and place (can be electronic) to meet outside class each week – Agreed policy on dealing with unavailability (eg timetable, known events) Timing for – main meetings -- at least 2 such blocks of time in addition to Mon 3-6 – adding meeting minutes to wiki – each team member checking these and indicating agreement or identifying problems (*** needed for later) – creating new Issues – Tracker reviewing progress each week Roles – All agreed roles and changes to them (rotating leadership in Weeks 2-4) About the Issues – Include all tasks: reading, test design, creating wiki resources, writing code, testing that code… – Policy for updating these – Policy for linking them to the individual member’s wiki page Process for reporting difficulties with a team member – Clearly defined commitments that have not been met – Opportunity to meet them by a new deadline – Need for handing task to another person

6. Leadership and XP RolesXP Roles In Weeks 2, 3 and 4, allocate different people to the two key leadership roles: Manager – schedules meetings (e.g. IterationPlan, CommitmentSchedule),IterationPlanCommitmentSchedule – makes sure the meeting process is followed, – records results of meeting for future reporting as Bitbucket Issues (during the class is a good time for one bout) – Does not tell people what to do (Customer and IterationPlan do that), when to be done (CommitmentSchedule), or check to see how they're doing (Tracker).IterationPlanCommitmentSchedule Tracker – 2-3 times a week, check the Bitbucket site for each person’s progress – asks each Programmer how they are doing, listens to the answer, takes action if things seem to be going off track.

7. Fine wikis

11. Priority tasks for this week Get internal communication for the group organised, making use of the contract Allocate roles (with rotating leadership roles for Weeks 3-5) Identify tasks to do this week Task: Learn about user stories from resources Elicit the first user stories from the client