No items in {{include.pageStatus}} currently...
+ {% else %}
+
{% for item in videos %}
-
+
@@ -12,8 +12,7 @@
Recommended Videos
{{item.title}}
-
-
+
{% endfor %}
diff --git a/src/_includes/sidebar-collection.html b/src/_includes/sidebar-collection.html
index d319c6e..c732d83 100644
--- a/src/_includes/sidebar-collection.html
+++ b/src/_includes/sidebar-collection.html
@@ -1,51 +1,30 @@
{% assign collection = site.collections | where: "label", include.collection | first %}
- {{ include.collection | capitalize_all }}
+ {{ include.collection | capitalize_all }}
+
+
{% assign overview = site.pages | where: "pageType", "index" | where: "indexForCollection", include.collection | first %}
{% if overview != null %}
- Overview
+ -
+ Overview
+
{% endif %}
{% if collection != null %}
{% assign items = collection.docs | where: "category", null | where: "pageStatus", "published" | sort: "importance" | reverse %}
-
-
- {% for item in items %}
- {% if item.pageStatus != "draft" %}
- -
-
- {{ item.title }}
-
-
- {% endif %}
- {% endfor %}
- {% assign items = collection.docs | except: "pageStatus", "published" | where: "category", null | sort: "importance" | reverse %}
+ {% assign items = collection.docs | where: "pageStatus", "published" | where: "category", null | sort: "importance" | reverse %}
{% if items != empty %}
- -
-
- Preview Content
-
-
-
{% endif %}
-
{% else %}
- No items in collection
+ - No items in collection
{% endif %}
+
+
diff --git a/src/_includes/sidebar-pagetype.html b/src/_includes/sidebar-pagetype.html
index 697f8a2..e38b33b 100644
--- a/src/_includes/sidebar-pagetype.html
+++ b/src/_includes/sidebar-pagetype.html
@@ -1,19 +1,41 @@
{% assign pages = site.pages | where: "pageType", include.pageType | where: "pageStatus", "published" | sort: "importance" | reverse %}
-{{ include.title | capitalize_all }}
-
- {% for page in pages %}
- -
-
- {{ page.title }}
-
-
- {% endfor %}
+
+
+
+ {{ include.title | capitalize_all }}
+
+
+
+
+ {% for page in pages %}
+ -
+
+ {{ page.title }}
+
+
+ {% endfor %}
+ {% if collection != null %}
+ {% assign items = collection.docs | where: "category", null | where: "pageStatus", "published" | sort: "importance" | reverse %}
+ {% assign items = collection.docs | where: "pageStatus", "published" | where: "category", null | sort: "importance" | reverse %}
+ {% if items != empty %}
+ {% for item in items %}
+ -
+ {{ item.title }}
+
+ {% endfor %}
+ {% endif %}
+ {% else %}
+ - No items in collection
+ {% endif %}
{% assign pages = site.pages | where: "pageType", include.pageType | except: "pageStatus", "published" | sort: "importance" | reverse %}
{% if pages != empty %}
-
- Preview Content
+ Draft
{% for page in pages %}
@@ -24,5 +46,8 @@
{% endif %}
-
-
+
+
+
+
+
diff --git a/src/assets/images/nexus-framework.png b/src/assets/images/nexus-framework.png
new file mode 100644
index 0000000..1e06992
Binary files /dev/null and b/src/assets/images/nexus-framework.png differ
diff --git a/src/collections/_anti-patterns/backlog-items-too-big.md b/src/collections/_anti-patterns/backlog-items-too-big.md
index b548353..9fc877f 100644
--- a/src/collections/_anti-patterns/backlog-items-too-big.md
+++ b/src/collections/_anti-patterns/backlog-items-too-big.md
@@ -4,6 +4,8 @@ layout: default
toc: true
pdf: true
pageType: anti-pattern
+catagorys:
+ - scrum
pageStatus: draft
discussionId:
references:
diff --git a/src/collections/_faq/is-having-a-definition-of-ready-a-good-idea.md b/src/collections/_faq/is-having-a-definition-of-ready-a-good-idea.md
new file mode 100644
index 0000000..7f4384b
--- /dev/null
+++ b/src/collections/_faq/is-having-a-definition-of-ready-a-good-idea.md
@@ -0,0 +1,44 @@
+---
+title: Does having a definition of ready a good idea?
+layout: default
+toc: true
+pdf: true
+pageType: faq
+pageStatus: published
+discussionId:
+references:
+ - title: Scrum Glossary - Scrum.org
+ url: https://www.scrum.org/resources/scrum-glossary
+recommendedContent:
+ - collection: guides
+ path: _guides/scrum-guide.md
+ - collection: practices
+ path: _practices/definition-of-ready-dor.md
+---
+
+## Question
+
+Does having a definition of ready a good idea?
+
+## Short Answer
+
+No. Having a definition of ready can lead to gating of work for a team.
+
+## Long Answer
+
+In the Scrum Guide there is the idea of "ready" that is associated with the [Product Backlog](../_guides/scrum-guide.md#product-backlog).
+
+> [!Quote]
+> Product Backlog items that can be Done by the Scrum Team within one Sprint are deemed ready for selection in a Sprint Planning event.\\
+> --[Scrum Glossary - Scrum.org](https://www.scrum.org/resources/scrum-glossary)
+{: .blockquote}
+
+This reflects the shared understand that is necessary for a Scrum Team to take on work.
+
+> [!Quote]
+> Ready: a shared understanding by the Product Owner and the Developers regarding the preferred level of description of Product Backlog items introduced at Sprint Planning.\\
+> --[Scrum Guide](../_guides/scrum-guide.md#product-backlog)
+{: .blockquote}
+
+While the intent behind a definition of ready is laudable the outcome is mostly an "us vs them" attitude between the Developers and the Stakeholders, or worse the Product Owner. Rather than having a checklist, definition of ready, or DOD, just get the Scrum Team together and come to an agreement of which items in the Backlog are "ready" for us to attempt.
+
diff --git a/src/collections/_guides/detecting-agile-bs.md b/src/collections/_guides/detecting-agile-bs.md
index 888c6c2..8400d0b 100644
--- a/src/collections/_guides/detecting-agile-bs.md
+++ b/src/collections/_guides/detecting-agile-bs.md
@@ -7,6 +7,8 @@ image: https://nkdagility.com/wp-content/uploads/2020/12/image-2.png
toc: true
pdf: true
pageStatus: published
+redirect_from:
+- /Guides/Detecting-Agile-BS.html
references:
- title: DIB Guide - Detecting Agile BS
url: https://media.defense.gov/2019/May/02/2002127286/-1/-1/0/DIBGUIDEDETECTINGAGILEBS.PDF
@@ -16,6 +18,13 @@ references:
url: https://media.defense.gov/2018/Jul/10/2001940937/-1/-1/0/DIB_METRICS_FOR_SOFTWARE_DEVELOPMENT_V0.9_2018.07.10.PDF
- title: Defense Innovation Board Do’s and Don’ts for Software
url: https://media.defense.gov/2018/Oct/09/2002049593/-1/-1/0/DIB_DOS_DONTS_SOFTWARE_2018.10.05.PDF
+recommendedVideos:
+ - title: stackconf 2021 | The Tyranny of Taylorism and how to spot Agile BS
+ embed: https://www.youtube.com/embed/OJ-7YVekG2s
+ - title: "stackconf online 2020 | Agile Evolution: An Enterprise transformation that shows that you can too"
+ embed: https://www.youtube.com/embed/6D7ZC5Yq8rU
+ - title: "Agile Evolution: Live Site Culture & Site Reliability at Azure DevOps"
+ embed: https://www.youtube.com/embed/5bgcpPqcGlw
---
Agile is a buzzword of software development, and so all DoD software development projects are, almost by default, now declared to be “agile.” The purpose of this document is to provide guidance to DoD program executives and acquisition professionals on how to detect software projects that are really using agile development versus those that are simply waterfall or spiral development in agile clothing (“agile-scrum-fall”).
diff --git a/src/collections/_guides/evidence-based-management-guide.md b/src/collections/_guides/evidence-based-management-guide.md
index c67e14e..ca14612 100644
--- a/src/collections/_guides/evidence-based-management-guide.md
+++ b/src/collections/_guides/evidence-based-management-guide.md
@@ -9,6 +9,16 @@ pageStatus: published
references:
- title: The Evidence-Based Management Guide | Scrum.org
url: https://scrum.org/resources/evidence-based-management-guide
+ - title: "Evidence-based Management: Gathering the metrics"
+ url: https://nkdagility.com/blog/evidence-based-management-gathering-metrics/
+ - title: "Metrics that matter with evidence-based management"
+ url: https://nkdagility.com/blog/metrics-that-matter-with-evidence-based-management/
+ - title: "Evidence-based Management: Gathering the metrics"
+ url: https://nkdagility.com/blog/evidence-based-management-gathering-metrics/
+ - title: Professional Agile Leadership with Evidence-Based Management (PAL-EBM)
+ url: https://nkdagility.com/training/courses/professional-agile-leadership-with-evidence-based-management-pal-ebm-training-experience-with-certification-measuring-value-to-enable-improvement-and-agility/
+recommendedContent:
+recommendedVideos:
---
Evidence-Based Management (EBM) is an empirical approach that helps organizations to continuously improve customer outcomes, organizational capabilities, and business results under conditions of uncertainty. It provides a framework for organizations to improve their ability to deliver value in an uncertain world, seeking a path toward strategic goals. Using intentional experimentation and evidence (measures), EBM enables organizations to systematically improve their performance over time and refine their goals based on better information
diff --git a/src/collections/_guides/kanban-guide-for-scrum-teams.md b/src/collections/_guides/kanban-guide-for-scrum-teams.md
index 056311c..4d11143 100644
--- a/src/collections/_guides/kanban-guide-for-scrum-teams.md
+++ b/src/collections/_guides/kanban-guide-for-scrum-teams.md
@@ -6,6 +6,19 @@ pageType: guide
toc: true
pdf: true
pageStatus: published
+redirect_from:
+ - /guides/Kanban-Guide-for-Scrum-Teams.html
+references:
+ - title: The Kanban Guide for Scrum Teams on Scrum.org
+ url: https://scrum.org/resources/kanban-guide-scrum-teams
+ - title: Work can flow across the Sprint boundary
+ url: https://nkdagility.com/blog/work-can-flow-across-sprint-boundary/
+ - title: No Estimates and is it advisable for a Scrum Team to adopt it?
+ url: https://nkdagility.com/blog/no-estimates-and-is-it-advisable-for-a-scrum-team-to-adopt-it/
+recommendedContent:
+ - collection: practices
+ path: _practices/service-level-expectation-sle.md
+recommendedVideos:
---
The flow-based perspective of Kanban can enhance and complement the Scrum framework and its implementation. Teams can add complementary Kanban practices whether they are just starting to use Scrum or have been using it all along. The Kanban Guide for Scrum Teams is the result of a collaboration between members of the Scrum.org community and leaders of the Kanban community. Together, they stand behind The Kanban Guide for Scrum Teams. It is their shared belief that professional product development practitioners can benefit from the application of Kanban together with Scrum.
@@ -124,14 +137,3 @@ A flow-based Sprint Retrospective adds the inspection of flow metrics and analyt
Scrum requires the team to create (at minimum) a valuable, useful Increment every Sprint. Scrum’s empiricism encourages the creation of multiple valuable increments during the Sprint to enable fast inspect and adapt feedback loops. Kanban helps manage the flow of these feedback loops more explicitly and allows the Scrum Team to identify bottlenecks, constraints, and impediments to enable this faster, more continuous delivery of value
Check our blog for more details
-
-Extracted from [The Kanban Guide for Scrum Teams on Scrum.org][1]{:target="_blank"}
-
-## Resources
-
-- [Work can flow across the Sprint boundary][2]
-- [No Estimates and is it advisable for a Scrum Team to adopt it?][3]
-
-[1]: https://scrum.org/resources/kanban-guide-scrum-teams "Kanban Guide for Scrum Teams"
-[2]: https://nkdagility.com/blog/work-can-flow-across-sprint-boundary/ "Work can flow across the Sprint boundary"
-[3]: https://nkdagility.com/blog/no-estimates-and-is-it-advisable-for-a-scrum-team-to-adopt-it/ "No Estimates and is it advisable for a Scrum Team to adopt it?"
\ No newline at end of file
diff --git a/src/collections/_guides/kanban-guide.md b/src/collections/_guides/kanban-guide.md
index 7b47968..c8ba4ce 100644
--- a/src/collections/_guides/kanban-guide.md
+++ b/src/collections/_guides/kanban-guide.md
@@ -6,6 +6,13 @@ pageType: guide
toc: true
pdf: true
pageStatus: published
+references:
+ - title: The Kanban Guide
+ url: https://kanbanguides.org/english/
+recommendedContent:
+ - collection: practices
+ path: _practices/service-level-expectation-sle.md
+recommendedVideos:
---
December 2020
@@ -24,7 +31,7 @@ Kanban comprises the following three practices working in tandem:
- Defining and visualizing a workflow
- Actively managing items in a workflow
- Improving a workflow
--
+
In their implementation, these Kanban practices are collectively called a Kanban system. Those who participate in the value delivery of a Kanban system are called Kanban system members.
## Why Use Kanban?
diff --git a/src/collections/_guides/manifesto-for-agile-software-development.md b/src/collections/_guides/manifesto-for-agile-software-development.md
index f62796a..d6c6e78 100644
--- a/src/collections/_guides/manifesto-for-agile-software-development.md
+++ b/src/collections/_guides/manifesto-for-agile-software-development.md
@@ -36,6 +36,4 @@ We follow these principles:
- Continuous attention to technical excellence and good design enhances agility.
- Simplicity--the art of maximizing the amount of work not done--is essential.
- The best architectures, requirements, and designs emerge from self-organizing teams.
-- At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
-
-Find the [Agile Manifesto](https://agilemanifesto.org/) for multiple languages and a full list of contributors.
\ No newline at end of file
+- At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
\ No newline at end of file
diff --git a/src/collections/_guides/nexus-framework.md b/src/collections/_guides/nexus-framework.md
index 86b6163..9f55128 100644
--- a/src/collections/_guides/nexus-framework.md
+++ b/src/collections/_guides/nexus-framework.md
@@ -5,6 +5,21 @@ pageType: guide
toc: true
pdf: true
pageStatus: published
+redirect_from:
+ - guides/Nexus-Framework/
+references:
+ - title: The 2020 Scrum Guide
+ url: https://scrumguides.org/scrum-guide.html
+ - title: The Nexus Guide
+ url: https://www.scrum.org/resources/online-nexus-guide
+recommendedContent:
+ - collection: practices
+ path: _practices/definition-of-done-dod.md
+ - collection: practices
+ path: _practices/definition-of-ready-dor.md
+recommendedVideos:
+ - title: Overview of The Scrum Framework with Martin Hinshelwood
+ embed: https://www.youtube.com/embed/Q2Fo3sM6BVo
---
@@ -17,12 +32,13 @@ Purpose of the Nexus Guide
Product delivery is complex, and the integration of product development work into a valuable product requires coordinating many diverse activities. Nexus is a framework for developing and sustaining scaled product delivery initiatives. It builds upon Scrum, extending it only where absolutely necessary to minimize and manage dependencies between multiple Scrum Teams while promoting empiricism and the Scrum Values.
-The Nexus framework inherits the purpose and intent of the Scrum framework as documented in the Scrum Guide ([scrumguides.org](http://scrumguides.org).) Scaled Scrum is still Scrum. Nexus does not change the core design or ideas of Scrum, or leave out elements, or negate the rules of Scrum. Doing so covers up problems and limits the benefits of Scrum, potentially even rendering it useless.
+The Nexus framework inherits the purpose and intent of the Scrum framework as documented in the [Scrum Guide](../_guides/scrum-guide.md) Scaled Scrum is still Scrum. Nexus does not change the core design or ideas of Scrum, or leave out elements, or negate the rules of Scrum. Doing so covers up problems and limits the benefits of Scrum, potentially even rendering it useless.
This Guide contains the definition of Nexus. Each element of the framework serves a specific purpose that is essential to help teams and organizations scale the benefits of Scrum with multiple teams working together.
As organizations use Nexus, they typically discover complementary patterns, processes, and practices that help them in their application of the Nexus framework. As with Scrum, such tactics vary widely and are described elsewhere.
+
Nexus Definition
================
diff --git a/src/collections/_practices/definition-of-ready-dor.md b/src/collections/_practices/definition-of-ready-dor.md
index ce8526e..3604bc6 100644
--- a/src/collections/_practices/definition-of-ready-dor.md
+++ b/src/collections/_practices/definition-of-ready-dor.md
@@ -5,6 +5,8 @@ layout: default
pageType: practice
pageStatus: published
recommendedContent:
+redirect_from:
+ - practices/Definition-of-Ready-DoR.html
---
**WARNING: Definition of Ready can result in significant anti-patterns in teams.**
diff --git a/src/collections/_practices/metrics-reports.md b/src/collections/_practices/metrics-reports.md
index 95e1b1c..2bfe689 100644
--- a/src/collections/_practices/metrics-reports.md
+++ b/src/collections/_practices/metrics-reports.md
@@ -6,6 +6,9 @@ toc: true
pdf: true
pageStatus: draft
recommendedContent:
+redirect_from:
+ - practices/Metrics-Reports/
+ - practices/Metrics-Reports.html
---
diff --git a/src/collections/_practices/service-level-expectation-sle.md b/src/collections/_practices/service-level-expectation-sle.md
index 5c5db96..5b92f63 100644
--- a/src/collections/_practices/service-level-expectation-sle.md
+++ b/src/collections/_practices/service-level-expectation-sle.md
@@ -7,6 +7,8 @@ toc: true
pdf: true
pageStatus: draft
recommendedContent:
+redirect_from:
+ - practices/Service-Level-Expectation-SLE.html
---
A service level expectation (SLE) forecasts how long it should take a given item to flow from start to finish within the Scrum Team's Workflow. The Scrum Team uses its SLE to find active flow issues and to inspect and adapt in cases of falling below those expectations.
diff --git a/src/collections/_strategies/one-engineering-system.md b/src/collections/_strategies/one-engineering-system.md
index 1cdbcd1..c01405f 100644
--- a/src/collections/_strategies/one-engineering-system.md
+++ b/src/collections/_strategies/one-engineering-system.md
@@ -5,6 +5,9 @@ pageType: strategy
toc: true
pdf: true
pageStatus: draft
+redirect_from:
+ - 1es/readme.html
+ - 1es
---
We have a number of tools that are in use and each one is different and provides
diff --git a/src/collections/_technologies/liberating-structures.md b/src/collections/_technologies/liberating-structures.md
index 3a51c74..942edcc 100644
--- a/src/collections/_technologies/liberating-structures.md
+++ b/src/collections/_technologies/liberating-structures.md
@@ -5,7 +5,11 @@ layout: default
pageType: technology
toc: true
pdf: true
-pageStatus: preview
+pageStatus: draft
+redirect_from:
+ - guides/Liberating-Structures.html
+ - guides/Liberating-Structures/
+ - technologies/Liberating-Structures.html
---
Liberating structures is a social technology.
diff --git a/src/collections/_technologies/liberating-structures/15-solutions.md b/src/collections/_technologies/liberating-structures/15-solutions.md
index 1eea6cb..397a3e1 100644
--- a/src/collections/_technologies/liberating-structures/15-solutions.md
+++ b/src/collections/_technologies/liberating-structures/15-solutions.md
@@ -6,7 +6,9 @@ toc: true
pdf: true
pageStatus: preview
category: liberating-structures
-permalink: /:collection/liberating-structures/:name
+redirect_from:
+ - recipes/technologies/liberating-structures/15-solutions.md
+ - technologies/liberating-structures/15-solutions.html
---
PURPOSE
diff --git a/src/collections/_technologies/liberating-structures/impromptu-networking.md b/src/collections/_technologies/liberating-structures/impromptu-networking.md
index fbc6442..ea4c58f 100644
--- a/src/collections/_technologies/liberating-structures/impromptu-networking.md
+++ b/src/collections/_technologies/liberating-structures/impromptu-networking.md
@@ -7,7 +7,9 @@ toc: true
pdf: true
pageStatus: preview
category: liberating-structures
-permalink: /:collection/liberating-structures/:name
+redirect_from:
+ - recipes/technologies/liberating-structures/impromptu-networking.md
+ - technologies/liberating-structures/impromptu-networking.html
---
## Purpose
diff --git a/src/collections/_technologies/liberating-structures/nine-whys.md b/src/collections/_technologies/liberating-structures/nine-whys.md
index edf9799..4ec17fa 100644
--- a/src/collections/_technologies/liberating-structures/nine-whys.md
+++ b/src/collections/_technologies/liberating-structures/nine-whys.md
@@ -6,7 +6,9 @@ toc: true
pdf: true
pageStatus: preview
category: liberating-structures
-permalink: /:collection/liberating-structures/:name
+redirect_from:
+ - recipes/technologies/liberating-structures/nine-whys.md
+ - technologies/liberating-structures/nine-whys.html
---
## PURPOSE
diff --git a/src/collections/_technologies/liberating-structures/shift-share.md b/src/collections/_technologies/liberating-structures/shift-share.md
index e578f64..f208168 100644
--- a/src/collections/_technologies/liberating-structures/shift-share.md
+++ b/src/collections/_technologies/liberating-structures/shift-share.md
@@ -7,7 +7,10 @@ toc: true
pdf: true
pageStatus: preview
category: liberating-structures
-permalink: /:collection/liberating-structures/:name
+redirect_from:
+ - recipes/technologies/liberating-structures/shift-share.md
+ - technologies/liberating-structures/shift-share.html
+ - guides/Liberating-Structures/Shift-&-Share-(40).html
---
PURPOSE
diff --git a/src/collections/_technologies/liberating-structures/what-so-what-now-what.md b/src/collections/_technologies/liberating-structures/what-so-what-now-what.md
index f59058b..773687b 100644
--- a/src/collections/_technologies/liberating-structures/what-so-what-now-what.md
+++ b/src/collections/_technologies/liberating-structures/what-so-what-now-what.md
@@ -7,9 +7,14 @@ toc: true
pdf: true
pageStatus: preview
category: liberating-structures
-permalink: /:collection/liberating-structures/:name
+redirect_from:
+ - technologies/liberating-structures/what-so-what-now-what.html
---
+{{page.path}}
+{{page.name}}
+{{page.collection}}
+
PURPOSE
Together, Look Back on Progress to Date and Decide What Adjustments Are Needed
diff --git a/src/collections/_technologies/openspace-agile.md b/src/collections/_technologies/openspace-agile.md
index 6a3cdf0..0638639 100644
--- a/src/collections/_technologies/openspace-agile.md
+++ b/src/collections/_technologies/openspace-agile.md
@@ -4,7 +4,7 @@ layout: default
toc: true
pdf: true
pageType: technology
-pageStatus:
+pageStatus: draft
discussionId:
---
diff --git a/src/collections/_technologies/professional-scrum.md b/src/collections/_technologies/professional-scrum.md
index a517066..4993b8b 100644
--- a/src/collections/_technologies/professional-scrum.md
+++ b/src/collections/_technologies/professional-scrum.md
@@ -31,8 +31,7 @@ recommendedVideos:
embed: https://www.youtube.com/embed/BYlv7eP9zgg
---
-
-Scrum is a Social Technology to help us shift to a collaborative, creative approach that helps us deal with the increasingly complex world that relies on increasingly complex technologies and products.
+Scrum is a Social Technology defined in the [Scrum Guide](../_guides/scrum-guide.md) to enable a shift to a collaborative, creative approach that helps us deal with the increasingly complex world that relies on increasingly difficult technologies and products.
## What is Professional Scrum?
@@ -44,16 +43,17 @@ Professional Scrum is a version of Scrum implemented by professionals for profes
## First Principals of Scrum
-- Transparency: It is the enabling principle to build trust among Scrum Team members, the stakeholders, and the organization in general. Without trust, no one can handle the complexity of product development.
-- Self-organization: Problems are best solved by those closest to it; it is key to autonomy and thus accountability and overcoming the industrial paradigm.
+- **Transparency**: It is the enabling principle to build trust among Scrum Team members, the stakeholders, and the organization in general. Without trust, no one can handle the complexity of product development.
+- **Self-organization**: Problems are best solved by those closest to it; it is key to autonomy and thus accountability and overcoming the industrial paradigm.
Scrum Values: Without courage, openness, and respect, there is no transparency.
-- Quality: Nothing great has ever originated from substandard, mediocre work, and a lack of craftsmanship. (I consider “done” an attribute of quality.)
+- **Quality**: Nothing great has ever originated from substandard, mediocre work and a lack of craftsmanship. (I consider “done” an attribute of quality.)
+
## Wording of the Scrum Guide
The Scrum Guide is a document that uses one word when it should really use ten in an effort to minimize any mandated or constraining element beyond the minimum required to deliver an empirical system.
-There are 9 load bearing elements of Scrum that are identified by the word "MUST", and 7 elements using the work "SHOULD". Everything else is present in service to those core elements and are open to different implementations that maintain integrity of the outcome of empiricism.
+There are 9 load bearing elements of Scrum that are identified by the word "MUST", and seven elements using the word "SHOULD". Everything else is present in service to those core elements and are open to different implementations that maintain the integrity of the outcome of empiricism.
### What MUST Scrum have?
@@ -132,9 +132,5 @@ Scrum is a lightweight framework that helps people, teams, and organizations gen
## Common failures or Anti-Patterns
-- Backlog Items are too Big
-- Dogmatic application of the mechanisms
-- No focus on Value
-- No sprint goals#
-- non-complex environment
+{% include content-collection.html collection = site.anti-patterns pageStatus = "published" catagory = "scrum" %}
diff --git a/src/collections/_workshops/customer-working-agreement.md b/src/collections/_workshops/customer-working-agreement.md
index bbc42ec..cc0303d 100644
--- a/src/collections/_workshops/customer-working-agreement.md
+++ b/src/collections/_workshops/customer-working-agreement.md
@@ -1,4 +1,6 @@
---
+redirect_from:
+ - workshops/Customer-Working-Agreement.html
---
## Customer Working Agreement
diff --git a/src/collections/_workshops/definition-of-done.md b/src/collections/_workshops/definition-of-done.md
index 5fc5df3..6919dac 100644
--- a/src/collections/_workshops/definition-of-done.md
+++ b/src/collections/_workshops/definition-of-done.md
@@ -1,4 +1,6 @@
---
+redirect_from:
+ - workshops/Definition-Of-Done.html
---
# What is the Definition of Done (DoD)
diff --git a/src/commitments.md b/src/commitments.md
index c918182..9f294f2 100644
--- a/src/commitments.md
+++ b/src/commitments.md
@@ -6,6 +6,8 @@ pdf: true
pageStatus:
pageType: overview
discussionId:
+redirect_from:
+ - commitments.html
---
These commitments exist to reinforce empiricism and the Scrum values for the Scrum Team and their
diff --git a/src/debunked-practices.md b/src/debunked-practices.md
index ea3a7b1..ed9a651 100644
--- a/src/debunked-practices.md
+++ b/src/debunked-practices.md
@@ -3,7 +3,7 @@ title: Debunked Practices
layout: default
toc: true
pdf: true
-pageStatus: published
+pageStatus: draft
pageType: overview
importance:
discussionId:
diff --git a/src/faq.md b/src/faq.md
new file mode 100644
index 0000000..911e1d4
--- /dev/null
+++ b/src/faq.md
@@ -0,0 +1,20 @@
+---
+title: Frequently Asked Questions
+layout: default
+pageType: index
+indexForCollection: faq
+toc: true
+pdf: true
+pageStatus: published
+---
+
+Some questions that we often get an their answers.
+
+
+## Questions
+
+{% include content-collection.html collection = site.faq %}
+
+## Draft Questions
+
+{% include content-collection.html collection = site.faq pageStatus = "draft" %}
\ No newline at end of file
diff --git a/src/introduction.md b/src/introduction.md
index 8f2560c..8148bbd 100644
--- a/src/introduction.md
+++ b/src/introduction.md
@@ -7,6 +7,8 @@ pageStatus: draft
pageType: overview
importance: 400
discussionId:
+redirect_from:
+ - introduction.html
---
\*\* Courage \| Focus \| Commitment \| Openness \| Respect \*\*
diff --git a/src/why-agile-does-not-work.md b/src/why-agile-does-not-work.md
index 3c6093c..5fd2361 100644
--- a/src/why-agile-does-not-work.md
+++ b/src/why-agile-does-not-work.md
@@ -4,7 +4,7 @@ layout: default
toc: true
pdf: true
pageType: overview
-pageStatus: published
+pageStatus: draft
discussionId:
references:
- title: What is Professional Scrum?