HKSM

Video conferencing is a real-time audio-video tool used in Scrum to connect distributed team members and stakeholders during events and collaboration. It enables face-to-face interaction, screen sharing, and quick decisions when physical co-location is not possible.

Key Points

• Enables synchronous communication with audio, video, and screen sharing.
• Used across Scrum events: Sprint Planning, Daily Standup, Backlog Refinement, Sprint Review, and Retrospective.
• Improves transparency through visual cues, shared boards, and live demonstrations.
• Supports distributed teams by approximating face-to-face collaboration.
• Scrum Master facilitates time-boxing, participation, and decision capture.
• Integrates with digital tools such as online whiteboards and backlog systems.
• Produces documented decisions, action items, updates to the product backlog, and sometimes recordings.

Purpose of Analysis

Video conferencing is used to quickly analyze requirements, designs, risks, and progress in real time when teams cannot meet in person. It helps validate understanding, align on acceptance criteria, and resolve impediments with immediate feedback.

The technique reduces delay in decision making, strengthens shared understanding, and supports transparency and inspection within time-boxed Scrum events.

Method Steps

1. Prepare the event: agenda, time-box, goals, and the conferencing link in the calendar invite.
2. Verify audio, video, and screen sharing; set etiquette such as mute, cameras, and hand-raise.
3. Facilitate the session: follow the event structure, keep focus on goals, and use visual boards.
4. Use features when needed: screen sharing, breakout rooms, chat, reactions, and polls.
5. Capture outcomes live: decisions, updated user stories, action items, owners, and due dates.
6. Confirm understanding with brief summaries and check-backs before closing.
7. Store artifacts: meeting notes, updated backlog items, and optional recording or screenshots.

Inputs Needed

• Agenda, time-box, and event goal (e.g., Sprint Goal, Retrospective focus area).
• Product backlog, user stories, acceptance criteria, and Definition of Done.
• Access to the conferencing tool and collaboration boards (backlog tool, whiteboard).
• Participant list with roles (Product Owner, Scrum Master, Developers, stakeholders).
• Stable internet, camera, microphone, and a quiet space.
• Any reference materials such as designs, test results, or demo builds.

Outputs Produced

• Shared understanding of status, requirements, risks, and decisions.
• Updated product backlog items, estimates, and acceptance criteria.
• Documented decisions, meeting notes, and action items with owners.
• Identified impediments and follow-up tasks for the Scrum Master.
• Optional artifacts such as recordings, screenshots, or annotated boards.

Interpretation Tips

• Watch nonverbal cues to gauge understanding and engagement.
• Use short summaries and check for agreement to confirm decisions.
• Keep screenshares focused and switch presenters as needed.
• Time-box discussions; move deep dives to a parking lot if off-topic.
• Encourage equal voice; invite quieter members to share.
• Use live edits in the backlog tool to reduce transcription errors.

Example

A distributed team runs Sprint Planning via video conferencing. The Product Owner shares the product backlog and walks through the highest-priority user stories while screen sharing the board.

Developers ask clarifying questions, update acceptance criteria, and estimate. The Scrum Master time-boxes discussion, captures decisions, and records action items. The team ends with a clear Sprint Goal and updated backlog reflecting agreed scope.

Pitfalls

• Poor audio or bandwidth causing miscommunication and rework.
• Unclear facilitation leading to side conversations and time overruns.
• Not documenting decisions, leaving the backlog inconsistent.
• Meeting fatigue from long, unfocused sessions.
• Excluding participants due to time zones or accessibility needs.
• Overreliance on recordings instead of concise notes and updates.

PMP/SCRUM Example Question

A distributed Scrum Team has frequent misunderstandings during the Daily Standup because they use audio-only calls and cannot see blockers on the task board. As the Scrum Master, what is the best next step?

1. Cancel the Daily Standup and ask members to send status updates by email.
2. Adopt video conferencing with cameras on and screen share the task board during the Daily Standup.
3. Extend the Sprint by one week to allow more time for detailed discussions.
4. Let team members resolve blockers offline after the event to save time.

Correct Answer: B — Adopt video conferencing with cameras on and screen share the task board during the Daily Standup.

Explanation: Video conferencing supports transparency and rapid alignment by enabling visual cues and shared boards. The other options reduce collaboration, break time-boxes, or defer problem solving.