Team Decisions
From DaVinci
This page will be used to track decisions made by the team, the criteria for the decision, concerns, and when the decision should be revisited.
Contents |
Decision Tracking - 04/04/2006
Starting Today, team DaVinci will start tracking all decisions made by the team on this wiki page. It is the responsibility of the scribe to record decisions for tracking just as they record action items. It is the responsibility of the team to verify that the decisions are recorded and are recorded accurately.
Criteria
- Ensure we have specified criteria for making decisions.
- Ensure we capture decisions so they are not forgoten.
- Ensure we capture any concerns regarding the decision made.
- Ensure the team knows when decisions will be reviewed for effectiveness.
Concerns
Capturing duplicat information that is being captured in action items and proposals.
Revisit
We will revisit this decision at the end of Sprint 5.
Online Scrum Questions - 04/04/2006
We will start posting answers to the three scrum questions below on the Scrum Meeting forum of our bulletin board prior to our Scrum meetings during our Tuesday and Saturday common hours.
Scrum Questions
- What have you done since the last Scrum Meeting?
- What are you going to work on until the next Scrum meeting?
- Is anything blockling you from working? If so, what?
Criteria
- This allows us to shorten our Scrum meetings.
- Only need to skim status.
- Discuss clarifications.
- Discuss who will resolve blocking points.
- This will allow us to track blocking points and ensure they are resolved.
- This will provide valuable information for Sprint, semester, and project reflections.
Concerns
- This may be introducing additional overhead.
Revisit
We will revisit this decision at the end of Sprint 5.
Policy for missing common working hours - 04/04/2005
Any team member missing planned working hours must notify the team via email at least 48 hours in advance of the start of the common hours that will be missed (except in cases of emergency).
Criteria
- Some team members may be planning mmeetings for the whole team (agendas are due 24hours in advance).
- Some team members may be expecting to talk to other members for help or clarification with their task(s).
- It is expected that team members may need to miss common hours on occasion due to the schedule of common hours on Tuesday/Thursday evenings and on Saturday morning.
Concerns
None
Revisit
We will revisit this decision at the end of Sprint 5.
Communication Lead is Scribe - 04/04/2005
For informal (adhoc) meetings occurring during common working hours, the Communication Lead is responsible for recording action items and decisions.
Criteria
- Ensure decisions and action items are not lost.
- For informal (adhoc) meetings, there is no asigned scribe.
Concerns
None.
Revisit
We will revisit this decision at the end of Sprint 5.
Risk Triggers with dates between sprints - 04/27/2005
All risk triggers will be given dates that fall between sprints.
Criteria
- Avoid changing of tasks mid-way through a sprint (which would go against Scrum methodology).
- Sprints are short (2 weeks in summer), so trigger dates can be of suitable granularity even when dates are between sprints.
- Trigger status from between sprints will function as input into sprint planning
Concerns
A critical risk may hit a trigger point mid sprint and require immediate attention, but the trigger check date is scheduled for later.
Revisit
We will revisit this decision at the end of Sprint 7.