Page Comparison

• Meet daily for 30 minutes max to air vexing programming issues
• Initiate a cooperative dialog towards resolving or exploring the issues
• Identify issues that may need help beyond the group.
• The ground rules are also simple

1. Each programmer will come to the meeting armed with one issue, if applicable, on which he or she needs constructive input
   1. A programmer does not have to have an issue every day
   2. Each programmer will prepare his/her issue before the meeting and add it via the comments section on the appropriate meeting's confluence page. Meeting's confluence pages or identified by the date when the meeting takes place.
2. Each day there is a different pre-identified leader who owns the session. This person will read each programmer's issue.
3. Group votes on each issue to hear more that day on each particular issue or to defer. Majority is in. Ties are called by the lead. Remainder of time is spent discussing accepted items. (e.g. If all are accepted you have 5 mins per issue max: 5 people x 5 issues = 25 mins. If none are in then the lead's issue is automatically in and you spend all the time on his/her issue. (That leaves 5 mins for first summaries and voting)
4. An issue brought to a meeting a third time must be addressed.
5. Group can (and is encouraged) to arrange additional time outside the meeting to solve tougher problems. It may also forward issues to the supervisors for additional help.
6. Day's lead prepares meeting's summary in confluence, using the established template
7. Issues and tasks that arise from these meetings need to be entered in JIRA's Sakai project.
   1. Make sure that the "XP Meeting" component is selected while creating the task/issue.

...