Update rule.md

rules/3-steps-to-a-pbi/rule.md

@@ -53,18 +53,21 @@ You have a backlog of PBIs (tasks, features, and fixes) which are already priori
 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).
 
 1. From the PBI, create a new branch (so that your work is automatically tagged to the PBI)
-2. On the Kanban Board, move your Task into "In Progress"
+2. On the Sprint board, mark your task as into "In Progress"
 3. Checkout your new branch and code, code, code... (remember to [Red, Green, Refactor](/reply-done-plus-added-a-unit-test))
-4. Open a Pull Request and get another engineer in your team to do an "over the shoulder" check of the code
-5. Record a [Done Video](/record-a-quick-and-dirty-done-video) so you get your ducks in a row for the explanation to the Product Owner, and so they give you earlier feedback.
+4. Open a Pull Request and get another engineer in your team to do an ["over the shoulder"](/over-the-shoulder) check of the code
+5. Record a [Done Video](/record-a-quick-and-dirty-done-video) so you get your ducks in a row for the explanation to the Product Owner, and so they give you earlier feedback
 6. Make changes based on feedback (and then get more feedback)
 7. Check your [Definition of Done](/definition-of-done) and complete the Pull Request!
+8. Deploy your code 🚀
 
 ### 3. Done
 
 This should be easiest part!
 
-1. Close off the PBI by replying 'Done' inside 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)
+1. Reply 'Done' inside 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 now ready to be demonstrated during your Sprint Review!