Update Rule “agreements-do-you-use-1-or-2-week-sprints/rule” (#8642)

* Update Rule “agreements-do-you-use-1-or-2-week-sprints/rule” * Update rules/agreements-do-you-use-1-or-2-week-sprints/rule.md Co-authored-by: Nick Curran [SSW] <[email protected]> * Update Rule “agreements-do-you-use-1-or-2-week-sprints/rule” --------- Co-authored-by: Nick Curran [SSW] <[email protected]>
SSWConsulting · Jun 3, 2024 · b379522 · b379522
1 parent 25deedf
commit b379522
Showing 1 changed file with 3 additions and 2 deletions.
diff --git a/rules/agreements-do-you-use-1-or-2-week-sprints/rule.md b/rules/agreements-do-you-use-1-or-2-week-sprints/rule.md
@@ -15,9 +15,10 @@ guid: 11cd2bad-7551-4500-a858-2e4743f63aa5
 Depending on how much visibility you need on ongoing costs, you will have to decide whether to use 1 or 2 week development iterations.  
 <!--endintro-->
 
-A 1-week Sprint is for small projects (less than 2 months) or if constant visibility into costs is an important factor, as it gives better feedback to the Product Owner.  
+A 1-week Sprint is for small projects (less than 2 months) or if constant visibility into costs is an important factor, as it gives better feedback to the Product Owner.
+
 ::: greybox
-**Note:** This can be at the cost of increased overheads. 
+**Note:** This can be at the cost of increased overheads.
 :::
 
 A 2-week Sprint is the most common and allows a reasonable amount of work to be done for each release, while minimising Project Management overheads.