microsoft / microsoft/dynamics365patternspractices

[ERROR]: Duplicate folders in the SbD delivery plan (Initiate and Prepare) with unevenly split content

Open
#363 0 comments 0 reactions 1 assignee View on GitHub

@rachel-profitt is already working on this.

Since Aug 7, 2026.

bug
Dominant language
Python
Stars
227
Forks
106
Avg merge
2d 13h
Merged PRs (30d)
1

Description

Contact Details

lholck@pingala.eu

Describe the error you see in the documentation, or the correction you suggest

Source: SbD Delivery Plan JUL 2026

Issue: the delivery plan contains duplicate folder pairs:

  • Initiate: Project governance appears twice, and Implementation strategy appears twice.
  • Prepare: Change management and adoption appears twice.

The pairs are not clean copies — the content is split unevenly across them. For example, one
Project governance folder holds the goal/commercial items (metrics, budget, goals) while
the other holds the approach/organisation items (approach, project organization, governance
structures); one Implementation strategy folder holds the methodology-choice tasks while
the other holds solution overview/deployment tasks. This looks like an artifact of merging
spreadsheet sections rather than an intentional structure.

While we're at it, two spelling errors in the same plan: "Change mangement" and
"Process-focsued".

Expected: one folder per topic per phase (or, if the split is intentional, distinct
folder names that make the difference visible).

Impact: importing the plan produces a structure where every team must first work out
which of two identically named folders an activity belongs to.

Link to the article where the error is

delivery plan

Code of Conduct
  • I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.