These lists of considerations are useful reminders for DAD teams to help them consider the practices of DAD and agile/lean during the various phases of the life cycles.
Use these lists of considerations as starting points. You should adapt them to fit your own local context and terminology.
Considerations for the Daily Coordination Meeting
Daily Coordination Meeting
Activity |
Description |
Setup |
Status of stories and tasks have been updated before the daily coordination meeting. |
Conduct |
Team members showed up on time. All team members were present. Team members talked with each other. Problem-solving and side conversations were kept to a minimum. |
Team and environment |
Team work space is clean: physical, communication, collaboration. Team’s project board is up to date. |
Impediments |
Progress on resolving impediments was reported. |
Daily Coordination Meeting Ground Rules
Rule |
Description |
Be consistent |
The daily coordination meeting meets every work day at the same time and in the same place. |
Show courtesy |
Team members show professional courtesy: show up on time, participate, and listen. |
Be brief |
The daily coordination meeting typically lasts for 15 minutes. This reinforces brevity. Extra discussions and problem-solving is conducted after the meeting, when there is more time. |
Hold a team-wide conversation |
The daily coordination meeting is for the team’s benefit. Each team member is expected to speak and speaks to the whole team. The team is not reporting to the team lead. The team lead is there to help facilitate this conversation but not to lead the session. |
Answer all three questions |
Each team member answer three questions:
Team members can raise issues and obstacles but not propose solutions. |
Review impediments |
The team lead reviews impediments and status. |
Swarm |
If you have the skills to help with a task and you do not have something else to do, you should volunteer to join the swarm. |
Finish work |
The priority is to complete stories that are in-work before starting new stories. |
Product Owner Overview
Practices
- Acceptance test-driven development
- Capturing functional requirements
- Controlling work-in-process (WIP)
- Daily coordination
- Decomposing a feature into stories
- Estimation
- Iteration demonstration and review
- Iteration demonstration and review (plan)
- Iteration planning meeting
- Iteration retrospective
- Operational metrics
- Unfinished work
- Visual controls
Considerations
- Considerations for DAD teams
- Considerations for daily coordination
- Considerations for value streams