XS✔ ◾ Updating rules on Scrum

categories/project-delivery/rules-to-better-scrum.md

@@ -7,7 +7,7 @@ index:
   - scrum-guide
   - 8-steps-to-scrum
   - scrum-master-do-you-schedule-the-3-meetings
-  - do-you-know-what-happens-at-a-sprint-review-meeting
+  - what-happens-at-a-sprint-review-meeting
   - what-happens-at-retro-meetings
   - what-happens-at-a-sprint-planning-meeting
   - methodology-daily-scrums

rules/8-steps-to-scrum/rule.md

@@ -11,34 +11,33 @@ authors:
 related:
   - backlog-refinement-meeting
   - 3-steps-to-a-pbi
+  - scrum-master-do-you-schedule-the-3-meetings
 redirects:
   - do-you-know-the-8-steps-to-scrum
 created: 2013-06-28T03:50:10.000Z
 archivedreason: null
 guid: 5759f753-1524-4803-869c-8b881eae28a1
 ---
 
-Scrum is easier than it seems, we'll explain how in these 8 simple steps.
+Scrum may seem complex at first, but it’s simpler than you think. Follow these 8 easy steps to master it.
+
+<!--endintro-->
 
 `youtube: https://youtu.be/xOvFK328C_Q`
 
 **Video: 8 Steps To Scrum - Scrum Explained (4 min)**
 
-<!--endintro-->
-
 ::: good
-
 ![Figure: This Scrum image includes all the important steps from the Initial Meeting to the Sprint Review and Retro](8StepstoScrum.png)
-
 :::
 
 Print out the [SSW 8 Steps to Scrum PDF](https://ssw.com.au/downloads/8StepstoScrum.pdf) and put it on your "War Room" wall.
 
-### 1. [Initial Meeting](/meetings-are-you-prepared-for-the-initial-meeting)
+## 1. [Initial Meeting](/meetings-are-you-prepared-for-the-initial-meeting)
 
 In the Initial Meeting, the Product Owner explains the product vision. The Developers think about the Architecture needed and how long they will need to come up with an estimate.
 
-### 2. [Backlog Construction](/product-owner-do-you-know-how-to-update-the-backlog)
+## 2. [Backlog Construction](/product-owner-do-you-know-how-to-update-the-backlog)
 
 The next step is Backlog Construction, also known as a Specification Review. The Developers propose a high-level software architecture and a to-do list called the Product Backlog. The required features are broken down into Product Backlog Items (PBIs for short).
 
@@ -48,31 +47,31 @@ This is also when the Product Owner 1st defines the Product Goal (aka the "why"
 
 A quick note, there are only 3 roles in a Scrum Team, The Product Owner (the boss), the Scrum Master (a kind of project manager), and the Developers (who do the work).
 
-### 3. [Sprint Planning](/what-happens-at-a-sprint-planning-meeting)
+## 3. [Sprint Planning](/what-happens-at-a-sprint-planning-meeting)
 
 The Sprint Planning session is for the Developers to focus on the subset of the Product Backlog that they think they can complete in the next Sprint, (which is most commonly a 2-week timebox).
 
 The Product Owner puts the PBIs into priority order and makes sure the top ones have enough detail to be worked on. The Developers then pulls PBIs from the top of the Backlog and commits to delivering as much as they forecast they can, in the coming Sprint.
 
 The Developers and Product Owner together then define the Sprint goal, (aka the "why" of the Sprint).
 
-### 4. [Sprint](/sprint-forecast)
+## 4. [Sprint](/sprint-forecast)
 
 The Developers work on features in priority order, having done a [Daily Scrum](/methodology-daily-scrums) and sending 'Done' emails once the ['Definition of Done'](/definition-of-done) is met. A task board is often used. During this process, the team also refines items in the Product Backlog to ensure they conform to the ['Definition of Ready'](/have-a-definition-of-ready).
 
-### 5. Product Increment
+## 5. Product Increment
 
 Each Sprint is a potentially shippable Product Increment, and with good DevOps, including automation of deployment and testing, this can be done on a "PBI by PBI" basis. This means each feature worked on can be in production as soon as it is finished.
 
-### 6. [Product Feedback](/during-a-sprint-do-you-know-when-to-create-bugs)
+## 6. [Product Feedback](/during-a-sprint-do-you-know-when-to-create-bugs)
 
 Product Feedback will then come in. Some will be bugs, and some will be small changes that can be added to the current Sprint. Other suggestions should be approved by the Product Owner and then added to the Product Backlog.
 
-### 7. [Sprint Review](/do-you-know-what-happens-at-a-sprint-review-meeting)
+## 7. [Sprint Review](/what-happens-at-a-sprint-review-meeting)
 
 At the end of the Sprint, there is a Sprint Review, where the Developers demo or play done videos of the completed PBIs. The goal is for the Product Owner to understand the increment and to discuss the feedback to make the product better. This is the real measure of success of the Sprint.
 
-### 8. [Sprint Retrospective](/do-you-know-what-happens-at-a-sprint-retrospective-meeting)
+## 8. [Sprint Retrospective](/what-happens-at-retro-meetings)
 
 Lastly, there is the Sprint Retrospective, and this is the best part! The Scrum Team discusses what went well, what didn't, and what to improve, always inspecting and adapting.
 

rules/meeting-do-you-update-your-tasks-before-the-daily-scrum/rule.md

@@ -23,14 +23,17 @@ All team members must update their tasks with status, (and remaining hours if yo
 
 **Note:** If you are updating the details of a PBI then follow the rule [Do you know when you use @ mentions in a PBI?](/when-you-use-mentions-in-a-pbi)
 
+---
+
 ::: greybox
-In Scrum, there are 4 meetings in total that you need to know about:
+Learn more about the meetings in Scrum:
 
-- [Sprint Planning Meeting](/what-happens-at-a-sprint-planning-meeting)
-- [Scrum Meeting (Daily standup)](/meeting-do-you-update-your-tasks-before-the-daily-scrum) - Update tasks before Daily Scrum Meeting
-- [Sprint Review Meeting](/do-you-know-what-happens-at-a-sprint-review-meeting)
-- [Sprint Retrospective Meeting](/do-you-know-what-happens-at-a-sprint-retrospective-meeting)
+* [Sprint Planning Meeting](/what-happens-at-a-sprint-planning-meeting "Sprint Planning Meeting")
+* [Sprint Review Meeting](/what-happens-at-a-sprint-review-meeting "Sprint Review Meeting")
+* [Sprint Retrospective Meeting](/what-happens-at-a-sprint-retrospective-meeting "Sprint Retrospective Meeting")
+* [Scrum Meeting (Daily standup)](/methodology-daily-scrums)
 
+**Tip:** It can be helpful to finish the **Sprint Planning meeting** with the first **Daily Scrum** of that Sprint.
 :::
 
 ---

rules/methodology-daily-scrums/rule.md

@@ -57,21 +57,22 @@ The team's successes and failures are shared, and anyone who knows the answer to
 
 Follow these essential tips to improve your Daily Scrum meetings:
 
-### Tip #1: Be prepared for the meeting
+## Tip #1: Be prepared for the meeting
 
 Before you join the Daily Scrum, [check the group](/how-to-see-what-is-going-on-in-your-project) to see what your colleagues have been discussing and working on, and check the portal to confirm the meeting time. If you’re joining a new project or re-joining a previous one after some time away, these steps are important to keep yourself up-to-date and abreast of progress.
 
 Then you’ll be able to say to your Scrum Master: “I've had a look at the Teams group. I am ready to join the daily Scrum”.
 
-### Tip #2: Have your Scrum Master to review the Sprint progress at the end
+## Tip #2: Have your Scrum Master to review the Sprint progress at the end
 
 At the end of the Scrum, the Scrum Master should [review the current burn down](/burndown-and-stories-overview-reports-updates) to check on the progress of the team.
 
 ![Figure: A burndown chart in visualstudio.com](burndowntfspreview_1710232021943.png)
 
-### Tip #3: Keep a schedule of the Daily Scrum times on a wall (+ have a recurring appointment in Outlook)
+## Tip #3: Keep a schedule of the Daily Scrum times on a wall (+ have a recurring appointment in Outlook)
 
 ::: email-template
+
 | | |
 | -------- | --- |
 | To: | {{ TEAM }} |
@@ -97,7 +98,7 @@ Figure: Schedule a recurring Daily Scrum meeting in Outlook using this template
 
 ![Figure: Or you can use Microsoft Teams](teams-meeting-daily-scrum.jpg)
 
-### Tip #4: Keep to the schedule - Same place, same time (even if people are missing)
+## Tip #4: Keep to the schedule - Same place, same time (even if people are missing)
 
 Get started on time. Especially in the beginning, people will be late, but the meeting should be held with the remaining people. Don't worry. People learn.
 
@@ -111,39 +112,39 @@ If the Scrum Master is not a full-time member of the team (often they are), they
 
 :::
 
-### Tip #5: Update tasks before the Daily Scrum
+## Tip #5: Update tasks before the Daily Scrum
 
 Daily Scrums are more effective when team members arrive when their tasks are already updated.
 
 See [Do you update your tasks before the daily stand-up meeting?](/meeting-do-you-update-your-tasks-before-the-daily-scrum)
 
-### Tip #6: Don't go into detail
+## Tip #6: Don't go into detail
 
 Keep your answers short and concise. Do not stray from the 3 main questions. Don't let your Daily Scrum become a general meeting.
 
 Remember to use the ["Parking Lot"](/keep-track-of-a-parking-lot-for-topics), the place for any discussions that stop the Team from answering the 3 main questions. Only interested people stay for the "Parking Lot" to discuss issues after the Daily Scrum.
 
-### Tip #7: No phones + no checking email - No distractions
+## Tip #7: No phones + no checking email - No distractions
 
 Technology in the Daily Scrum causes people to lose focus on the goal. The goal is for the team to synchronize by sharing what they are doing. Avoid giving people the opportunity to be distracted easily by forbidding email, SMS and mobile phones from the Daily Scrum.
 
-### Tip #8: Use a task board (even better use an electronic one)
+## Tip #8: Use a task board (even better use an electronic one)
 
 A task board allows people to visualize what the team is talking about.
 
 ![Figure: A Task Board from Azure DevOps](tfspreviewtaskboard_1710232021943.png)
 
-### Tip #9: Carry a pen and paper
+## Tip #9: Carry a pen and paper
 
 Use a pen and paper to jot things down. A whiteboard is also great for "Parking Lot" topics that arise, to be discussed after the meeting.
 
-### Tip #10: If you have raised impediments, consider contacting the Product Owner
+## Tip #10: If you have raised impediments, consider contacting the Product Owner
 
 Often the Product Owner won’t be at the Scrum. However, call the Product Owner if you have an impediment (aka roadblock). Communication with the Product Owner is essential and if you haven't touched base with him in the few days, then do so. A disconnected or absent Product Owner is a sign of dysfunction.
 
 ![Figure: Call the Product Owner if you have an impediment](ProductOwnerTelephone_1710232021942.jpg)
 
-### Tip #11: Store Daily Scrums in the Teams team so the PO can easily access it
+## Tip #11: Store Daily Scrums in the Teams team so the PO can easily access it
 
 Sometimes, the Product Owner will want to see the Daily Scrum for many teams. Adding them to every meeting would create lots of noise in their calendar. Instead, make the [Teams meetings easy to find](/do-you-make-your-team-meetings-easy-to-find) so they can locate the Daily Scrum for any project via the Teams team.
 
@@ -155,21 +156,22 @@ Sometimes, the Product Owner will want to see the Daily Scrum for many teams. Ad
 ![Figure: Good example - Make Daily Scrums easy to find via the Teams Channel Calendar](daily-scrum-good.png)
 :::
 
-### Tip #12: What to do when you're working for a PO directly
+## Tip #12: What to do when you're working for a PO directly
 
 If you don't have a team, and you're doing ad hoc work for a PO directly, it's best to contact him for the Daily Scrum every day if possible, and follow up with an email. This will keep the 2 of you synchronized.
 
-### Tip #13: How do you enter Scrum meetings into your timesheets?
+## Tip #13: How do you enter Scrum meetings into your timesheets?
 
 Once you have completed your stand up, add “S” to your timesheet as per [Rules to Better Timesheets](/rules-to-better-timesheets).
 
-### Tip #14: Send an email
+## Tip #14: Send an email
 
 To prevent misunderstandings or potential disagreements, send your Daily Scrum update via email. This ensures that everyone on your team is aware of your current tasks, even if they were unable to attend the meeting. 😊
 
 **Note:** Be sure to include the project name in both the subject line and the email content, as people often read the message without referencing the subject.
 
 ::: email-template
+
 | | |
 | -------- | --- |
 | To: | Bob Northwind |
@@ -199,7 +201,7 @@ Today I'm working on {{ PROJECT NAME }}:
 Figure: Good example - Always include what you previously worked on and what you plan on doing today
 :::
 
-### Tip #15: Use IM
+## Tip #15: Use IM
 
 After you have sent your email, you can also make it front and center by sending them a ping on IM.
 _“Check your email for my Daily Scrum”_ or paste in the below (a lightweight version with only what to do).
@@ -249,7 +251,7 @@ Today I am working on:
 Figure: Good example - Clear details
 :::
 
-### Tip #16: Auto-generate your Daily Scrum with AutoScrum
+## Tip #16: Auto-generate your Daily Scrum with AutoScrum
 
 AutoScrum will scan your Azure DevOps repositories and find all the PBIs that you worked on yesterday and that are In Progress today.
 
@@ -277,3 +279,16 @@ The goal is to be productive for 8 hours of the day, so communicate with the res
 It is important that any major incidents are dealt with first. Start with any major incidents that occurred in the last 24 hours.
 
 ![Figure: Daily Scrums will alert everyone if there is a major problem and get all brains aligned in the right direction. There is no sense in putting a Band-Aid on a patient's scraped knee if there is a big knife in his eye!](NewStandUpImage_1710232021942.jpg)
+
+---
+
+::: greybox
+Learn more about the meetings in Scrum:
+
+* [Sprint Planning Meeting](/what-happens-at-a-sprint-planning-meeting "Sprint Planning Meeting")
+* [Sprint Review Meeting](/what-happens-at-a-sprint-review-meeting "Sprint Review Meeting")
+* [Sprint Retrospective Meeting](/what-happens-at-a-sprint-retrospective-meeting "Sprint Retrospective Meeting")
+* Daily Scrum (Stand-up) Meeting (this rule)
+
+**Tip:** It can be helpful to finish the **Sprint Planning meeting** with the first **Daily Scrum** of that Sprint.
+:::

rules/scrum-master-do-you-schedule-the-3-meetings/rule.md

@@ -1,6 +1,6 @@
 ---
 type: rule
-title: Scrum Master - Do you schedule the 3 meetings?
+title: Scrum Master - Do you schedule the 3 Scrum meetings?
 seoDescription: As a Scrum Master, scheduling 3 crucial meetings - Sprint Review, Retrospective, and Planning - ensures successful Sprints.
 uri: scrum-master-do-you-schedule-the-3-meetings
 authors:
@@ -10,7 +10,11 @@ authors:
     url: https://ssw.com.au/people/ulysses-maclaren
   - title: Matt Wicks
     url: https://ssw.com.au/people/matt-wicks
-related: []
+related:
+  - 8-steps-to-scrum
+  - what-happens-at-a-sprint-planning-meeting
+  - what-happens-at-retro-meetings
+  - what-happens-at-a-sprint-review-meeting
 redirects: []
 created: 2010-05-06T05:41:54.000Z
 archivedreason: null
@@ -21,6 +25,8 @@ The Scrum Master plays a key role in the Scrum framework by scheduling and facil
 
 <!--endintro-->
 
+![Figure: The 3 meetings in the Scrum steps](8StepstoScrum-meetings.png)
+
 The Scrum Master should estimate how much time each meeting will require, then schedule a single calendar appointment to cater to the 3 meetings. When scheduling the calendar appointment, keep in mind the following:
 
 * Ideally, each of the 3 meetings should be time-boxed to an hour for every week of their associated Sprint
@@ -33,12 +39,22 @@ The Scrum Master should estimate how much time each meeting will require, then s
 * Since these meetings will occur every Sprint - set a recurrence on the calendar appointment (every 1, 2, 3, or 4 weeks) so that people have the time blocked out well in advance
 
 ::: greybox
-**Tip:** It can be helpful to finish the Sprint Planning meeting with the first Daily Scrum.
+Learn more about the meetings in Scrum:
+
+* [Sprint Planning Meeting](/what-happens-at-a-sprint-planning-meeting)
+* [Sprint Review Meeting](/what-happens-at-a-sprint-review-meeting "Sprint Review Meeting")
+* [Sprint Retrospective Meeting](/what-happens-at-a-sprint-retrospective-meeting "Sprint Retrospective Meeting")
+* [Daily Scrum (Stand-up) Meeting](/meeting-do-you-update-your-tasks-before-the-daily-scrum "Daily Scrum Meeting")
+
+**Tip:** It can be helpful to finish the **Sprint Planning meeting** with the first **Daily Scrum** of that Sprint.
 :::
 
+## Scheduling the meetings
+
 Schedule the meeting and invite the Scrum Team and any interested stakeholders.
 
 ::: email-template
+
 | | |
 | -------- | --- |
 | Required Attendees: | Scrum Team |
@@ -47,7 +63,7 @@ Schedule the meeting and invite the Scrum Team and any interested stakeholders.
 | Subject: | {{ PROJECT NAME }} – Sprint Review, Retro and Planning |
 ::: email-content
 
-### Hi Team,
+### Hi Team
 
 * Product Owner: {{ PRODUCT OWNER }}
 * Scrum Master: {{ SCRUM MASTER }}
@@ -68,8 +84,8 @@ See rule [What happens at a Sprint Retrospective Meeting?](/do-you-know-what-hap
 
 **Sprint Planning Meeting**
 
-We go through the backlog (aka to-do list), get more information, estimate and then prioritize.   
-We then breakdown to tasks and commit to what we believe we can deliver for the next Sprint.   
+We go through the backlog (aka to-do list), get more information, estimate and then prioritize.
+We then breakdown to tasks and commit to what we believe we can deliver for the next Sprint.
 See the rule [What happens at a Sprint Planning Meeting?](/what-happens-at-a-sprint-planning-meeting)
 
 Regards,
@@ -88,13 +104,3 @@ Figure: Good example - Copy this appointment template and send to the Scrum Team
 :::
 
 See [Meetings - Do you know when to send an Appointment or a Teams Meeting?](/send-appointment-or-teams-meeting) for more information.
-
-::: greybox
-In Scrum, there are 4 meetings in total that you need to know about:
-
-* [Sprint Planning Meeting](/what-happens-at-a-sprint-planning-meeting)
-* [Daily Scrum Meeting](/meeting-do-you-update-your-tasks-before-the-daily-scrum "Daily Scrum Meeting") (Stand-up)
-* [Sprint Review Meeting](/do-you-know-what-happens-at-a-sprint-review-meeting "Sprint Review Meeting")
-* [Sprint Retrospective Meeting](/do-you-know-what-happens-at-a-sprint-retrospective-meeting "Sprint Retrospective Meeting")
-
-:::