From 31c50f7194c518623a80cf4a040106b1c6a72cba Mon Sep 17 00:00:00 2001
From: "Ulysses Maclaren [SSW]"
 <45545178+UlyssesMaclaren@users.noreply.github.com>
Date: Mon, 18 Dec 2023 09:13:43 +1100
Subject: [PATCH] =?UTF-8?q?Update=20Rule=20=E2=80=9Cmeetings-do-you-know-t?=
 =?UTF-8?q?he-agenda-for-the-initial-meeting/rule=E2=80=9D?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 .../rule.md                                                 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/rules/meetings-do-you-know-the-agenda-for-the-initial-meeting/rule.md b/rules/meetings-do-you-know-the-agenda-for-the-initial-meeting/rule.md
index 0eea1bfc448..1e6286a2e73 100644
--- a/rules/meetings-do-you-know-the-agenda-for-the-initial-meeting/rule.md
+++ b/rules/meetings-do-you-know-the-agenda-for-the-initial-meeting/rule.md
@@ -27,7 +27,7 @@ The best way to action this is to ask questions, **listen and take notes**: Clie
 * Introduce your team, explain how our involvement can help them, and whether you have a 'good fit'
 * Explain your rates, including pre-paid
 * Explain the strengths and challenges of a Time and Materials or Fixed Price approach
-* Explain our Scrum development method including the importance of a Specification Review
+* Explain our [Scrum ](https://www.ssw.com.au/rules/8-steps-to-scrum/)development method including the importance of a Specification Review
 * Potentially explain their role as the Product Owner and show a bit of the [Product Owner video](https://www.youtube.com/watch?v=3eljozEWpf8)
 * Ask for the sale: "This project is right up our alley and we'd love to be involved, is there anything stopping you from scheduling a [Specification Review](/do-you-ensure-an-excellent-1st-date-aka-winning-customers-via-a-smaller-specification-review)?" This will focus the mind of the client on the next step
 * Leave a bit of marketing collateral behind. Branded Notepads or USB sticks are ideal.
@@ -43,7 +43,7 @@ The best way to action this is to ask questions, **listen and take notes**: Clie
 * Determine whether scope, time, quality or cost has the highest priority for the client and what level of project management they require. E.g. If a project must be delivered by June 30, a high level of management will be required to ensure enough resources are supplied to achieve this
 * Understand as much as you can about the processes/business rules the system has to manage. Every level of detail you can correctly comprehend and confirm back builds your credibility as a good communicator and supplier!
 * Assess the overall scope of the project, (is it 'small', 'medium' or 'large'?). The attending Architect should start guessing how many man-months this project might be. This information will help you assess how long the Spec Review should be. These initial thoughts should not be shared with the client at this stage as they are most likely incorrect.
-* Determine the client's $ budget and who controls it. E.g. Are you dealing with the business owner or a line manager in a corporation? Do they have a fixed amount to spend? Do they have a time period to spend it in?  
+* Determine the client's $ budget and who controls it. E.g. Are you dealing with the business owner or a line manager in a corporation? Do they have a fixed amount to spend? Do they have a time period to spend it in?\
   Make sure you **ask** them - it's important
 * Find out if this is the sort of project you can do and want to do
-* Qualify the client to make sure they can afford what they want
+* Qualify the client to make sure they can afford what they want
\ No newline at end of file