XS✔ ◾ Geordie88 patch 2 (#6996)

* Updating image

* Update index.md

adding new category to appropriate top category

* Create rules-to-betters-scaled-agile-framework-(SAFe).md

* Create rule.md

1st of 10 rules Uly requested

* Delete do-you-use-SAFe-to-align-multiple-scrum-teams directory

* Create rule.md

* Create rule.md

rule 2 of 10

* Create rule.md

rule 3 of 10

* Create rule.md

rule 4 of 10

* Update rule.md

* Update rule.md

* Create rule.md

rule 5 of 10

* Update rule.md

* Create rule.md

* Create rule.md

7 of 10

* Create rule.md

8/10

* Create rule.md

9/10

* Create rule.md

10/10

* Update rule.md

fixing formatting

* Update rule.md

fix formating

* Update rule.md

fixing formatting

* Update rules-to-betters-scaled-agile-framework-(SAFe).md

* Update rules-to-betters-scaled-agile-framework-(SAFe).md

* Update categories/management/index.md

Co-authored-by: Jayden Alchin [SSW] <[email protected]>

* Update categories/management/rules-to-betters-scaled-agile-framework-(SAFe).md

Co-authored-by: Jayden Alchin [SSW] <[email protected]>

* Delete categories/management/rules-to-betters-scaled-agile-framework-(SAFe).md

renaming file

* Create rules-to-better-scaled-agile-framework-(SAFe).md

changing file name from:

rules-to-betters-scaled-agile-framework-(SAFe).md

to:

rules-to-better-scaled-agile-framework-(SAFe).md

---------

Co-authored-by: Brady Stroud [SSW] <[email protected]>
Co-authored-by: Jayden Alchin [SSW] <[email protected]>

categories/management/index.md

@@ -10,6 +10,7 @@ index:
   - rules-to-better-product-owners
   - rules-to-better-software-consultants-dealing-with-clients
   - rules-to-better-software-consultants-working-in-a-team
+  - rules-to-better-scaled-agile-framework-(SAFe)
   - rules-to-better-software-consultants-happy-clients
   - rules-to-better-crm
   - rules-to-better-accounting

categories/management/rules-to-better-scaled-agile-framework-(SAFe).md

@@ -0,0 +1,19 @@
+---
+type: category
+title: Rules to Better Scaled Agile Framework (SAFe)
+guid: fe191cd3-36bc-4a61-900a-973780bb1cd3
+uri: rules-to-better-scaled-agile-framework-(SAFe)
+experts: https://www.ssw.com.au/people/?skill=Scrum
+consulting: https://www.ssw.com.au/consulting/scrum
+index:
+- do-you-use-SAFe-to-align-multiple-scrum-teams
+- do-you-prioritize-value-streams-over-individual-projects
+- do-you-establish-a-Lean-Agile-mindset-across-all-teams
+- do-you-implement-DevOps-practices-for-continuous-delivery
+- do-you-utilize-a-release-train-engineer-(RTE)-for-synchronization
+- do-you-involve-business-stakeholders-in-program-increment-(PI)-planning
+- do-you-measure-success-using-lean-agile-metrics
+- do-you-regularly-inspect-and-adapt-at-scale
+- do-you-foster-a-culture-of-relentless-improvement
+- do-you-ensure-compliance-and-governance-without-compromising-agility
+---

rules/do-you-ensure-compliance-and-governance-without-compromising-agility/rule.md

@@ -0,0 +1,64 @@
+---
+type: rule
+title: Do you ensure compliance and governance without compromising agility?
+uri: do-you-ensure-compliance-and-governance-without-compromising-agility
+authors:
+  - title: Ulysses Maclaren
+    url: https://ssw.com.au/people/uly
+related:
+redirects:
+created: 2023-10-13
+archivedreason: null
+guid: 684c1885-d097-4e9c-8e68-0998a81ff940
+---
+Your organization is scaling Agile practices, but you're facing a dilemma. On one hand, you have regulatory requirements and governance structures to adhere to; on the other, you don't want to stifle the agility that's driving your success. Striking a balance is crucial.
+
+<!--endintro-->
+
+## What Does It Mean to Balance Compliance and Agility?
+
+Balancing compliance and agility involves creating a governance framework that ensures regulatory compliance while still allowing teams the flexibility to be agile.
+
+### Benefits of Balancing Compliance and Agility
+
+- **Risk Mitigation**: Ensures that the organization meets all legal and regulatory requirements.
+- **Operational Efficiency**: Allows teams to be agile and responsive without being bogged down by excessive controls.
+- **Business Alignment**: Ensures that governance and agility are aligned with business objectives.
+
+::: greybox
+Balance compliance and governance with agility to achieve both operational efficiency and risk mitigation.
+:::
+
+::: good
+Figure: Good Example - A balanced approach allows for agility within the boundaries of compliance and governance.
+:::
+
+## Why Should You Balance Compliance and Agility?
+
+### Regulatory Peace of Mind
+
+Having a balanced approach ensures that you're not sacrificing compliance for the sake of agility, giving you peace of mind in regulatory matters.
+
+::: greybox
+Achieve regulatory peace of mind without compromising agility.
+:::
+
+::: good
+Figure: Good Example - Organizations that balance compliance and agility are less likely to face regulatory issues.
+:::
+
+### Business Agility
+
+By not letting compliance and governance stifle your agility, you can respond more quickly to market changes and opportunities.
+
+::: greybox
+Maintain business agility while adhering to governance requirements.
+:::
+
+::: bad
+Figure: Bad Example - Overemphasis on compliance can make an organization rigid and slow to respond to market changes.
+:::
+
+## Conclusion
+
+Ensuring compliance and governance without compromising agility is a challenging but necessary endeavor. A balanced approach allows organizations to meet regulatory requirements while maintaining the flexibility to adapt and innovate, making it a best practice that should not be overlooked.

rules/do-you-establish-a-Lean-Agile-mindset-across-all-teams/rule.md

@@ -0,0 +1,63 @@
+---
+type: rule
+title: Do you establish a Lean-Agile mindset across all teams?
+guid: fe96d5c6-3817-466c-8882-52d62c5831bd
+uri: do-you-establish-a-Lean-Agile-mindset-across-all-teams
+created: 13/10/2023
+authors:
+  - title: Ulysses Maclaren
+    url: https://ssw.com.au/people/uly
+related:
+
+---
+You've got multiple teams working on various projects, but you notice that they're not all operating with the same level of agility. Some are stuck in old ways of working, leading to inefficiencies and delays. Establishing a Lean-Agile mindset across all teams can solve this inconsistency.
+
+<!--endintro-->
+
+## What is a Lean-Agile Mindset?
+
+A Lean-Agile mindset is a set of beliefs and practices that encourage continuous improvement, efficiency, and delivering value. It combines the principles of Lean thinking with Agile methodologies to create a culture that is both flexible and focused on value delivery.
+
+### Benefits of a Lean-Agile Mindset
+
+- **Efficiency**: Lean principles help in eliminating waste and focusing on value-added activities.
+- **Flexibility**: Agile methodologies allow teams to adapt to changes quickly.
+- **Collaboration**: A Lean-Agile mindset fosters a culture of collaboration and shared responsibility.
+
+::: greybox
+Cultivate a Lean-Agile mindset to improve efficiency, flexibility, and collaboration.
+:::
+
+::: good
+Figure: Good Example - Teams that adopt a Lean-Agile mindset are more efficient and adaptable.
+:::
+
+## Why Should You Establish a Lean-Agile Mindset?
+
+### Consistency Across Teams
+
+When all teams share the same mindset, it's easier to align them towards common goals and objectives.
+
+::: greybox
+Standardize the Lean-Agile mindset for consistent performance across teams.
+:::
+
+::: good
+Figure: Good Example - Consistency in mindset leads to better alignment and easier management.
+:::
+
+### Improved Value Delivery
+
+A Lean-Agile mindset focuses on delivering the most value, both to the customer and the business, ensuring better outcomes.
+
+::: greybox
+Adopt a Lean-Agile mindset for better value delivery.
+:::
+
+::: bad
+Figure: Bad Example - Teams without a Lean-Agile mindset may focus on tasks that don't deliver maximum value.
+:::
+
+## Conclusion
+
+Establishing a Lean-Agile mindset across all teams is not just a philosophical change; it's a practical approach to improving efficiency, adaptability, and value delivery. It ensures that all teams are aligned and moving in the same direction, making it easier to achieve business objectives.

rules/do-you-foster-a-culture-of-relentless-improvement/rule.md

@@ -0,0 +1,64 @@
+---
+type: rule
+title: Do you foster a culture of relentless improvement?
+uri: do-you-foster-a-culture-of-relentless-improvement
+authors:
+  - title: Ulysses Maclaren
+    url: https://ssw.com.au/people/uly
+related:
+redirects:
+created: 2023-10-13
+archivedreason: null
+guid: 3f74f7c0-2db9-4dc6-96a4-dbddca7fa5bd
+---
+Your teams are delivering, and things seem to be going well. However, you notice that the pace of innovation has slowed down, and the teams are stuck in their ways. Fostering a culture of relentless improvement can reignite that innovative spirit.
+
+<!--endintro-->
+
+## What is a Culture of Relentless Improvement?
+
+A culture of relentless improvement is an organizational mindset where teams are continuously looking for ways to improve their processes, products, and overall performance.
+
+### Benefits of Fostering this Culture
+
+- **Innovation**: Encourages teams to think outside the box and innovate.
+- **Efficiency**: Drives the teams to optimize processes for better results.
+- **Employee Satisfaction**: Empowers employees, making them more engaged and satisfied.
+
+::: greybox
+Foster a culture of relentless improvement to drive innovation and efficiency.
+:::
+
+::: good
+Figure: Good Example - Teams in a culture of relentless improvement are always looking for ways to do things better.
+:::
+
+## Why Should You Foster this Culture?
+
+### Competitive Advantage
+
+In today's fast-paced environment, the ability to adapt and improve is a significant competitive advantage.
+
+::: greybox
+Gain a competitive edge by continuously improving.
+:::
+
+::: good
+Figure: Good Example - Companies that foster a culture of improvement are more adaptable and competitive.
+:::
+
+### Long-Term Success
+
+A culture that values improvement is more sustainable and better positioned for long-term success.
+
+::: greybox
+Invest in long-term success through continuous improvement.
+:::
+
+::: bad
+Figure: Bad Example - Organizations that don't foster a culture of improvement may find it difficult to adapt to market changes.
+:::
+
+## Conclusion
+
+Fostering a culture of relentless improvement is not just a one-time initiative but an ongoing commitment. It drives innovation, efficiency, and employee satisfaction, making it essential for any organization aiming for long-term success.

rules/do-you-implement-DevOps-practices-for-continuous-delivery/rule.md

@@ -0,0 +1,64 @@
+---
+type: rule
+title: Do you implement DevOps practices for continuous delivery?
+uri: do-you-implement-DevOps-practices-for-continuous-delivery
+authors:
+  - title: Ulysses Maclaren
+    url: https://ssw.com.au/people/uly
+related:
+redirects:
+created: 2023-10-13
+archivedreason: null
+guid: 605b433e-d6ef-474a-80ef-06e2ac8cd425
+---
+You've got your development and operations teams working in silos, leading to delays in deployments and frequent bottlenecks. The lack of a streamlined process affects your ability to deliver features and fixes quickly. Implementing DevOps practices for continuous delivery can be the solution to these challenges.
+
+<!--endintro-->
+
+## What is DevOps?
+
+DevOps is a set of practices that combines software development (Dev) and IT operations (Ops) to shorten the system development life cycle and provide continuous delivery.
+
+### Benefits of Implementing DevOps
+
+- **Speed**: DevOps enables you to deliver at a faster pace, improving your time to market.
+- **Reliability**: Automated testing and continuous monitoring ensure that the changes are reliable.
+- **Collaboration**: DevOps practices encourage greater communication and collaboration between teams.
+
+::: greybox
+Implement DevOps practices to streamline development and operations.
+:::
+
+::: good
+Figure: Good Example - DevOps practices enable faster, more reliable deployments.
+:::
+
+## Why Should You Implement DevOps?
+
+### Seamless Integration
+
+DevOps practices allow for seamless integration between development and operations, reducing the time from development to deployment.
+
+::: greybox
+Adopt DevOps for a seamless integration between development and operations.
+:::
+
+::: good
+Figure: Good Example - DevOps practices reduce the time from code commit to deployment.
+:::
+
+### Risk Mitigation
+
+Continuous testing and monitoring as part of the DevOps practices help in early identification of issues, reducing the risks associated with deployments.
+
+::: greybox
+Utilize DevOps for continuous testing and risk mitigation.
+:::
+
+::: bad
+Figure: Bad Example - Lack of DevOps practices can lead to risky deployments and frequent rollbacks.
+:::
+
+## Conclusion
+
+Implementing DevOps practices for continuous delivery is not just a technical change; it's a cultural shift that brings development and operations teams together. It enables faster, more reliable, and safer deployments, making your entire software development life cycle more efficient.

rules/do-you-involve-business-stakeholders-in-program-increment-(PI)-planning/rule.md

@@ -0,0 +1,64 @@
+---
+type: rule
+title: Do you involve business stakeholders in Program Increment (PI) planning?
+uri: do-you-involve-business-stakeholders-in-program-increment-(PI)-planning
+authors:
+  - title: Ulysses Maclaren
+    url: https://ssw.com.au/people/uly
+related:
+redirects:
+created: 2023-10-13
+archivedreason: null
+guid: c7d58999-e7af-4e2d-89f7-38f693a9fbaa
+---
+You're about to kick off a new Program Increment (PI), and the development teams are all set. However, you notice that the business stakeholders are not actively involved, leading to a disconnect between what's being built and what the business actually needs. Involving business stakeholders in PI planning can bridge this gap.
+
+<!--endintro-->
+
+## What is Program Increment (PI) Planning?
+
+Program Increment (PI) planning is a routine event in the Scaled Agile Framework (SAFe) where all members of an Agile Release Train (ART) come together to understand the priorities for the upcoming PI, discuss technical considerations, and create plans.
+
+### Benefits of Involving Business Stakeholders
+
+- **Alignment**: Ensures that the development work is aligned with business objectives.
+- **Clarity**: Provides clarity on business priorities and requirements.
+- **Feedback Loop**: Creates an immediate feedback loop between development teams and business stakeholders.
+
+::: greybox
+Involve business stakeholders in PI planning to align development work with business objectives.
+:::
+
+::: good
+Figure: Good Example - Involving business stakeholders in PI planning ensures that everyone is aligned and working toward the same goals.
+:::
+
+## Why Should You Involve Business Stakeholders?
+
+### Better Decision-Making
+
+When business stakeholders are involved, it leads to better decision-making as they bring the business context and priorities into the planning process.
+
+::: greybox
+Include business stakeholders for informed decision-making.
+:::
+
+::: good
+Figure: Good Example - Business stakeholders can provide valuable insights that lead to better decisions during PI planning.
+:::
+
+### Risk Mitigation
+
+Involving business stakeholders early in the planning process helps in identifying and mitigating risks related to market needs, compliance, and other business-related factors.
+
+::: greybox
+Engage business stakeholders for early risk identification and mitigation.
+:::
+
+::: bad
+Figure: Bad Example - Excluding business stakeholders can result in overlooking important business risks and priorities.
+:::
+
+## Conclusion
+
+Involving business stakeholders in Program Increment (PI) planning is crucial for ensuring that the development work is aligned with the business objectives. It not only improves decision-making but also helps in risk mitigation, making it a practice that should not be overlooked.