TinaCMS content update

Co-authored-by: Jake Bayliss [SSW] <jakebayliss@ssw.com.au>

Author: jakebayliss

public/uploads/rules/3-steps-to-a-pbi/rule.mdx

@@ -1,50 +1,52 @@
 ---
-archivedreason: null
-authors:
-- title: Adam Cogan
-  url: https://ssw.com.au/people/adam-cogan
-- title: Matt Wicks
-  url: https://ssw.com.au/people/matt-wicks
-- title: Piers Sinclair
-  url: https://ssw.com.au/people/piers-sinclair
-- title: Brady Stroud
-  url: https://ssw.com.au/people/brady-stroud
+type: rule
+title: Do you know the 3 steps to completing a PBI?
+uri: 3-steps-to-a-pbi
 categories:
-- category: categories/project-delivery/rules-to-better-scrum-using-azure-devops.mdx
-created: 2023-08-23 17:26:23+00:00
-createdBy: Geordie Robinson [SSW]
-createdByEmail: 97079655+Geordie88@users.noreply.github.com
+  - category: categories/project-delivery/rules-to-better-scrum-using-azure-devops.mdx
+authors:
+  - title: Adam Cogan
+    url: 'https://ssw.com.au/people/adam-cogan'
+  - title: Matt Wicks
+    url: 'https://ssw.com.au/people/matt-wicks'
+  - title: Piers Sinclair
+    url: 'https://ssw.com.au/people/piers-sinclair'
+  - title: Brady Stroud
+    url: 'https://ssw.com.au/people/brady-stroud'
+related:
+  - rule: public/uploads/rules/turn-emails-into-pbis/rule.mdx
+  - rule: public/uploads/rules/have-a-definition-of-ready/rule.mdx
+  - rule: public/uploads/rules/acceptance-criteria/rule.mdx
+  - rule: public/uploads/rules/react-to-reviewed-pbis/rule.mdx
+  - rule: public/uploads/rules/write-a-good-pull-request/rule.mdx
+  - rule: public/uploads/rules/done-video/rule.mdx
+  - rule: public/uploads/rules/definition-of-done/rule.mdx
+  - rule: public/uploads/rules/close-pbis-with-context/rule.mdx
+  - rule: public/uploads/rules/8-steps-to-scrum/rule.mdx
+redirects:
+  - do-you-know-the-3-steps-to-completing-a-pbi
+  - do-you-know-the-3-steps-to-a-pbi
 guid: 1de9df77-9b69-4242-b648-e08e5980e9a6
-isArchived: false
-lastUpdated: 2025-06-10 00:27:36+00:00
-lastUpdatedBy: Tiago Araújo [SSW]
+seoDescription: >-
+  Master the 3 essential steps of PBI management with SSW's expert guide. From
+  readiness to coding and finalization, streamline your Agile processes for
+  maximum efficiency. Learn more and enhance your project management skills
+  today.
+created: 2023-08-23T17:26:23.000Z
+createdBy: 'Geordie Robinson [SSW]'
+createdByEmail: 97079655+Geordie88@users.noreply.github.com
+lastUpdated: 2025-06-10T00:27:36.000Z
+lastUpdatedBy: 'Tiago Araújo [SSW]'
 lastUpdatedByEmail: tiagov8@gmail.com
-redirects:
-- do-you-know-the-3-steps-to-completing-a-pbi
-- do-you-know-the-3-steps-to-a-pbi
-related:
-- rule: public/uploads/rules/turn-emails-into-pbis/rule.mdx
-- rule: public/uploads/rules/have-a-definition-of-ready/rule.mdx
-- rule: public/uploads/rules/acceptance-criteria/rule.mdx
-- rule: public/uploads/rules/react-to-reviewed-pbis/rule.mdx
-- rule: public/uploads/rules/write-a-good-pull-request/rule.mdx
-- rule: public/uploads/rules/done-video/rule.mdx
-- rule: public/uploads/rules/definition-of-done/rule.mdx
-- rule: public/uploads/rules/close-pbis-with-context/rule.mdx
-- rule: public/uploads/rules/8-steps-to-scrum/rule.mdx
-seoDescription: Master the 3 essential steps of PBI management with SSW's expert guide.
-  From readiness to coding and finalization, streamline your Agile processes for maximum
-  efficiency. Learn more and enhance your project management skills today.
-title: Do you know the 3 steps to completing a PBI?
-type: rule
-uri: 3-steps-to-a-pbi
+isArchived: false
+archivedreason: null
 ---
 
 <introEmbed
   body={<>
-A PBI (Product Backlog Item) is a term commonly used in Agile project management and software development to represent a unit of work. It refers to an item in the Product Backlog, which is a prioritized list of features, enhancements, or fixes to be addressed in a project.
-
-Before a PBI is worked on it should be added to the current Sprint Backlog during [Sprint Planning](/what-happens-at-a-sprint-planning-meeting). If your PBI doesn't exist, or is in an email then you need to [turn it into a PBI](/turn-emails-into-pbis) to be prioritized in Sprint Planning.
+    A PBI (Product Backlog Item) is a term commonly used in Agile project management and software development to represent a unit of work. It refers to an item in the Product Backlog, which is a prioritized list of features, enhancements, or fixes to be addressed in a project.
+    
+    Before a PBI is worked on it should be added to the current Sprint Backlog during [Sprint Planning](/what-happens-at-a-sprint-planning-meeting). If your PBI doesn't exist, or is in an email then you need to [turn it into a PBI](/turn-emails-into-pbis) to be prioritized in Sprint Planning.
   </>}
 />
 
@@ -53,33 +55,22 @@ Before a PBI is worked on it should be added to the current Sprint Backlog durin
   body={<>
     **Tip:** After reviewing a PBI, don’t forget to [react with 👍 or 👎 to show it’s been validated](/react-to-reviewed-pbis).
   </>}
-  figureEmbed={{
-    preset: "default",
-    figure: "XXX",
-    shouldDisplay: false
-  }}
+  figureEmbed={{ preset: "default", figure: "XXX", shouldDisplay: false }}
 />
 
-
-
 <asideEmbed
   variant="greybox"
   body={<>
+    ### Use YakShaver and make it even easier
 
-### Use YakShaver and make it even easier
-
-You can save time by not writing PBIs manually.
-
-With [YakShaver](https://yakshaver.ai), simply record your message and let the AI do the rest. YakShaver writes a clear and complete PBI, GitHub Issue, or even an email (for projects without a backlog), mentioning the right people and assigning it to the correct team.
+    You can save time by not writing PBIs manually.
+    
+    With [YakShaver](https://yakshaver.ai), simply record your message and let the AI do the rest. YakShaver writes a clear and complete PBI, GitHub Issue, or even an email (for projects without a backlog), mentioning the right people and assigning it to the correct team.
   </>}
-  figureEmbed={{
-    preset: "default",
-    figure: "XXX",
-    shouldDisplay: false
-  }}
+  figureEmbed={{ preset: "default", figure: "XXX", shouldDisplay: false }}
 />
 
-Jakes Test Change
+Jakes Test Change #2
 
 Once a PBI is in the Sprint Backlog, it's lifecycle can be broken down into 3 steps:
 
@@ -91,20 +82,19 @@ You have a Sprint Backlog of PBIs (tasks, features, and fixes) which are already
 2. Double check the [Definition of Ready](/have-a-definition-of-ready)
 3. Break the PBI into tasks (optional)
 
-
 <imageEmbed
   alt="Image"
   size="large"
   showBorder={false}
-  figureEmbed={ {
+  figureEmbed={{
     preset: "default",
-    figure: "\"Testing Task\" added to a PBI. This is the board the team will use for 90% of the Sprint so that testing is visible to everyone",
+    figure:
+      '"Testing Task" added to a PBI. This is the board the team will use for 90% of the Sprint so that testing is visible to everyone',
     shouldDisplay: true
-  } }
+  }}
   src="/uploads/rules/3-steps-to-a-pbi/Testing-task.png"
 />
 
-
 ## 2. Time to Code
 
 This step depends on the complexity and nature of the task, especially if the PBI involves intricate coding or extensive testing to meet the defined [Acceptance Criteria](/acceptance-criteria).
@@ -127,7 +117,6 @@ This should be the easiest part!
 2. Reply 'done' to the PBI and also in the email thread, as per [when to send a 'done' email in Scrum](/done-do-you-know-when-to-send-a-done-email-in-scrum)
 
    **Note:** Remember to [close PBIs, tasks and goals with context](/close-pbis-with-context)
-
 3. Close the PBI
 
 Congrats, your PBI is ready to be demonstrated during your Sprint Review!
@@ -136,13 +125,12 @@ Congrats, your PBI is ready to be demonstrated during your Sprint Review!
   alt="Image"
   size="large"
   showBorder={false}
-  figureEmbed={ {
+  figureEmbed={{
     preset: "goodExample",
     figure: "The important steps in a PBI lifecycle.",
     shouldDisplay: true
-  } }
+  }}
   src="/uploads/rules/3-steps-to-a-pbi/3-steps-to-a-pbi.jpg"
 />
 
-
 Print out the [SSW 3 Steps to a PBI PDF](/uploads/rules/3-steps-to-a-pbi/3-steps-to-a-pbi.pdf) and put it on your "War Room" wall.