fix agile links

docs/SPRINT-STRUCTURE.md

@@ -14,7 +14,7 @@ The purpose of this document is to:
   - [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)
-  - [Estimation](agile-development/core-expectations/README.md)
+  - [Estimation](agile-development/basics/ceremonies.md#estimation)
 - [ ] [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
@@ -25,7 +25,7 @@ The purpose of this document is to:
 
 ### Day 1
 
-- [ ] [Plan the first sprint](agile-development/core-expectations/README.md)
+- [ ] [Plan the first sprint](agile-development/basics/ceremonies.md#sprint-planning)
   - Agree on a sprint goal, and how to measure the sprint progress
   - Determine team capacity
   - Assign user stories to the sprint and split user stories into tasks
@@ -42,7 +42,7 @@ The purpose of this document is to:
 - [ ] [Set up Source Control](source-control/README.md)
   - Agree on [best practices for commits](source-control/git-guidance/README.md#commit-best-practices)
 - [ ] [Set up basic Continuous Integration with linters and automated tests](continuous-integration/README.md)
-- [ ] [Set up meetings for Daily Stand-ups and decide on a Process Lead](agile-development/core-expectations/README.md)
+- [ ] [Set up meetings for Daily Stand-ups and decide on a Process Lead](agile-development/basics/ceremonies.md#stand-up)
   - Discuss purpose, goals, participants and facilitation guidance
   - Discuss timing, and how to run an efficient stand-up
 - [ ] [If the project has sub-teams, set up a Scrum of Scrums](agile-development/advanced-topics/effective-organization/scrum-of-scrums.md)

docs/design/design-reviews/recipes/engagement-process.md

@@ -21,7 +21,7 @@ During this time the team uncovers many unknowns, leveraging all new-found infor
 
 ## Sprint Planning
 
-In many engagements Microsoft works with customers using a SCRUM agile development process which begins with sprint planning. [Sprint planning](../../../agile-development/core-expectations/README.md) is a great opportunity to dive deep into the next set of high priority work. Some key points to address are the following:
+In many engagements Microsoft works with customers using a SCRUM agile development process which begins with sprint planning. [Sprint planning](../../../agile-development/basics/ceremonies.md#sprint-planning) is a great opportunity to dive deep into the next set of high priority work. Some key points to address are the following:
 
 1. Identify stories that require design reviews
 1. Separate design from implementation for complex stories
@@ -48,7 +48,7 @@ The team can follow the same steps from [sprint planning](#sprint-planning) to h
 
 ## Sprint Retrospectives
 
-[Sprint retrospectives](../../../agile-development/core-expectations/README.md) are a great time to check in with the dev team, identify what is working or not working, and propose changes to keep improving.
+[Sprint retrospectives](../../../agile-development/basics/ceremonies.md#retrospectives) are a great time to check in with the dev team, identify what is working or not working, and propose changes to keep improving.
 
 It is also a great time to check in on design reviews
 

docs/design/design-reviews/recipes/engineering-feasibility-spikes.md

@@ -89,4 +89,4 @@ Conducting engineering feasibility spikes sets the team and the customer up for
 - The key purpose of the engineering feasibility spike is learning.
 - Learning comes from both conducting and sharing insights from spikes.
 - Use new spike infused learnings to revise, refine, re-prioritize, or create the next set of spikes.
-- When spikes are completed, look for new weekly rhythms like adding a ‘risk’ column to the retro board or raising topics at [daily standup](../../../agile-development/core-expectations/README.md) to identify emerging risks.
+- When spikes are completed, look for new weekly rhythms like adding a ‘risk’ column to the retro board or raising topics at [daily standup](../../../agile-development/basics/ceremonies.md#stand-up) to identify emerging risks.

docs/machine-learning/ml-project-management.md

@@ -14,17 +14,17 @@ 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)
-- [Retrospectives](../agile-development/core-expectations/README.md)
+- [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/core-expectations/README.md)
-- [Stand-ups](../agile-development/core-expectations/README.md)
+- [Sprint planning](../agile-development/basics/ceremonies.md#sprint-planning)
+- [Stand-ups](../agile-development/basics/ceremonies.md#stand-up)
 - [Working agreement](../agile-development/advanced-topics/team-agreements/working-agreements.md)
 
 ### Notes on Agile process during exploration and experimentation
 
 1. While acknowledging the fact that ML user stories and research spikes are less predictable than software development ones, we strive to have a deliverable for every user story in every sprint.
 
-2. User stories and spikes are usually estimated using [T-shirt sizes](../agile-development/core-expectations/README.md) or similar, and not in actual days/hours. See more [here](../agile-development/core-expectations/README.md) on story estimation.
+2. User stories and spikes are usually estimated using [T-shirt sizes](../agile-development/basics/ceremonies.md#estimation) or similar, and not in actual days/hours.
 
 3. ML design sessions should be included in each sprint.