Skip to content

Commit e9b4ad5

Browse files
committed
added Collaborations page
added and updated 'Collaborations' page, under 'Agil Development' section. [Ticket: X] Signed-off-by: Scott McCarthy <scott.mccarthy@opencastsoftware.com>
1 parent 13cd5d3 commit e9b4ad5

3 files changed

Lines changed: 3 additions & 93 deletions

File tree

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

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,6 @@
11

22
# Collaboration
33

4-
[[_TOC_]]
5-
64
## Why collaboration is important
75

86
In engagements, we aim to be highly collaborative because when we code together, we perform better, have a higher sprint velocity, and have a greater degree of knowledge sharing across the team.
@@ -25,7 +23,7 @@ Below are some general guidelines for pairing:
2523
- Engineers leverage feature branches for the collaboration during the development of each story to have small Pull Requests (PRs) (as opposed to a single giant PR) at the end of the sprint.
2624
- Code is committed to the repository by both members of the assigned pair where and when it makes sense as tasks were completed.
2725
- The pairing assignee is the voice representing the pair during the daily standup while being supported by the story owner.
28-
- Having the names of both individuals (owner and pair assignee) visible on the PBI can be helpful during sprint ceremonies and lead to greater accountability by the pairing assignee. An example of this using Azure DevOps cards can be found [here](./Collaboration/Add-Pairing-Field-Azure-Devops-Cards.md).
26+
- Having the names of both individuals (owner and pair assignee) visible on the PBI can be helpful during sprint ceremonies and lead to greater accountability by the pairing assignee.
2927

3028
## Why pair programming helps collaboration
3129

@@ -75,8 +73,6 @@ Knowledge sharing and bringing customer engineers together in a ‘code-with’
7573

7674
## Resources
7775

78-
- [How to add a pairing custom field in Azure DevOps User Stories](./Collaboration/Add-Pairing-Field-Azure-Devops-Cards.md) - adding a custom field of type _Identity_ in Azure DevOps for pairing
79-
8076
- [On Pair Programming - Martin Fowler](https://martinfowler.com/articles/on-pair-programming.html)
8177

82-
- [Pair Programming hands-on lessons](https://github.com/The-V8/pair-programming-sessions) - these can be used (and adapted) to support bringing pair programming into your team (MS internal or including customers)
78+
- [Pair Programming hands-on lessons](https://github.com/The-V8/pair-programming-sessions) - these can be used (and adapted) to support bringing pair programming into your team.

docs/devops-practices/continuous-planning/agile-development/Collaboration/Add-Pairing-Field-Azure-Devops-Cards.md

Lines changed: 0 additions & 87 deletions
This file was deleted.

mkdocs.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -74,6 +74,7 @@ nav:
7474
- Agile Development:
7575
- What is is Agile: devops-practices/continuous-planning/agile-development/whatis-agile.md
7676
- Backlog Management: devops-practices/continuous-planning/agile-development/backlog-management.md
77+
- Collaboration: devops-practices/continuous-planning/agile-development/collaboration.md
7778

7879
- Tools:
7980
- devops-tools/tools-overview.md

0 commit comments

Comments
 (0)