add delivery plan page

added new delivery plan page
renamed Collaboration page to fix broken link

[Ticket: X]

Signed-off-by: Scott McCarthy <scott.mccarthy@opencastsoftware.com>

Author: idmac75

docs/devops-practices/continuous-planning/agile-development/Delivery-Plan.md

@@ -1,8 +1,8 @@
 # Delivery Plan
 
-## Goals
+## Overview
 
-While Scrum does not require and discourages planning more than one sprint at a time. Most of us work in enterprises where we are dependent outside teams (for example: marketing, sales, support).
+While Scrum does not require and discourages planning more than one sprint at a time. Most of us work in enterprises where we are dependent outside teams (for example: marketing, sales, support or other development teams).
 
 A rough assessment of the planned project scope is achievable within a reasonable time frame and resources. The goal is to have a rough plan and estimate as a starting point, not to implement "Agile-fall or Wagile."
 
@@ -22,7 +22,7 @@ One approach you can take to accomplish is with stickies and a spreadsheet.
 Step 1: Stack rank the features for everything in your backlog
 
 - Functional Features
-- [Non-functional Features](/Continuous-Planning/Design-Reviews/Design-Patterns/Non-Functional-Requirements-Capture-Guide.md)
+- [Non-functional Features](../continuous-planning/design-reviews/design-patterns/non-functional-requirements-capture-guide.md)
 - User Research and Design
 - Testing
 - Documentation

…-development/Collaboration/Teaming-Up.md …ment/Team-Agreements/team-engagements.mddocs/devops-practices/continuous-planning/agile-development/Collaboration/Teaming-Up.md renamed to docs/devops-practices/continuous-planning/agile-development/Team-Agreements/team-engagements.md docs/devops-practices/continuous-planning/agile-development/Collaboration/Teaming-Up.md renamed to docs/devops-practices/continuous-planning/agile-development/Team-Agreements/team-engagements.md

@@ -1,4 +1,4 @@
-# Engagement Team Development
+# Team Engagements
 
 In every engagement or project, dynamics are different & so are the team requirements. Based on transfer learning among teams, we aim to build right "code-with" environments in every team.
 
@@ -11,7 +11,7 @@ However those phases can be extremely fast or sometimes mismatched in teams due
 
 In order to minimize the risk and set the expectations on the right way for all parties, an identification phase is important to understand each other. Some potential steps in this phase may be as following (not limited):
 
-- [Working agreement](/Continuous-Planning/Agile-Development/Team-Agreements/Working-Agreements.md)
+- [Working agreement](./Continuous-Planning/Agile-Development/Team-Agreements/Working-Agreements.md)
 
 - Identification of styles/preferences in communication, sharing, learning, decision making of each team member
 

mkdocs.yml

@@ -75,6 +75,7 @@ nav:
             - What is is Agile:             devops-practices/continuous-planning/agile-development/whatis-agile.md
             - Backlog Management:           devops-practices/continuous-planning/agile-development/backlog-management.md
             - Collaboration:                devops-practices/continuous-planning/agile-development/collaboration.md
+            - Delivery Plan:                devops-practices/continuous-planning/agile-development/delivery-plan.md
 
     - Tools:
          -                                  devops-tools/tools-overview.md