...
- Scrumaster will drive the meeting, using the burndown chart. Purpose is to simply assess if we are on track: were our estimates correct or do we need to adjust them? are we on schedule with our due dates on tasks? Are there impediments that need to be addressed?
- This will require developers having estimates, and due dates in their tasks
- Are there any issues relevant to the whole team, or red flags that need to be raised?
- Scrum should be brief, probably closer to 15 minutes than a half hour.
WEEKLY TRIAGE
- QA should review all issues in the Triage queue before the meeting.
- Note: Suggest developers wait and review Triage list right before the meeting or save time and just listen at the meeting.
- QA should run the Triage meeting.
- QA person should take notes; it's helpful to have a printed issues list.
- Triage meeting should run as:
- QA person reads the issue number, the title and a brief description of the problem if needed - just enough info until the issue is understood.
- Discuss if issue is related to another issue, a dupe, ask questions, request additional testing if needed, etc.
- Team should:
- Understand the issue to make sure change makes sense.
- Think about possible ramifications of the requested change.
- Make sure noted bug issue is really a bug (and not expected behavior).
- Make issue decisions:
- To be part of the current Sprint or which bucket it gets added to?
- Assign resource.
- If additional testing is needed, the issue could be reviewed again at the next Triage meeting or decided now.
- QA should should update Triage issues soon after the meeting.
- Assign resource, Fix Version bucket, etc.
- Include any relevant notes, link issue, etc.
- Updates should include a comment to detail what's being changed, i.e.: Changing to Robin, Codfish as per Triage meeting 12/21/07.
ROLES:
Project Manager:
- Tracking status
- "The accountability piece": main artifact is the Burn-down chart
- Red flags (ie: people are going beyond what they estimated, totals add up to more time than is allotted, etc) should be raised to Janet
- Coordinate Biz issues
- Include PM tasks in the chart, with estimates and dates
- Collect information off-line, not in meetings
...