Before diving into specific examples, let’s discuss the general approach to designing and facilitating collaborative events. As a Scrum Master, it’s important to not only focus on the technical aspects of the event but also anticipate and manage human dynamics.
Key dynamics to consider:
- Engagement – Maintaining participants’ energy and focus throughout the session
- Openness – Ensuring everyone has an equal opportunity to contribute.
- Insight – Encouraging breakthrough thinking and problem-solving.
- Results – Driving toward specific, action-oriented outcomes.
Example 1: Sprint Planning Meeting
Our first example of a collaborative event in the Scrum process is the sprint planning meeting. In this meeting, the team decides what work they will complete in the upcoming sprint.
Designing the event:
Decide on the time, date, and location for the meeting. Ensure the product backlog is well-refined, and the team is aware of the meeting’s objectives. Have a tentative plan in order, but also be flexible to accommodate team’s dynamics.
Facilitating the event:
Introduce the meeting’s objectives. Facilitate a discussion around the user stories in a product backlog and the team’s capacity. Encourage team members to participate, foster a respectful environment for discussion, and guide the team towards a commitment for the upcoming sprint.
Example 2: Retrospective Meeting
The retrospective meeting is another important collaborative event in Scrum. In this meeting, the team reflects on the previous sprint to understand what went well and uncover areas of improvement.
Designing the event:
Determine when and where the retrospective will be held. Agree on the retrospective format (Start, Stop, Continue, etc.), and ensure necessary materials for the event.
Facilitating the event:
Start the meeting by setting the guidelines for respectful and open communication. Facilitate the discussion around the agreed format and help team members prioritize actionable items for the next sprint. Ensure to capture all the suggestions and ensure active involvement of all members.
Comparing the Two Events
| Event | When | Purpose | Facilitation |
| Sprint Planning | At the beginning of each iteration or sprint | Decide what work will be done in the upcoming sprint | Encourage participation, guide towards commitment |
| Retrospective | At the end of each iteration or sprint | Reflect on the past sprint, identify what went well, and determine areas of improvement | Foster open communication, prioritize improvements |
In conclusion, designing and facilitating collaborative events are crucial skills for an Advanced Certified ScrumMaster. The A-CSM should foster an environment of open and respectful communication, promote active participation, and guide the team towards their goals. The collaborative events like Sprint Planning and Retrospective Meetings provide ample opportunities for the ScrumMaster to showcase these skills while driving the team towards continuous improvement.
Practice Test
A collaborative event in Scrum is a meeting with a set agenda and fixed duration.
- A) True
- B) False
Answer: A) True
Explanation: In Scrum, meetings or “events” are time-boxed to ensure focus and productivity. They follow certain agenda to meet the objectives.
The primary focus of the Sprint Planning meeting is to identify potential risks and issues for the upcoming sprint.
- A) True
- B) False
Answer: B) False
Explanation: The primary focus of the Sprint Planning meeting is to decide what work will be done in the upcoming sprint and how this work will be done.
The duration of a collaborative event in Scrum is determined by the Scrum Master alone.
- A) True
- B) False
Answer: B) False
Explanation: The duration of Scrum events is prescribed in the Scrum guide and is not solely determined by the Scrum Master. Scrum Master facilitates these events but does not dictate their duration.
It’s important for a ScrumMaster to utilize effective facilitation techniques to lead collaborative events.
- A) True
- B) False
Answer: A) True
Explanation: A ScrumMaster’s role is to facilitate events and conversations, helping the team to collaborate and reach agreements.
A retrospective is a collaborative event where a team looks ahead at potential improvements for future sprints.
- A) True
- B) False
Answer: A) True
Explanation: A retrospective is an opportunity for the team to inspect itself and create a plan for improvements to be enacted during the next sprint.
Who determines what will be done in the upcoming sprint?
- A) Development team
- B) Product Owner
- C) Scrum Master
Answer: A) Development team
Explanation: It’s up to the members of the development team to self-manage and decide which items from the backlog they can commit to delivering in the upcoming sprint.
In Scrum, what is considered as the heartbeat of Scrum?
- A) Sprint retrospective
- B) Sprint review
- C) Sprint
Answer: C) Sprint
Explanation: The Sprint is considered the heartbeat of Scrum, where ideas are turned into value.
The Product Owner is responsible for facilitating collaborative events in Scrum.
- A) True
- B) False
Answer: B) False
Explanation: It’s the Scrum Master’s responsibility to facilitate collaborative events in Scrum, not the Product Owner.
Which of the following is NOT a common collaborative event in Scrum?
- A) Sprint planning
- B) User testing
- C) Daily Scrum
Answer: B) User testing
Explanation: While user testing is important, but it’s not considered a common collaborative event in the Scrum framework.
Failed sprints should be viewed as a negative outcome and avoided at all costs.
- A) True
- B) False
Answer: B) False
Explanation: In Scrum, a failed sprint is a learning opportunity and provides valuable insights for the team to improve.
Interview Questions
What are collaborative events in Scrum?
Collaborative events in Scrum are certain meetings and interactions such as Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective that bring the Scrum team together to plan, review, and improve their work.
How is the Sprint Planning event designed in Scrum?
In Sprint Planning, the whole team comes together to plan the work for the upcoming Sprint. The Product Owner presents the highest priority items on the Product Backlog and the team discusses how to implement these items, resulting in a Sprint Goal and a Sprint Backlog.
What purpose does the Daily Scrum serve in a Scrum team’s routine?
The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. It promotes constant collaboration and adjustment.
What is the purpose of a Sprint Review in Scrum?
In the Sprint Review, the Scrum Team and stakeholders inspect the outcome of the Sprint and figure out what to do in the upcoming Sprint. The Product Backlog may also be adjusted based on the feedback.
How is a Sprint Retrospective organized and what benefits does it have?
The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. Facilitating it effectively helps the team continuously improve their process and teamwork.
What is important to consider when facilitating collaborative events?
It’s important to create an environment where everyone feels comfortable to express their ideas and concerns. The Scrum Master should effectively guide the team to keep the focus on the meeting’s objective making sure all voices are heard.
How might a Scrum Master ensure all members participate in collaborative events?
A Scrum Master can use techniques such as round-robin to ensure each team member has an equal opportunity to contribute. They can also use silent brainstorming or other creativity-enhancing techniques to promote deeper thought and active engagement.
Can the format and time of collaborative events be adjusted?
Yes, the time and format of events can be adjusted based on the team’s needs and preferences, as long as the objectives of the events as described in Scrum Guide are still met.
Can collaborative events be skipped if the team finds no value in them?
The decision to skip any Scrum event should be made with great care. These events are crucial for ensuring transparency, inspection, and adaptation, which are the pillars of Scrum.
Who is responsible for facilitating the collaborative events?
The Scrum Master is generally responsible for facilitating the Scrum events, though other team members can also lead these meetings if the Scrum Master deems it beneficial for the team’s development.
extutorials.com