Hold Team Stand-Up Meeting

(Activity) for Tier: Sprint

PURPOSE

Team stand-up meetings keep the development team up to date on the status of current work, plans for upcoming work, and any impediments that are slowing or blocking their work. The stand-up provides a regular cadence of peer-to-peer sharing of information in a short, focused, and energetic meeting. This practice contributes to team cohesion and reduced waste in the form of re-work, defects, and team member waiting.

PARTICIPATING ROLES

• ACCOUNTABLE

  • Scrum Master

• RESPONSIBLE

  • Scrum Master
  • Project Manager
  • User Experience Architect
  • Database Developer
  • Developer
  • Lead Developer
  • Test Manager
  • Tester
  • Business Analyst
  • Product Owner

INPUTS

• Sprint Goal
• Sprint Backlog
• Burndown Chart - Sprint Progress

ENTRY CRITERIA

• Established cadence of meetings.
• Sprint tasks are up to date.

WHEN

Daily during a sprint.

SUB-ACTIVITIES

1. Schedule Team Stand-Up Meeting

   • Determine Team Stand-up cadence.
   • Communicate time and place of the Team Stand-up to the team.

2. Report Status

   • Each person who is working on the Sprint Backlog reports the following:

     • Tasks performed since last meeting.
     • Tasks that will be performed prior to next meeting.
     • Current impediments, if any.

   • Review the sprint burndown to ensure the team is trending toward finishing on time.

3. Post-Daily Stand Up

   • Update or Create tasks to capture actions for removing impediments or other actions needed to achieve the sprint goal.

EXIT CRITERIA

• Sprint burndown and progress against the current sprint backlog has been reviewed.

OUTPUTS

SEE ALSO

Process Guidance Version: 10.4