CASM C10 Lesson 10 - Scrum Events
C10-01: What are the six events in the Scrum World and in the ASM world?
1. Release Planning Meeting / Process Planning Meeting 2. Sprint Planning Meeting / Sprint Planning Meeting 3. Sprint / Sprint 4. Daily Scrum / Daily Scrum 5. Sprint Review / Sprint Review 6. Sprint Retrospective / Sprint Retrospective All of these events are mandatory except the Scrum Release Planning Meeting. Not every Sprint will lead to a release - some Sprints deliver an increment that is part of a much larger project or piece of work. The Scrum Team should only carry out release planning if it is relevant for the particular Sprint. During all events, it is the role of the Scrum Master to facilitate the meetings and keep the Team focused. This will ensure that proper inspection and adaptation takes place. Using these events will help to ensure the pillars of Scrum are brought to life.
C10-02: Timexboxes - All mandatory Scrum events are timeboxed. Scrum uses timeboxes to define the maximum duration of an event. This ensures an appropriate amount of time is allocated to and spent on planning without allowing any waste. Using timeboxes maintains focus, and stops stakeholders getting diverted away from the key topics. What are the time-boxes for the five events 1. Sprint Planning Meeting 2. Sprint 3. Daily Scrum 4. Sprint Review 5. Sprint Retrospective
1. Sprint Planning Meeting: 4 to 8 hours 2. Sprint: 2 to 4 weeks 3. Daily Scrum: 15 minutes 4. Sprint Review: 2 to 4 hours 5. Sprint Retrospective: 1.5 to 3 hours
C10-09: At the end of each Sprint, a Sprint Review meeting is held. During this meeting, the Scrum Team shows what they accomplished during the Sprint. The Scrum Master ensures that this event takes place and that all attendees understand its purpose. The Review is timeboxed for 2 to 4 hours, and the Scrum Master coaches attendees to help them stay within that time. What is the character of the Sprint Review meeting? (4A)
1. This is an informal meeting, not a status meeting, and the presentation of the increment is intended only to elicit feedback and foster collaboration. 2. The Product Owner, Scrum Master and the Team will all be part of the Sprint Review meeting. 3. The Product Owner can update on the status of the Product Backlog, and the Team can discuss what went well, and what didn't go so well. 4. It's very important for all attendees to collaborate on what to do next. The Sprint Review provides valuable input to the next Sprint Planning Meeting.
C10-07: What are the questions each team member shall answer during the daily scrum?
1. What did you do yesterday? 2. What will you do today? 3. Are there any impediments in your way? By focusing on what each person accomplished yesterday and will accomplish today, the team can understand what work has been done and what work remains.
C10-15: (Quiz Question 1) Which SCRUM event is NOT mandatory? A. Release Planning Meeting B. Sprint C. Daily Scrum D. Sprint Retrospective
=> A
C10-17: (Quiz Question 3) How long is the Daily Scrum timeboxed? A. 10 minutes B. Fifteen minutes C. 30 minutes D. One hour
=> B
C10-19: (Quiz Question 5) Which Scrum event is NOT timeboxed? A. Daily Scrum B. Sprint Retrospective C. Release Planning Meeting D. Sprint Planning Meeting
=> C
C10-20: (Quiz Question 6) How long is the Sprint Review timeboxed? A. Fifteen minutes B. Thirty minutes C. 1 to 2 hours D. 2 to 4 hours
=> D
C10-03: In Scrum, work is confined to a regular, repeatable work cycle, which is referred to as a sprint or iteration. What is the difference between an 'iteration' and an 'increment'?
An increment is the sum of all the Product Backlog items completed during a Sprint and all previous Sprints. The term iteration relates to the Sprint - each repetition of a sprint (or work process) is an iteration. Iteration involves repeating a process, usually with the aim of approaching a desired goal or target or result.
C10-10: Another event that takes place after the Sprint is the Sprint Retrospective. The sprint retrospective is usually the last thing done in a sprint, and many teams will do it immediately after the Sprint Review. What is the difference between the 'Sprint Review' and the 'Sprint Retrospective' ?
'Sprint Review': This is an informal meeting, not a status meeting, and the presentation of the increment is intended only to elicit feedback and foster collaboration. 'Sprint Retrospective': It identifies actionable improvements that can be implemented in the next Sprint
C10-14: Definition of "Done". Why is the definition of "Done" so important? (6A)
1. Teams must deliver a completed increment every Sprint. How do they know when it is "done"? 2. To be effective, the definition of done should include the perspective of all team members. 3. Team members must have a shared understanding of the Definition of Done which they can use to assess when work is complete on the increment. 4. A completed increment should be potentially shippable or ready to release. 5. The Definition of Done also guides the Team in knowing how many Product Backlog items it can select to work on during Sprint Planning. 6. If the desired end state isn't clear, it can be very challenging for the team to know what can be done during a Sprint.
C10-13: What is the purpose of the Sprint Retrospective? (3A)
1. The purpose of the Sprint Retrospective is to inspect how the last Sprint went with regards to people, relationships, process, and tools. 2. It will identify and order the major items that went well, and any potential improvements. 3. It will create a plan for implementing improvements to the way the Scrum Team does its work.
C10-21: (Quiz Question 7) Which of the following is NOT true about the Definition of Done? A. It is used to assess when work is complete on an increment B. It guides the Team in knowing how many Product Backlog items it can select during Sprint Planning C. It defines the end of the Sprint D. It defines when an increment is potentially shippable or ready to release
=> C
C10-16: (Quiz Question 2) Once a Sprint has been planned, under what circumstances would changes be allowed? A. With the customer's consent? B. With the team's consent? C. With the Scrum Master's consent? D. With the Product Owner's consent?
=> D
C10-18: (Quiz Question 4) Who must attend Scrum meetings A. Scrum Master B. Team C. Product Owner D. All of these
=> D
C10-05: Who should attend the Daily Scrum meeting ... ?
All team members must attend scrum meetings, including the Scrum Master and Product Owner. They too are committed team members. Other staff may attend, but will only be allowed to listen. Scrum meetings can be a good way to share information with these staff.
C10-12: What is a simple way to carry out a Sprint Retrospective ?
Ask the three questions: 1. What should the team Start doing? 2. Stop doing? 3. Continue doing?
C10-08: The Daily Scrum meeting is not a status update meeting. It is ... ?
It is an inspection of the progress towards the Sprint Goal each day. At the Daily Scrum, team members can discuss impediments that are stopping them getting things done. If the Scrum Master cannot remove them immediately, he or she will take them away for action. You might also see the Daily Scrum referred to as the 'daily standup'.
C10-04: What is the difference between "committed" and "involved" in a Scrum Meeting ?
Scrum makes a distinction between those who are committed on a project and those who are only involved. The staff who are committed make up the Team. Scrum gives committed staff special status, and many teams enforce a rule in which only those who are committed are allowed to talk during the Daily Scrum meeting.
C10-06: Who is responsible for holding the Daily Scrum meetings?
The Scrum Master will be responsible for ensuring that the meeting occurs and the rules are followed. The Daily Scrum meeting is not used as a problem-solving or issue resolution meeting. Issues that are raised are taken offline and usually dealt with by the relevant sub-group immediately after the meeting.
C10-11: During the Sprint Retrospective, the team reflects on the accomplishments of the last Sprint and identifies and prioritizes improvements to their actual ways of working. This event isn't focused on the output of the Sprint - it is focused on how the Team worked during the Sprint. What are typical potential areas for improvements ? (6A)
1. Scrum Team composition 2. Meeting logistics 3. Tools 4. The Definition of Done 5. Communication 6. Process performance
