1. Meeting Practices Yan Wei Weiyan@cc.hut.fi

2. Foundation Extreme programming is used Meeting practices are based on extreme programming technology with some changes

3. Meetings in two phases Project planning phase (PP phase): User stories meeting Release planning meeting Implementation phase (IM phase): Iteration planning meeting Daily stand up meeting (not used) Weekly Status meeting (replacement)

4. User stories meeting (PP) Participates: development team and customer Frequency: 1 or 2 weeks Goal: get customer requirements (User stories in XP term) Maybe need 2 or 3 times

5. Release planning meeting (PP) Participates: development team and customer Frequency: only once Goal: create a release plan which is then used to create iteration plans for each individual iteration development team estimates the time used for each user story customer decides what stories need to be completed according to priority, time and resource permits

6. Iteration planning meeting(IM) Participates: development team and customer Frequency: 1 to 3 weeks according to each iteration duration Goal: produce the current iteration's plan of programming tasks Customer chooses the user stories to be implemented for the current iteration Failed acceptance tests for the previous iteration are also selected

7. Daily stand up meeting (IM) Communicate problems, solutions, and promote team focus Recommended by XP, not realistic for our project For us, use another kinds of meeting instead: Weekly Status meeting

8. Weekly Status meeting (IM)/1 Participants: all team members Frequency: once a week Preparation: XP pair groups: what’s done&what’s next; give the doc to PM beforehand PM: what’s done&what’s next from whole project point of view; make handout for group work and project work status.

9. Weekly Status meeting (IM)/2 Agenda: XP pair groups represent each group work status PM represents project status Questions and discussions Meeting minutes Choose one secretary for each meeting Use meeting handout as draft Add new things to or modify the draft into meeting minutes

10. Project reviews – Required by the course Participates: All developers, customer and mentor Frequency: at the end of each iteration of the course Preparation: According to the template given by the course Agenda: different agenda for normal project review and final demonstration Goal: checkpoints to ensure that the projects proceed as planned

11. Meeting suggestions Arrive on time A meeting agenda should be ready before the meeting When having the meeting, agenda should be followed first and leave the questions and discussions at the end As short as possible, otherwise not efficient and people get tired. Within 1.5 hours Within 2 hours for special long agenda’s meeting

12. Questions?