From e203e288faa05de8c77de91bb467b120fb858dc2 Mon Sep 17 00:00:00 2001 From: Tess Ferrandez Date: Thu, 15 Aug 2024 10:48:22 +0200 Subject: [PATCH] fix agile links --- docs/ENG-FUNDAMENTALS-CHECKLIST.md | 2 +- docs/SPRINT-STRUCTURE.md | 12 ++++++------ .../design-reviews/recipes/engagement-process.md | 2 +- .../recipes/engineering-feasibility-spikes.md | 2 +- docs/machine-learning/ml-project-management.md | 2 +- 5 files changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/ENG-FUNDAMENTALS-CHECKLIST.md b/docs/ENG-FUNDAMENTALS-CHECKLIST.md index 76eca615cb..9a1ea69a73 100644 --- a/docs/ENG-FUNDAMENTALS-CHECKLIST.md +++ b/docs/ENG-FUNDAMENTALS-CHECKLIST.md @@ -97,7 +97,7 @@ More details on [code reviews](code-reviews/README.md) - [ ] Experiments have owners and are added to project backlog. - [ ] The team conducts longer retrospective for Milestones and project completion. -More details on [retrospectives](agile-development/core-expectations/README.md) +More details on [retrospectives](agile-development/basics/ceremonies.md#retrospectives) ## Engineering Feedback diff --git a/docs/SPRINT-STRUCTURE.md b/docs/SPRINT-STRUCTURE.md index 0e5171acfc..4433a1dd42 100644 --- a/docs/SPRINT-STRUCTURE.md +++ b/docs/SPRINT-STRUCTURE.md @@ -10,7 +10,7 @@ The purpose of this document is to: ### Before starting the project -- [ ] [Discuss and start writing the Team Agreements](agile-development/advanced-topics/team-agreements/README.md). Update these documents with any process decisions made throughout the project +- [ ] Discuss and start writing the Team Agreements. Update these documents with any process decisions made throughout the project - [Working Agreement](agile-development/advanced-topics/team-agreements/working-agreements.md) - [Definition of Ready](agile-development/advanced-topics/team-agreements/definition-of-ready.md) - [Definition of Done](agile-development/advanced-topics/team-agreements/definition-of-done.md) @@ -18,7 +18,7 @@ The purpose of this document is to: - [ ] [Set up the repository/repositories](source-control/README.md#creating-a-new-repository) - Decide on repository structure/s - Add [README.md](resources/templates/README.md), [LICENSE](resources/templates/LICENSE), [CONTRIBUTING.md](resources/templates/CONTRIBUTING.md), .gitignore, etc -- [ ] [Build a Product Backlog](agile-development/advanced-topics/backlog-management/README.md) +- [ ] [Build a Product Backlog](agile-development/advanced-topics/backlog-management) - Set up a project in your chosen project management tool (ex. Azure DevOps) - [INVEST](https://en.wikipedia.org/wiki/INVEST_(mnemonic)) in good User Stories and Acceptance Criteria - [Non-Functional Requirements Guidance](design/design-patterns/non-functional-requirements-capture-guide.md) @@ -64,12 +64,12 @@ The purpose of this document is to: ### Day 5 -- [ ] Conduct a Sprint Demo -- [ ] [Conduct a Retrospective](agile-development/core-expectations/README.md) +- [ ] Conduct a [Sprint Demo](agile-development/basics/ceremonies.md#sprint-demo) +- [ ] Conduct a [Retrospective](agile-development/basics/ceremonies.md#retrospectives) - Determine required participants, how to capture input (tools) and outcome - Set a timeline, and discuss facilitation, meeting structure etc. -- [ ] [Refine the Backlog](agile-development/advanced-topics/backlog-management/README.md) +- [ ] [Refine the Backlog](agile-development/advanced-topics/backlog-management) - Determine required participants - Update the [Definition of Ready](agile-development/advanced-topics/team-agreements/definition-of-ready.md) - - Update estimates, and the [Estimation](agile-development/core-expectations/README.md) document + - Update estimates, and the [Estimation](agile-development/basics/ceremonies.md#estimation) document - [ ] [Submit Engineering Feedback for issues encountered](engineering-feedback/README.md) diff --git a/docs/design/design-reviews/recipes/engagement-process.md b/docs/design/design-reviews/recipes/engagement-process.md index 4b4717b24d..68999861e7 100644 --- a/docs/design/design-reviews/recipes/engagement-process.md +++ b/docs/design/design-reviews/recipes/engagement-process.md @@ -37,7 +37,7 @@ Stories that will benefit from design reviews have one or more of the following ## Sprint Backlog Refinement -If your team is not already hosting a [Sprint Backlog Refinement](../../../agile-development/advanced-topics/backlog-management/README.md) session at least once per week you should consider it. It is a great opportunity to: +If your team is not already hosting a [Sprint Backlog Refinement](../../../agile-development/advanced-topics/backlog-management) session at least once per week you should consider it. It is a great opportunity to: 1. Keep the backlog clean 1. Re-prioritize work based on shifting business priorities diff --git a/docs/design/design-reviews/recipes/engineering-feasibility-spikes.md b/docs/design/design-reviews/recipes/engineering-feasibility-spikes.md index cd7f226569..26e7f2fb87 100644 --- a/docs/design/design-reviews/recipes/engineering-feasibility-spikes.md +++ b/docs/design/design-reviews/recipes/engineering-feasibility-spikes.md @@ -13,7 +13,7 @@ The following guidelines outline how Microsoft and the customer can incorporate ## Pre-Mortem -A good way to gauge what engineering spikes to conduct is to do a [pre-mortem](https://www.facebook.com/business/m/thinkkit/exercises/strong-starts/pre-mortem). +A good way to gauge what engineering spikes to conduct is to do a pre-mortem. ### What is a pre-mortem? diff --git a/docs/machine-learning/ml-project-management.md b/docs/machine-learning/ml-project-management.md index 7087ea6683..002ee1c1cb 100644 --- a/docs/machine-learning/ml-project-management.md +++ b/docs/machine-learning/ml-project-management.md @@ -13,7 +13,7 @@ To learn more about how ISE runs the Agile process for software development team Within this framework, the team follows these Agile ceremonies: -- [Backlog management](../agile-development/advanced-topics/backlog-management/README.md) +- [Backlog management](../agile-development/advanced-topics/backlog-management) - [Retrospectives](../agile-development/basics/ceremonies.md#retrospectives) - [Scrum of Scrums](../agile-development/advanced-topics/effective-organization/scrum-of-scrums.md) (where applicable) - [Sprint planning](../agile-development/basics/ceremonies.md#sprint-planning)