Skip to content

Commit ca25bc0

Browse files
committed
fix to file name casing
fix to Git caching filename with case sensitivity. this is to solve number of 404 page errors that cannot be found. Signed-off-by: Scott McCarthy <scott.mccarthy@opencastsoftware.com>
1 parent f97030f commit ca25bc0

17 files changed

Lines changed: 28 additions & 28 deletions

docs/devops-practices/continuous-planning/agile-development/backlog-management.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -123,7 +123,6 @@ _Example:_ Feedback like “the homepage doesn’t feel good” will not help th
123123

124124
### Useful Links
125125

126-
- Always try and deliver in [Minimal Slices](./Minimal-Slices.md)
127126
- [Backlog Refinement: Who Should Attend and How to Maximize Value](https://www.mountaingoatsoftware.com/blog/backlog-grooming-who-should-attend-and-how-to-maximize-value#:~:text=A%20good%20rule%20of%20thumb,may%20be%20able%20to%20participate)
128127
- [You're doing backlog refinement wrong. Here's how to do it less wrong](https://clubhouse.io/blog/how-to-do-backlog-refinement-less-wrong/)
129128
- [multi team backlog refinement](https://www.scrum.org/resources/blog/multi-team-backlog-refinement)

docs/devops-practices/continuous-planning/agile-development/Collaboration.md renamed to docs/devops-practices/continuous-planning/agile-development/collaboration.md

File renamed without changes.

docs/devops-practices/continuous-planning/agile-development/Delivery-Plan.md renamed to docs/devops-practices/continuous-planning/agile-development/delivery-plan.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ One approach you can take to accomplish is with stickies and a spreadsheet.
2222
Step 1: Stack rank the features for everything in your backlog
2323

2424
- Functional Features
25-
- [Non-functional Features](../continuous-planning/design-reviews/design-patterns/non-functional-requirements-capture-guide.md)
25+
- [Non-functional Features](design-reviews/design-patterns/non-functional-requirements-capture-guide.md)
2626
- User Research and Design
2727
- Testing
2828
- Documentation

docs/devops-practices/continuous-planning/agile-development/Retrospectives.md renamed to docs/devops-practices/continuous-planning/agile-development/retrospectives.md

File renamed without changes.

docs/devops-practices/continuous-planning/agile-development/Scrum-of-Scrums.md renamed to docs/devops-practices/continuous-planning/agile-development/scrum-of-scrums.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
# Scrum of Scrums
22

3-
Scrum of scrums is a technique used to scale Scrum to a larger group working towards the same project goal. In Scrum, we consider a team being too big when going over 10-12 individuals. This should be decided on a case by case basis. If the project is set up in multiple work streams that contain a fixed group of people and a common [stand-up](stand-ups/README.md) meeting is slowing down productivity: scrum of scrums should be considered. The team would identify the different subgroups that would act as a separate scrum teams with their own backlog, board and [stand-up](stand-ups/README.md).
3+
Scrum of scrums is a technique used to scale Scrum to a larger group working towards the same project goal. In Scrum, we consider a team being too big when going over 10-12 individuals. This should be decided on a case by case basis. If the project is set up in multiple work streams that contain a fixed group of people and a common [stand-up](stand-ups.md) meeting is slowing down productivity: scrum of scrums should be considered. The team would identify the different subgroups that would act as a separate scrum teams with their own backlog, board and [stand-up](stand-ups.md).
44

55
## Goals
66

77
The goal of the scrum of scrums ceremony is to give sub-teams the agility they need while not loosing visibility and coordination. It also helps to ensure that the sub-teams are achieving their sprint goals, and they are going in the right direction to achieve the overall project goal.
88

9-
The scrum of scrums ceremony happens every day and can be seen as a regular [stand-up](/Continuous-Planning/Agile-Development/Stand-Ups.md):
9+
The scrum of scrums ceremony happens every day and can be seen as a regular [stand-up](stand-ups.md):
1010

1111
- What was done the day before by the sub-team.
1212
- What will be done today by the sub-team.
@@ -15,11 +15,11 @@ The scrum of scrums ceremony happens every day and can be seen as a regular [sta
1515

1616
The outcome of the meeting will result in a list of impediments related to coordination of the whole project. Solutions could be: agreeing on interfaces between teams, discussing architecture changes, evolving responsibility boundaries, etc.
1717

18-
This list of impediments is usually managed in a separate [backlog](/Continuous-Planning/Agile-Development/Backlog-Management.md) but does not have to.
18+
This list of impediments is usually managed in a separate [backlog](backlog-management.md) but does not have to.
1919

2020
## Participation
2121

22-
The common guideline is to have on average one person per sub-team to participate in the scrum of scrums. Ideally, the Process Lead of each sub-team would represent them in this ceremony. In some instances, the representative for the day is selected at the end of each sub-team daily [stand-up](/Continuous-Planning/Agile-Development/Stand-Ups.md) and could change every day. In practice, having a fixed representative tends to be more efficient in the long term.
22+
The common guideline is to have on average one person per sub-team to participate in the scrum of scrums. Ideally, the Process Lead of each sub-team would represent them in this ceremony. In some instances, the representative for the day is selected at the end of each sub-team daily [stand-up](stand-ups.md) and could change every day. In practice, having a fixed representative tends to be more efficient in the long term.
2323

2424
## Impact
2525

@@ -29,8 +29,8 @@ When choosing to implement Scrum of Scrums, you need to keep in mind that some t
2929

3030
## Measures
3131

32-
The easiest way to measure the impact is by tracking the time to resolve issues in the scrum of scrums backlog. You can also track issues reported during the [retrospective](/Continuous-Planning/Agile-Development/Retrospectives.md) related to global coordination (is it well done? can it be improved?).
32+
The easiest way to measure the impact is by tracking the time to resolve issues in the scrum of scrums backlog. You can also track issues reported during the [retrospective](retrospectives.md) related to global coordination (is it well done? can it be improved?).
3333

3434
## Facilitation Guidance
3535

36-
This should be facilitated like a regular [stand-up](/Continuous-Planning/Agile-Development/Stand-Ups.md).
36+
This should be facilitated like a regular [stand-up](stand-ups.md).

docs/devops-practices/continuous-planning/agile-development/Sprint-Planning.md renamed to docs/devops-practices/continuous-planning/agile-development/sprint-planning.md

File renamed without changes.

docs/devops-practices/continuous-planning/agile-development/Sprint-Planning/Estimation.md renamed to docs/devops-practices/continuous-planning/agile-development/sprint-planning/Estimation.md

File renamed without changes.

docs/devops-practices/continuous-planning/agile-development/Sprint-Planning/Sprint-Structure.md renamed to docs/devops-practices/continuous-planning/agile-development/sprint-planning/Sprint-Structure.md

File renamed without changes.

docs/devops-practices/continuous-planning/agile-development/Stand-Ups/Social-Question.md renamed to docs/devops-practices/continuous-planning/agile-development/stand-ups/Social-Question.md

File renamed without changes.

docs/devops-practices/continuous-planning/agile-development/Team-Agreements/Definition-of-Done.md renamed to docs/devops-practices/continuous-planning/agile-development/team-agreements/Definition-of-Done.md

File renamed without changes.

0 commit comments

Comments
 (0)