From 1cdeb282d77dd6a73036f5aaa47f8e6762f9812d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tiago=20Ara=C3=BAjo=20=5BSSW=5D?= Date: Tue, 23 Apr 2024 09:39:59 -0700 Subject: [PATCH 01/10] Adding related rules --- rules/work-in-order-of-importance-aka-priorities/rule.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/rules/work-in-order-of-importance-aka-priorities/rule.md b/rules/work-in-order-of-importance-aka-priorities/rule.md index 6efadc65788..6c70df2b7fb 100644 --- a/rules/work-in-order-of-importance-aka-priorities/rule.md +++ b/rules/work-in-order-of-importance-aka-priorities/rule.md @@ -7,7 +7,8 @@ authors: url: https://ssw.com.au/people/adam-cogan - title: Ulysses Maclaren url: https://ssw.com.au/people/ulysses-maclaren -related: [] +related: + - meaningful-pbi-titles redirects: - do-you-complete-work-in-order-of-importance-(aka-priorities) - priorities-do-you-complete-work-in-order-of-importance-aka-priorities From afd4e44b978f5c3b285f9d4e8a9d99abd6d971ba Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tiago=20Ara=C3=BAjo=20=5BSSW=5D?= Date: Tue, 23 Apr 2024 09:41:23 -0700 Subject: [PATCH 02/10] Update rule.md --- rules/meaningful-pbi-titles/rule.md | 1 + 1 file changed, 1 insertion(+) diff --git a/rules/meaningful-pbi-titles/rule.md b/rules/meaningful-pbi-titles/rule.md index b4cb7241316..4c67e497578 100644 --- a/rules/meaningful-pbi-titles/rule.md +++ b/rules/meaningful-pbi-titles/rule.md @@ -7,6 +7,7 @@ authors: url: https://ssw.com.au/people/luke-cook related: - good-email-subject + - work-in-order-of-importance-aka-priorities redirects: - do-you-use-meaningful-pbi-titles created: 2022-12-08T07:23:54.000Z From a96cb26925c7cd0220d83c061211dc0796ced4ec Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Tue, 23 Apr 2024 16:42:20 +0000 Subject: [PATCH 03/10] Auto-fix Markdown files --- rules/meaningful-pbi-titles/rule.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/rules/meaningful-pbi-titles/rule.md b/rules/meaningful-pbi-titles/rule.md index 4c67e497578..40a1ae44f7b 100644 --- a/rules/meaningful-pbi-titles/rule.md +++ b/rules/meaningful-pbi-titles/rule.md @@ -55,13 +55,12 @@ Figure: Good example - "Fire" emoji to bring attention to the PBI's importance, ### Do -βœ… Be specific (e.g. "{{Area}} | {{behaviour}}"). See our rule to [order of instructions](/use-the-right-order-of-instructions) +βœ… Be specific (e.g. "{{Area}} | {{behaviour}}"). See our rule to [order of instructions](/use-the-right-order-of-instructions) βœ… Prefix the area/form βœ… Identify its urgency (e.g. πŸ”₯) βœ… Identify the bugs (e.g. "Bug" and/or πŸ›). Bugs are special case - they should have [greater visibiliy](/management-do-you-fix-bugs-first) βœ… Use emojis. See our rule on [emojis in Scrum](/which-emojis-to-use-in-scrum) - ### Good PBI titles examples Using this structure: **{{ EMOJI FOR PBI TYPE }} {{ BUSINESS AREA TOUCHED }} | {{ SHORT DESCRIPTION }}** @@ -101,19 +100,19 @@ Other examples: ::: greybox πŸ› Invoices | Invoice totals are rounded incorrectly -βš’οΈ Infrastructure | Implement staging deployment pipeline +βš’οΈ Infrastructure | Implement staging deployment pipeline -✨ Clients page | Add create/edit client fieldsΒ  +✨ Clients page | Add create/edit client fields ::: Great titles are also important on [Pull Requests](/write-a-good-pull-request/#1-write-a-concise-and-self-explanatory-title), and [email subjects](/good-email-subject). ::: info -**Emojis** +**Emojis** Love them or hate them, emojis have become a staple in the development world. As the old saying goes... _"a picture is worth a thousand words"_. You can use emojis (responsibly!) to categorize PBIs/Issues/PRs/Emails, as well as bring attention to important items in a way that is easily interpreted by other people. -Regardless of whether or not you choose to adopt the emoji language, you should always be mindful of the title's text. +Regardless of whether or not you choose to adopt the emoji language, you should always be mindful of the title's text. Always ask yourself: _"Can a developer (or Product Owner) interpret the task and its importance without needing to dive into the details?"_ ::: From 8dae94eaf366deffeda11c88adbdbb2a2f2ec60c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tiago=20Ara=C3=BAjo=20=5BSSW=5D?= Date: Tue, 23 Apr 2024 09:47:46 -0700 Subject: [PATCH 04/10] Update rule.md --- rules/meaningful-pbi-titles/rule.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/rules/meaningful-pbi-titles/rule.md b/rules/meaningful-pbi-titles/rule.md index 40a1ae44f7b..41e050ac4d6 100644 --- a/rules/meaningful-pbi-titles/rule.md +++ b/rules/meaningful-pbi-titles/rule.md @@ -40,11 +40,11 @@ Figure: Bad example – What bug? How important is this? ::: ::: greybox -πŸ”₯ πŸ› BUG | Menu disappears on mobile devices +❗️ IMPORTANT πŸ› BUG | Menu disappears on mobile devices ::: ::: good -Figure: Good example - "Fire" emoji to bring attention to the PBI's importance, "Bug" emoji to indicate the PBI type, and a clear description of the issue +Figure: Good example - "Important" emoji and text to bring attention to the PBI's importance, "Bug" emoji and text to indicate the PBI type, with a clear description of the issue ::: ### Don't @@ -55,10 +55,9 @@ Figure: Good example - "Fire" emoji to bring attention to the PBI's importance, ### Do -βœ… Be specific (e.g. "{{Area}} | {{behaviour}}"). See our rule to [order of instructions](/use-the-right-order-of-instructions) -βœ… Prefix the area/form -βœ… Identify its urgency (e.g. πŸ”₯) -βœ… Identify the bugs (e.g. "Bug" and/or πŸ›). Bugs are special case - they should have [greater visibiliy](/management-do-you-fix-bugs-first) +βœ… Be specific (e.g. "{{ AREA }} | {{ BEHAVIOUR }}"). See our rule to [order of instructions](/use-the-right-order-of-instructions) +βœ… Prefix - Identify its urgency (e.g. ❗️ IMPORTANT) +βœ… Prefix - Identify the area (e.g. πŸ› BUG). Bugs are special case - they should have [greater visibiliy](/management-do-you-fix-bugs-first) βœ… Use emojis. See our rule on [emojis in Scrum](/which-emojis-to-use-in-scrum) ### Good PBI titles examples @@ -92,7 +91,7 @@ DevOps/Infra: Urgent tasks: ::: greybox -πŸ”₯πŸ›πŸ‘·β€β™‚οΈ SysAdmin | Northwind app inaccessible through company VPN +❗️ IMPORTANT πŸ›πŸ‘·β€β™‚οΈ SysAdmin | Northwind app inaccessible through company VPN ::: Other examples: From 0560c93a95cd87012baa8a1cdf4ce011026a3a9f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tiago=20Ara=C3=BAjo=20=5BSSW=5D?= Date: Tue, 23 Apr 2024 09:59:45 -0700 Subject: [PATCH 05/10] Update rule.md --- .../rule.md | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/rules/work-in-order-of-importance-aka-priorities/rule.md b/rules/work-in-order-of-importance-aka-priorities/rule.md index 6c70df2b7fb..dbe17f5cc92 100644 --- a/rules/work-in-order-of-importance-aka-priorities/rule.md +++ b/rules/work-in-order-of-importance-aka-priorities/rule.md @@ -28,17 +28,25 @@ The word **"Urgent"** is more important than the word **"Important"** ### This is the order which you should work -1. **Urgent emails & PBIs/tasks** – If you see the keyword "URGENT" (or the warning ⚠️ emoji) in the subject/title/body, it automatically becomes the top priority and is to be resolved immediately. +1. **Urgent/Important emails & PBIs/tasks** – Make them visible in the Backlog, communicate, and action + If you see the keyword "URGENT" (or ⚠️ emoji) in the subject/title/body, it automatically becomes the **top priority** and is to be resolved immediately. - E.g. "URGENT ⚠️ the website is down" + E.g. "⚠️ URGENT - The website is down" + + If you see the keyword "IMPORTANT" (or ❗ emoji), that PBI should to be treated as **high priority** and is to be resolved ASAP. + + E.g. "❗️ IMPORTANT - Broken link" ::: warning - Immediately call your Product Owner and Scrum Master to let them know that this urgent issue has arisen, and that you will be working on it instead of other items in the Sprint. + Immediately call your Product Owner and Scrum Master when "URGENT/IMPORTANT" issues arisen, and inform them you will be working on it instead of other items in the Sprint. + ::: + + ::: info + **Note:** The fire πŸ”₯ emoji is no longer used because it can be misinterpreted as a good thing or a 'hot topic' ::: - Note: the fireπŸ”₯emoji is no longer used because it can be misinterpreted as a good thing or a 'hot topic' 3. **Emails about [timesheets](/do-you-know-how-important-timesheets-are)** or invoicing issues -4. **Your calendar** - [keep your calendar up-to-date,](/calendar-does-your-calendar-always-accurately-show-where-you-are)so people know where you are +4. **Your calendar** - [keep your calendar up-to-date,](/calendar-does-your-calendar-always-accurately-show-where-you-are) so people know where you are 5. **Your existing clients** - Planned client work and client administration (preferably working on a [Sprint Backlog](/do-you-know-how-to-manage-the-product-backlog) and doing [Daily Scrums](/methodology-daily-scrums)) 6. **Other client work** - Ask others if you can help with their client work 7. **Prospective clients** - Project management, answering questions and setting up meetings @@ -50,6 +58,7 @@ The word **"Urgent"** is more important than the word **"Important"** 4. Help others get their important emails to 0 5. Get your inbox to 0 6. Ping others to see if they need help completing their Sprint + 9. Phew... Done... **Tips:** From 6647d0ce25e7a28a2b4414013ef7dca43543cd7d Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Tue, 23 Apr 2024 17:00:43 +0000 Subject: [PATCH 06/10] Auto-fix Markdown files --- rules/work-in-order-of-importance-aka-priorities/rule.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rules/work-in-order-of-importance-aka-priorities/rule.md b/rules/work-in-order-of-importance-aka-priorities/rule.md index dbe17f5cc92..f471d422233 100644 --- a/rules/work-in-order-of-importance-aka-priorities/rule.md +++ b/rules/work-in-order-of-importance-aka-priorities/rule.md @@ -29,11 +29,11 @@ The word **"Urgent"** is more important than the word **"Important"** ### This is the order which you should work 1. **Urgent/Important emails & PBIs/tasks** – Make them visible in the Backlog, communicate, and action - If you see the keyword "URGENT" (or ⚠️ emoji) in the subject/title/body, it automatically becomes the **top priority** and is to be resolved immediately. + If you see the keyword "URGENT" (or ⚠️ emoji) in the subject/title/body, it automatically becomes the **top priority** and is to be resolved immediately. E.g. "⚠️ URGENT - The website is down" - If you see the keyword "IMPORTANT" (or ❗ emoji), that PBI should to be treated as **high priority** and is to be resolved ASAP. + If you see the keyword "IMPORTANT" (or ❗ emoji), that PBI should to be treated as **high priority** and is to be resolved ASAP. E.g. "❗️ IMPORTANT - Broken link" From ea0589d16e7148b47802c3a6f93bb429f1f68fc9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tiago=20Ara=C3=BAjo=20=5BSSW=5D?= Date: Tue, 23 Apr 2024 10:01:05 -0700 Subject: [PATCH 07/10] Update rule.md --- rules/work-in-order-of-importance-aka-priorities/rule.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/rules/work-in-order-of-importance-aka-priorities/rule.md b/rules/work-in-order-of-importance-aka-priorities/rule.md index f471d422233..01fe3713722 100644 --- a/rules/work-in-order-of-importance-aka-priorities/rule.md +++ b/rules/work-in-order-of-importance-aka-priorities/rule.md @@ -29,12 +29,10 @@ The word **"Urgent"** is more important than the word **"Important"** ### This is the order which you should work 1. **Urgent/Important emails & PBIs/tasks** – Make them visible in the Backlog, communicate, and action - If you see the keyword "URGENT" (or ⚠️ emoji) in the subject/title/body, it automatically becomes the **top priority** and is to be resolved immediately. - + If you see the keyword "URGENT" (or ⚠️ emoji) in the subject/title/body, it automatically becomes the **top priority** and is to be resolved immediately. E.g. "⚠️ URGENT - The website is down" - If you see the keyword "IMPORTANT" (or ❗ emoji), that PBI should to be treated as **high priority** and is to be resolved ASAP. - + If you see the keyword "IMPORTANT" (or ❗ emoji), that PBI should to be treated as **high priority** and is to be resolved ASAP. E.g. "❗️ IMPORTANT - Broken link" ::: warning From e95bd4b9b4d11455edecbd11a706c4898461800b Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Tue, 23 Apr 2024 17:02:23 +0000 Subject: [PATCH 08/10] Auto-fix Markdown files --- rules/work-in-order-of-importance-aka-priorities/rule.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rules/work-in-order-of-importance-aka-priorities/rule.md b/rules/work-in-order-of-importance-aka-priorities/rule.md index 01fe3713722..e9f9de40473 100644 --- a/rules/work-in-order-of-importance-aka-priorities/rule.md +++ b/rules/work-in-order-of-importance-aka-priorities/rule.md @@ -29,10 +29,10 @@ The word **"Urgent"** is more important than the word **"Important"** ### This is the order which you should work 1. **Urgent/Important emails & PBIs/tasks** – Make them visible in the Backlog, communicate, and action - If you see the keyword "URGENT" (or ⚠️ emoji) in the subject/title/body, it automatically becomes the **top priority** and is to be resolved immediately. + If you see the keyword "URGENT" (or ⚠️ emoji) in the subject/title/body, it automatically becomes the **top priority** and is to be resolved immediately. E.g. "⚠️ URGENT - The website is down" - If you see the keyword "IMPORTANT" (or ❗ emoji), that PBI should to be treated as **high priority** and is to be resolved ASAP. + If you see the keyword "IMPORTANT" (or ❗ emoji), that PBI should to be treated as **high priority** and is to be resolved ASAP. E.g. "❗️ IMPORTANT - Broken link" ::: warning From 5efa3dd296dda2a37f9a2b7b1d1f83e1db1b700c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tiago=20Ara=C3=BAjo=20=5BSSW=5D?= Date: Tue, 23 Apr 2024 20:59:56 -0700 Subject: [PATCH 09/10] Change wording as per @piers-sinclair --- rules/work-in-order-of-importance-aka-priorities/rule.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules/work-in-order-of-importance-aka-priorities/rule.md b/rules/work-in-order-of-importance-aka-priorities/rule.md index e9f9de40473..46814dd171d 100644 --- a/rules/work-in-order-of-importance-aka-priorities/rule.md +++ b/rules/work-in-order-of-importance-aka-priorities/rule.md @@ -36,7 +36,7 @@ The word **"Urgent"** is more important than the word **"Important"** E.g. "❗️ IMPORTANT - Broken link" ::: warning - Immediately call your Product Owner and Scrum Master when "URGENT/IMPORTANT" issues arisen, and inform them you will be working on it instead of other items in the Sprint. + Call your Product Owner and Scrum Master when "URGENT/IMPORTANT" issues arisen, and inform them you will be working on it (immediately if "URGENT") instead of other items in the Sprint. ::: ::: info From f2e7954baa59c1dbbe0854a260ac7c642fa0bfa7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tiago=20Ara=C3=BAjo=20=5BSSW=5D?= Date: Tue, 23 Apr 2024 21:02:57 -0700 Subject: [PATCH 10/10] changed from "area" to "type" --- rules/meaningful-pbi-titles/rule.md | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/rules/meaningful-pbi-titles/rule.md b/rules/meaningful-pbi-titles/rule.md index 41e050ac4d6..6ad554e2fe0 100644 --- a/rules/meaningful-pbi-titles/rule.md +++ b/rules/meaningful-pbi-titles/rule.md @@ -47,18 +47,19 @@ Figure: Bad example – What bug? How important is this? Figure: Good example - "Important" emoji and text to bring attention to the PBI's importance, "Bug" emoji and text to indicate the PBI type, with a clear description of the issue ::: -### Don't +### ❌ Don't -❌ Be generic (e.g. "Fix bug in site") -❌ Write a novel in the title -❌ Ignore the importance of urgent PBIs +* Be generic (e.g. "Fix bug in site") +* Write a novel in the title +* Ignore the importance of urgent PBIs -### Do +### βœ… Do -βœ… Be specific (e.g. "{{ AREA }} | {{ BEHAVIOUR }}"). See our rule to [order of instructions](/use-the-right-order-of-instructions) -βœ… Prefix - Identify its urgency (e.g. ❗️ IMPORTANT) -βœ… Prefix - Identify the area (e.g. πŸ› BUG). Bugs are special case - they should have [greater visibiliy](/management-do-you-fix-bugs-first) -βœ… Use emojis. See our rule on [emojis in Scrum](/which-emojis-to-use-in-scrum) +* Be specific (e.g. "{{ AREA }} | {{ BEHAVIOUR }}"). See our rule to [order of instructions](/use-the-right-order-of-instructions) +* Prefix - Identify its urgency (e.g. ❗️ IMPORTANT) +* Prefix - Identify the type (e.g. πŸ› BUG) + **Note:** Bugs are special case - they should have [greater visibiliy](/management-do-you-fix-bugs-first) +* Use emojis. See our rule on [emojis in Scrum](/which-emojis-to-use-in-scrum) ### Good PBI titles examples