Skip to content

Commit

Permalink
Merge pull request #41 from nkdAgility/UpdateProfessionalScrum
Browse files Browse the repository at this point in the history
Updatearounie with 404 fixes
  • Loading branch information
MrHinsh authored Apr 26, 2023
2 parents e9ba2c1 + 1b4682b commit a474a8a
Show file tree
Hide file tree
Showing 33 changed files with 245 additions and 98 deletions.
22 changes: 11 additions & 11 deletions Gemfile.lock
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ GEM
i18n (>= 1.6, < 2)
minitest (>= 5.1)
tzinfo (~> 2.0)
addressable (2.8.1)
addressable (2.8.4)
public_suffix (>= 2.0.2, < 6.0)
builder (3.2.4)
colorator (1.1.0)
Expand All @@ -86,7 +86,7 @@ GEM
forwardable-extended (2.6.0)
globalid (1.1.0)
activesupport (>= 5.0)
google-protobuf (3.22.2-x64-mingw-ucrt)
google-protobuf (3.22.3-x64-mingw-ucrt)
http_parser.rb (0.8.0)
i18n (1.12.0)
concurrent-ruby (~> 1.0)
Expand All @@ -106,9 +106,9 @@ GEM
safe_yaml (~> 1.0)
terminal-table (>= 1.8, < 4.0)
webrick (~> 1.7)
jekyll-github-metadata (2.15.0)
jekyll-github-metadata (2.16.0)
jekyll (>= 3.4, < 5.0)
octokit (~> 4.0, != 4.4.0)
octokit (>= 4, < 7, != 4.4.0)
jekyll-last-modified-at (1.3.0)
jekyll (>= 3.7, < 5.0)
posix-spawn (~> 0.3.9)
Expand All @@ -124,7 +124,7 @@ GEM
jekyll (>= 3.8, < 5.0)
jekyll-sitemap (1.4.0)
jekyll (>= 3.7, < 5.0)
jekyll-target-blank (2.0.0)
jekyll-target-blank (2.0.2)
jekyll (>= 3.0, < 5.0)
nokogiri (~> 1.10)
jekyll-time-to-read (0.1.2)
Expand All @@ -143,7 +143,7 @@ GEM
listen (3.8.0)
rb-fsevent (~> 0.10, >= 0.10.3)
rb-inotify (~> 0.9, >= 0.9.10)
loofah (2.19.1)
loofah (2.20.0)
crass (~> 1.0.2)
nokogiri (>= 1.5.9)
mail (2.8.1)
Expand All @@ -165,18 +165,18 @@ GEM
timeout
net-smtp (0.3.3)
net-protocol
nio4r (2.5.8)
nokogiri (1.14.2-x64-mingw-ucrt)
nio4r (2.5.9)
nokogiri (1.14.3-x64-mingw-ucrt)
racc (~> 1.4)
octokit (4.25.1)
octokit (6.1.1)
faraday (>= 1, < 3)
sawyer (~> 0.9)
pathutil (0.16.2)
forwardable-extended (~> 2.6)
posix-spawn (0.3.15)
public_suffix (5.0.1)
racc (1.6.2)
rack (2.2.6.4)
rack (2.2.7)
rack-test (2.1.0)
rack (>= 1.3)
rails (7.0.4.3)
Expand Down Expand Up @@ -218,7 +218,7 @@ GEM
ruby2_keywords (0.0.5)
rubyzip (2.3.2)
safe_yaml (1.0.5)
sass-embedded (1.60.0-x64-mingw-ucrt)
sass-embedded (1.62.0-x64-mingw-ucrt)
google-protobuf (~> 3.21)
sawyer (0.9.2)
addressable (>= 2.3.5)
Expand Down
6 changes: 5 additions & 1 deletion src/_includes/content-collection.html
Original file line number Diff line number Diff line change
@@ -1,12 +1,15 @@
{% if include.collection != null %}

{% if include.pageStatus == null %}
{% assign filterPageStatus = "published" %}
{% else %}
{% assign filterPageStatus = include.pageStatus %}
{% endif %}

{% assign items = include.collection | where: "category", include.category | where: "pageStatus", filterPageStatus | sort: "importance" | reverse %}
{% if items == empty or items == 0 %}
<p>No items in {{include.pageStatus}} currently...</p>
{% else %}

<ul class="btn-toggle-nav fw-normal pb-1 small">
{% for item in items %}
<li class="align-items-center">
Expand All @@ -16,6 +19,7 @@
</li>
{% endfor %}
</ul>
{% endif %}
{% else %}
<p>No items in collection</p>
{% endif %}
5 changes: 2 additions & 3 deletions src/_includes/recommended-videos.html
Original file line number Diff line number Diff line change
Expand Up @@ -4,16 +4,15 @@
<h2>Recommended Videos</h2>
<div class="row">
{% for item in videos %}
<div class="col-12 col-lg-6 col-xl-6 d-flex">
<div class="col-12 col-lg-6 col-xl-6 d-flex p-3">
<div class="card">
<div class="card-img-top ratio ratio-16x9">
<iframe src="{{item.embed}}" title="{{item.title}}" allowfullscreen></iframe>
</div>
<div class="card-body">
<h5 class="card-title">{{item.title}}</h5>
</div>
</div>

</div>
</div>
{% endfor %}
</div>
Expand Down
49 changes: 14 additions & 35 deletions src/_includes/sidebar-collection.html
Original file line number Diff line number Diff line change
@@ -1,51 +1,30 @@
{% assign collection = site.collections | where: "label", include.collection | first %}
<li class="mb-1">
<strong class="bd-links-heading d-flex w-100 align-items-center fw-semibold">{{ include.collection | capitalize_all }}</strong>
<a href="#" class="navbar-toggler btn btn-toggle link-body-emphasis d-inline-flex text-decoration-none rounded border-0 collapsed"
data-bs-toggle="collapse"
data-bs-target="#{{include.collection}}-collapse"
aria-expanded="false"><strong class="bd-links-heading d-flex w-100 align-items-center fw-semibold"><i class="fa-sharp fa-solid fa-chevron-down"></i>&nbsp; {{ include.collection | capitalize_all }}</strong></a>
<div class="collapse" id="{{include.collection}}-collapse">
<ul class="btn-toggle-nav list-unstyled fw-normal pb-1 ms-2 small">
{% assign overview = site.pages | where: "pageType", "index" | where: "indexForCollection", include.collection | first %}
{% if overview != null %}
<a href="{{ site.baseurl }}{{overview.url}}">Overview</a>
<li class="align-items-center">
<a href="{{ site.baseurl }}{{overview.url}}" class="link-body-emphasis d-inline-flex text-decoration-none rounded">Overview</a>
</li>
{% endif %}
{% if collection != null %}
{% assign items = collection.docs | where: "category", null | where: "pageStatus", "published" | sort: "importance" | reverse %}

<ul class="btn-toggle-nav list-unstyled fw-normal pb-1 small">
{% for item in items %}
{% if item.pageStatus != "draft" %}
<li class="align-items-center">
<a href="{{ site.baseurl }}{{ item.url }}" class="link-body-emphasis d-inline-flex text-decoration-none rounded">
{{ item.title }}
</a>
</li>
{% 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 %}
<li class="align-items-center">
<small>
<a
href="#"
class="link-body-emphasis d-inline-flex text-decoration-none rounded"
data-bs-toggle="collapse"
data-bs-target="#{{include.collection}}-collapse"
aria-expanded="false">Preview Content</a>
<div class="collapse" id="{{include.collection}}-collapse">
<ul class="btn-toggle-nav list-unstyled fw-normal pb-1 ms-2 small">
{% for item in items %}
<li class="align-items-center">
<a href="{{ site.baseurl }}{{ item.url }}" class="link-body-emphasis d-inline-flex text-decoration-none rounded">{{ item.title }}</a>&nbsp;<small>
{% if item.pageStatus != "production" %}
<i class="fa-regular {% if item.pageStatus == null %}fa-triangle-exclamation{% else %}fa-circle-exclamation{% endif %}"></i>
{% endif %}
</small>
<a href="{{ site.baseurl }}{{ item.url }}" class="link-body-emphasis d-inline-flex text-decoration-none rounded">{{ item.title }}</a>
</li>
{% endfor %}
</ul>
</div>
</small>
</li>
{% endif %}
</ul>
{% else %}
<p>No items in collection</p>
<li>No items in collection</li>
{% endif %}
</ul>
</div>
</li>
49 changes: 37 additions & 12 deletions src/_includes/sidebar-pagetype.html
Original file line number Diff line number Diff line change
@@ -1,19 +1,41 @@
{% assign pages = site.pages | where: "pageType", include.pageType | where: "pageStatus", "published" | sort: "importance" | reverse %}
<li class="mb-1">
<strong class="bd-links-heading d-flex w-100 align-items-center fw-semibold">{{ include.title | capitalize_all }}</strong>
<ul class="btn-toggle-nav list-unstyled fw-normal pb-1 small">
{% for page in pages %}
<li class="align-items-center">
<a href="{{ site.baseurl }}{{ page.url }}" class="link-body-emphasis d-inline-flex text-decoration-none rounded">
{{ page.title }}
</a>
</li>
{% endfor %}
<a href="#" class="navbar-toggler btn btn-toggle link-body-emphasis d-inline-flex text-decoration-none rounded border-0 collapsed"
data-bs-toggle="collapse"
data-bs-target="#{{include.collection}}-collapse"
aria-expanded="false">
<strong class="bd-links-heading d-flex w-100 align-items-center fw-semibold">
<i class="fa-sharp fa-solid fa-chevron-down"></i>&nbsp;
{{ include.title | capitalize_all }}
</strong>
</a>
<div class="collapse" id="{{include.collection}}-collapse">
<ul class="btn-toggle-nav list-unstyled fw-normal pb-1 ms-2 small">
{% for page in pages %}
<li class="align-items-center">
<a href="{{ site.baseurl }}{{ page.url }}" class="link-body-emphasis d-inline-flex text-decoration-none rounded">
{{ page.title }}
</a>
</li>
{% 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 %}
<li class="align-items-center">
<a href="{{ site.baseurl }}{{ item.url }}" class="link-body-emphasis d-inline-flex text-decoration-none rounded">{{ item.title }}</a>
</li>
{% endfor %}
{% endif %}
{% else %}
<li>No items in collection</li>
{% endif %}
{% assign pages = site.pages | where: "pageType", include.pageType | except: "pageStatus", "published" | sort: "importance" | reverse %}
{% if pages != empty %}
<li class="align-items-center">
<small>
<a href="#" class="link-body-emphasis d-inline-flex text-decoration-none rounded" data-bs-toggle="collapse" data-bs-target="#{{include.pageType}}-collapse" aria-expanded="false">Preview Content</a>
<a href="#" class="link-body-emphasis d-inline-flex text-decoration-none rounded" data-bs-toggle="collapse" data-bs-target="#{{include.pageType}}-collapse" aria-expanded="false">Draft</a>
<div class="collapse" id="{{include.pageType}}-collapse">
<ul class="btn-toggle-nav list-unstyled fw-normal pb-1 ms-2 small">
{% for page in pages %}
Expand All @@ -24,5 +46,8 @@
</small>
</li>
{% endif %}
</ul>
</li>
</ul>
</div>
</li>


Binary file added src/assets/images/nexus-framework.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
2 changes: 2 additions & 0 deletions src/collections/_anti-patterns/backlog-items-too-big.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@ layout: default
toc: true
pdf: true
pageType: anti-pattern
catagorys:
- scrum
pageStatus: draft
discussionId:
references:
Expand Down
Original file line number Diff line number Diff line change
@@ -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.\\
> --<cite>[Scrum Glossary - Scrum.org](https://www.scrum.org/resources/scrum-glossary)</cite>
{: .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.\\
> --<cite>[Scrum Guide](../_guides/scrum-guide.md#product-backlog)</cite>
{: .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.

9 changes: 9 additions & 0 deletions src/collections/_guides/detecting-agile-bs.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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”).
Expand Down
10 changes: 10 additions & 0 deletions src/collections/_guides/evidence-based-management-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
24 changes: 13 additions & 11 deletions src/collections/_guides/kanban-guide-for-scrum-teams.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -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?"
Loading

0 comments on commit a474a8a

Please sign in to comment.