You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/wwl-azure/manage-azure-boards-using-github-copilot/includes/1-introduction.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,10 @@
1
1
Modern agile teams increasingly use Azure Boards as their planning system while relying on GitHub Copilot to accelerate implementation. This module shows how to make those tools work together so teams can move faster without losing governance, quality, or visibility.
2
2
3
+
A common customer scenario we see today is DevOps teams using **Azure DevOps Boards** as the **system of record** for project and work management - planning epics, tracking user stories, managing backlogs, and aligning delivery to business priorities while relying on **GitHub Copilot** as their primary generative AI assistant inside the developer workflow. With the **new integration** between Azure DevOps Boards and GitHub Copilot, these two worlds now come together seamlessly: developers can work in GitHub and their IDE with Copilot while staying fully connected to the work items, acceptance criteria, and priorities defined in Azure Boards. Copilot can surface context from linked work items, helping developers generate more relevant code, tests, and comments that directly map back to tracked requirements, while updates and progress remain visible to project managers in Azure DevOps. The result is a **unified experience** where planning and governance stay centralized in Azure DevOps Boards, AI-powered coding productivity lives in GitHub, and teams no longer have to choose between strong project management and modern, generative AI–driven development—they get both, working together by design.
4
+
3
5
## Why this integration matters
4
6
5
-
When planning and delivery tools are disconnected, teams lose context and spend time translating requirements between systems. Integrating Azure Boards with GitHub and Copilot helps teams:
7
+
When planning and delivery tools are disconnected, teams lose context and spend time translating requirements between systems. Integrating Azure Boards with GitHub and GitHub Copilot helps teams with:
6
8
7
9
- Keep work tracking in Azure Boards while coding stays in GitHub.
8
10
- Give Copilot better context through clearer work items.
@@ -11,7 +13,7 @@ When planning and delivery tools are disconnected, teams lose context and spend
11
13
12
14
## What you learn in this module
13
15
14
-
You learn how to connect Azure Boards to GitHub, prepare Copilot-ready work items, delegate implementation, and supervise AI-assisted pull requests using human-in-the-loop review.
16
+
You learn how to connect Azure Boards to GitHub, prepare Copilot-ready work items, delegate implementation, and supervise AI-assisted pull requests using **human-in-the-loop** review.
15
17
16
18
## Learning objectives
17
19
@@ -31,3 +33,6 @@ Before you begin, confirm:
31
33
-[ ] You can access a GitHub repository and create pull requests.
32
34
-[ ] Your environment has GitHub Copilot capabilities enabled.
33
35
-[ ] You understand your team's review and merge policy.
36
+
37
+
> [!IMPORTANT]
38
+
> To complete this GitHub Copilot training, you must have an active subscription for both Azure DevOps and GitHub Copilot, or you must be assigned to a subscription managed by an organization or enterprise. The GitHub Copilot Free Subscription is not compatible with Azure Boards integration.
Copy file name to clipboardExpand all lines: learn-pr/wwl-azure/manage-azure-boards-using-github-copilot/includes/10-maintain-traceability-boards.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,8 @@ One of the biggest benefits of this integration is end-to-end traceability. Azur
2
2
3
3
## Traceability chain
4
4
5
+
Traceability means anyone can follow the lifecycle of a requirement from idea to shipped change. In this workflow, every important step should connect back to the original work item. This is valuable for project tracking, compliance reviews, onboarding, and retrospectives.
6
+
5
7
An effective chain connects:
6
8
7
9
- Work item intent and acceptance criteria.
@@ -11,6 +13,8 @@ An effective chain connects:
11
13
12
14
## Keep links useful
13
15
16
+
Links are only useful when they are consistent and meaningful. Teams should use common conventions so work items and pull requests stay easy to understand over time.
17
+
14
18
Use consistent team practices so links stay meaningful:
15
19
16
20
- Ensure each delegated item maps to one primary pull request when possible.
@@ -19,6 +23,8 @@ Use consistent team practices so links stay meaningful:
19
23
20
24
## Reporting and visibility
21
25
26
+
When traceability is clean, reporting becomes much easier for both technical and non-technical stakeholders. You can answer questions about status, quality, and ownership without manual reconstruction from chat messages or memory.
27
+
22
28
With clean linking, project and engineering leaders can:
23
29
24
30
- Review sprint progress with implementation evidence.
@@ -28,8 +34,14 @@ With clean linking, project and engineering leaders can:
28
34
29
35
## Practical anti-patterns
30
36
37
+
Most traceability problems come from shortcuts, such as broad pull requests or manual status updates with no supporting artifacts. Avoiding these anti-patterns keeps dashboards and board views trustworthy.
38
+
31
39
- Merging broad pull requests that cover many unrelated work items.
32
40
- Updating work item state manually without code artifact links.
33
41
- Closing items before review and test completion.
34
42
35
43
Traceability is strongest when planning, coding, and review stay connected throughout the lifecycle.
44
+
45
+
## Summary
46
+
47
+
End-to-end traceability is a core benefit of integrating Azure Boards with GitHub workflows. By maintaining clear links and avoiding common shortcuts, teams gain better reporting, better accountability, and more reliable delivery insights.
Copy file name to clipboardExpand all lines: learn-pr/wwl-azure/manage-azure-boards-using-github-copilot/includes/11-apply-governance-security.md
+19-5Lines changed: 19 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,8 @@ AI-assisted delivery should accelerate work without weakening governance. Define
2
2
3
3
## Governance baseline
4
4
5
+
Governance is the framework that ensures speed does not reduce quality, security, or accountability. For learners, a useful perspective is to view governance as "guardrails" that allow safe experimentation while preventing high-impact mistakes.
6
+
5
7
Establish policy in three layers:
6
8
7
9
-**Access controls**: Least-privilege permissions in Azure DevOps and GitHub.
@@ -10,13 +12,17 @@ Establish policy in three layers:
10
12
11
13
## Security practices for delegated work
12
14
15
+
Security expectations should be explicit before delegation begins. Copilot can generate helpful implementation ideas, but teams are still responsible for protecting credentials, sensitive data, and compliance boundaries.
16
+
13
17
- Avoid including secrets, tokens, or sensitive data in prompts.
14
18
- Keep identity, credential, and infrastructure tasks human-approved.
15
19
- Require security review for authentication and authorization changes.
16
20
- Enforce dependency and code scanning in the PR pipeline.
17
21
18
22
## Responsible AI usage
19
23
24
+
Responsible AI usage means deciding where automation is appropriate and where human control is mandatory. Not all tasks have the same risk profile, and high-impact decisions still require experienced judgment.
25
+
20
26
Teams should define where Copilot is preferred and where human ownership is mandatory.
21
27
22
28
Examples of human-led areas:
@@ -27,9 +33,17 @@ Examples of human-led areas:
27
33
28
34
## Governance scorecard
29
35
30
-
Use a lightweight monthly scorecard:
36
+
Use a lightweight scorecard to measure whether your governance approach is working. These metrics help you assess if AI assistance is improving outcomes while keeping risk under control.
37
+
38
+
Track these metrics monthly in **both Azure DevOps (work item analytics) and GitHub (pull request insights)**:
39
+
40
+
-**Percentage of Copilot-assisted PRs that passed first review** — Measure in GitHub; track approval rate without rework requests.
41
+
-**Average rework cycles per delegated item** — Monitor in Azure DevOps (work item history) and GitHub (PR revision count).
42
+
-**Security issues introduced or prevented** — Review in GitHub (code scanning results in PRs) and Azure DevOps (security task tracking).
43
+
-**Lead time change relative to non-assisted baseline** — Calculate in Azure DevOps (cycle time reports) and correlate with GitHub PR merge times.
44
+
45
+
Use Azure DevOps dashboards for organizational rollup and GitHub for PR-level detail. Align review gates in both systems to ensure consistent governance enforcement.
46
+
47
+
## Summary
31
48
32
-
- Percentage of Copilot-assisted PRs that passed first review.
33
-
- Average rework cycles per delegated item.
34
-
- Security issues introduced or prevented.
35
-
- Lead time change relative to non-assisted baseline.
49
+
Strong governance and security practices are essential for sustainable AI-assisted delivery. By applying clear guardrails, explicit security rules, and outcome-based metrics, teams can scale Copilot usage confidently without losing control.
Copy file name to clipboardExpand all lines: learn-pr/wwl-azure/manage-azure-boards-using-github-copilot/includes/12-drive-adoption-improvement.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,8 @@ Sustainable adoption depends on measurable outcomes, not just tool enablement. S
2
2
3
3
## Pilot-to-scale approach
4
4
5
+
Adoption works best as a progression, not a one-time rollout. A pilot lets teams learn with low risk, then apply those lessons before expanding to more repositories and teams. This approach prevents common issues such as inconsistent templates, unclear expectations, or uncontrolled process variation.
6
+
5
7
Use a phased rollout:
6
8
7
9
1.**Pilot** with one team and a narrow work-item type (for example, bug fixes).
@@ -10,6 +12,8 @@ Use a phased rollout:
10
12
11
13
## Metrics that matter
12
14
15
+
If you only measure speed, quality can decline. If you only measure quality, teams may not see delivery benefits. Track both dimensions together so you can evaluate whether adoption is actually improving outcomes.
16
+
13
17
Track both speed and quality:
14
18
15
19
- Cycle time from work item start to merge.
@@ -19,6 +23,8 @@ Track both speed and quality:
19
23
20
24
## Build team capability
21
25
26
+
Capability growth is a major part of adoption. Teams need shared language, examples, and coaching so contributors at different experience levels can write better work items and review AI-assisted pull requests effectively.
27
+
22
28
Improve results through deliberate enablement:
23
29
24
30
- Run short workshops on writing Copilot-ready work items.
@@ -28,6 +34,8 @@ Improve results through deliberate enablement:
28
34
29
35
## Continuous improvement loop
30
36
37
+
Continuous improvement means treating each sprint as a feedback cycle. You are not only delivering features; you are also improving how your team collaborates with Copilot.
38
+
31
39
At the end of each sprint:
32
40
33
41
- Identify where Copilot created clear acceleration.
@@ -36,3 +44,7 @@ At the end of each sprint:
36
44
- Re-test and compare metrics in the next sprint.
37
45
38
46
This approach turns integration into a repeatable delivery capability.
47
+
48
+
## Summary
49
+
50
+
Long-term adoption succeeds when teams combine phased rollout, balanced metrics, and regular coaching. By measuring outcomes and refining practices each sprint, you can turn AI-assisted delivery into a stable and scalable team capability.
Copy file name to clipboardExpand all lines: learn-pr/wwl-azure/manage-azure-boards-using-github-copilot/includes/2-integration-overview.md
+39-2Lines changed: 39 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,35 @@
1
+
<!-- DOCUMENTATION COMMENT -->
2
+
This section introduces the integration between Azure Boards and GitHub Copilot, which allows teams to combine two powerful capabilities:
3
+
4
+
1.**Azure Boards** - Acts as the central planning hub where teams define, prioritize, and organize work items (like user stories, tasks, and bugs) in a structured backlog.
5
+
6
+
2.**GitHub Copilot** - An AI-powered coding assistant that helps developers write, understand, and complete code more efficiently during implementation.
7
+
8
+
**Key Points:**
9
+
-**Single Source of Truth**: Azure Boards maintains the authoritative backlog and work priorities. This ensures everyone knows what needs to be done and in what order.
10
+
-**Streamlined Workflow**: Instead of switching between multiple tools, developers can reference work items from Azure Boards while coding in GitHub, and Copilot can help accelerate the implementation.
11
+
-**Better Collaboration**: This integration creates a transparent link between planning (what needs to be built) and coding (how it's being built), improving team communication.
12
+
13
+
**Simple Analogy**: Think of Azure Boards as your team's to-do list and GitHub Copilot as an intelligent assistant who helps you complete those tasks faster.
1
14
Azure Boards and GitHub Copilot integration combines structured planning with AI-assisted delivery. Azure Boards remains the source of truth for backlog hierarchy and prioritization, while GitHub and Copilot streamline implementation and collaboration.
2
15
3
16
## Core workflow model
4
17
5
-
In a typical flow:
18
+
In a typical flow, we refer to the end-to-end process of how users interact with Azure Boards through GitHub Copilot integration, starting from initial setup and configuration, moving through the daily workflow of creating and managing work items, and culminating in the synchronization of changes back to the repository. This flow encompasses several key phases: first, the user establishes the connection between their GitHub repository and Azure Boards project, ensuring that Copilot has the necessary permissions and context to interact with both systems. Next, as developers write code and make commits, Copilot intelligently assists in creating work items, linking code changes to existing tasks, and updating item statuses based on the development activities. Finally, the system maintains bidirectional synchronization so that any updates made in Azure Boards—such as priority changes, status transitions, or new task assignments—are reflected in the development context, creating a seamless feedback loop between planning and execution.
19
+
20
+
The flow could be represented like this:
21
+
22
+
```mermaid
23
+
flowchart TD
24
+
A[Define work items in Azure Boards<br/>epics, features, stories, bugs, tasks]
C[Refine work items for clarity<br/>and implementation readiness]
27
+
D[Use GitHub Copilot for analysis,<br/>code generation, and PR creation]
28
+
E[Human review for quality,<br/>security, and test coverage]
29
+
F[Traceability in Azure Boards<br/>from plan to code]
30
+
31
+
A --> B --> C --> D --> E --> F
32
+
```
6
33
7
34
1. Product and engineering teams define epics, features, user stories, bugs, and tasks in Azure Boards.
8
35
2. Teams connect the project to GitHub repositories.
@@ -13,6 +40,8 @@ In a typical flow:
13
40
14
41
## Role alignment
15
42
43
+
Clear role definition ensures accountability and leverages each team member's strengths. In the Azure Boards and GitHub integration, each role has distinct responsibilities that collectively enable efficient planning-to-delivery workflows. Product owners focus on vision and prioritization, team leads ensure quality and organization, developers drive implementation with AI assistance, reviewers maintain standards, and project managers provide visibility. This structured collaboration prevents bottlenecks, ensures that Copilot suggestions receive appropriate human oversight, and maintains traceability across the entire delivery lifecycle.
44
+
16
45
| Role | Main responsibility in this integration |
17
46
| --- | --- |
18
47
| Product owner | Prioritize and clarify desired outcomes in Boards |
@@ -21,7 +50,9 @@ In a typical flow:
21
50
| Reviewer | Validate correctness, risks, and standards |
22
51
| Project manager | Track progress and outcomes through linked artifacts |
23
52
24
-
## Outcomes you should expect
53
+
## Expected Outcomes
54
+
55
+
By integrating Azure Boards with GitHub and leveraging Copilot assistance, teams achieve measurable improvements in delivery efficiency and quality. These outcomes demonstrate the value of connecting planning artifacts directly to implementation, ensuring visibility across the entire workflow while maintaining human oversight of AI-generated suggestions.
25
56
26
57
- Faster cycle time for clearly scoped work.
27
58
- Better implementation consistency when criteria are explicit.
@@ -35,3 +66,9 @@ Copilot accelerates implementation, but it doesn't replace planning accountabili
35
66
- Well-defined requirements and acceptance criteria.
36
67
- Review and testing discipline.
37
68
- Clear governance for permissions and merge policies.
69
+
70
+
> [!IMPORTANT]
71
+
> **Why manual review remains critical:** While Copilot can generate code quickly, human reviewers provide essential oversight that AI cannot replicate. Reviewers catch logical errors, security vulnerabilities, performance issues, and ensure code aligns with team standards and business requirements. They also validate that generated solutions actually satisfy the original work item's acceptance criteria. This human judgment layer prevents technical debt, maintains code quality, and ensures accountability—making review an irreplaceable part of the workflow, not a bottleneck to bypass.
72
+
73
+
## Summary
74
+
This section covered the foundational elements of integrating Azure Boards with GitHub Copilot. You learned how this integration combines structured planning in Azure Boards with AI-assisted development in GitHub Copilot to streamline workflows. The core workflow model demonstrates the end-to-end process from defining work items through code review and traceability. Role alignment ensures accountability across product owners, team leads, developers, reviewers, and project managers. Expected outcomes highlight measurable improvements in cycle time, consistency, visibility, and handoffs. Finally, integration boundaries clarify that while Copilot accelerates implementation, human oversight, clear requirements, and testing discipline remain essential for maintaining quality and accountability.
0 commit comments