Training course · GitHub Copilot · Tech Leads & Engineering Managers

GitHub Copilot for Tech Leads and Engineering Managers

Use GitHub Copilot professionally: completions, chat, agent mode, the coding agent for issues and PRs, code review and enterprise policies.

Duration
2 days (14 hrs)
Format
Online or on-site
Language
German or English
Participants
open dates or exclusive for your team
Certificate
Certificate of attendance

Overview

This course connects GitHub Copilot with the everyday processes of Tech Leads & Engineering Managers. Participants work on realistic scenarios and leave with prompts, workflows and checklists they can use straight away.

GitHub Copilot has grown from simple code completion into a broad AI platform that supports the entire development lifecycle. In the editor you work with inline suggestions, next edit suggestions and Copilot Chat; in agent mode Copilot handles tasks across multiple files and runs commands. On GitHub itself, the coding agent picks up assigned issues and delivers pull requests. In this two-day course you will learn how to use each of these building blocks deliberately and fit them cleanly into your existing development process.

Beyond hands-on editor work, the course covers control and quality. Custom instructions and prompt files give Copilot the project knowledge it needs, MCP adds further tools, and Copilot code review complements human reviewers. For those responsible for teams and organisations, we look at policies at organisation and enterprise level, content exclusions, model availability and usage reporting. Together, these lay the groundwork for a secure, transparent and genuinely effective Copilot rollout across the entire company.

AI coding assistants and autonomous agents are changing how engineering teams work: tasks are sliced differently, effort shifts from writing code to reviewing it, and deciding which work can be delegated to agents becomes a leadership responsibility. Tech leads and engineering managers have to select tools, set policies, enable their teams and measure impact without losing sight of code quality, security and the growth of junior engineers. In this course you learn to plan the rollout of AI coding tools in a structured way, establish shared working practices and rule files for your team, choose meaningful metrics beyond raw speed and apply AI to leadership tasks such as planning, onboarding and technical communication. Deep programming skills are not required.

The course is delivered live – either online in a virtual classroom or on-site in our training rooms in Munich, Salzburg, Berlin, Augsburg, Hanover, Bremen, Stuttgart and Kaiserslautern. We can also run it exclusively for your team.

Who is this course for?

  • Tech leads and lead developers
  • Engineering managers and software team leads
  • Heads of engineering and CTOs in mid-sized companies
  • Delivery and project leads in IT organisations
  • Developer experience and enablement leads

Typical challenges we address

  • Unclear policies lead to a patchwork of tools and shadow AI within the team
  • More generated code increases review load and the risk of technical debt
  • Difficulty measuring the real benefit of AI tools in a credible way
  • Concerns about junior engineers’ skill development and team buy-in

What you will be able to do

  • You use Copilot completions, chat and agent mode purposefully for your everyday development tasks.
  • You capture project knowledge in custom instructions and prompt files to improve output quality.
  • You delegate suitable issues to the coding agent and review its pull requests properly.
  • You integrate Copilot code review sensibly into your existing review process.
  • Plan the rollout of AI coding tools in a structured way with clear policies, roles and guardrails.
  • Measure the impact on delivery, quality and satisfaction with credible metrics.
  • Use AI agents yourself for leadership tasks such as planning, onboarding and technical communication.

Course outline

Day 1

Module 1 Copilot in the editor: completions and chat
  • Accepting, rejecting and steering inline and next edit suggestions efficiently
  • Using Copilot Chat for explanations, debugging and test generation
  • Setting context precisely with files, selections, workspace and chat variables
  • Model selection and differences between VS Code, Visual Studio and JetBrains IDEs
Module 2 Agent mode and extensions
  • Planning multi-step tasks in agent mode and executing them under control
  • Feeding terminal commands, test runs and error output into the agent loop
  • Connecting MCP servers for additional tools and data sources
  • Reviewing changes, accepting them partially or rolling them back
Module 3 Project knowledge through custom instructions
  • Writing repository-wide instructions on architecture, style and testing
  • Creating path-specific instructions and reusable prompt files
  • Combining personal and organisation-wide guidance sensibly
  • Refining instructions continuously based on output quality
Module 4 Coding agent and code review on GitHub
  • Writing issues the coding agent can implement reliably
  • Reviewing, commenting on and iterating over the agent’s pull requests
  • Using Copilot code review as an additional check in the PR process
  • Configuring the agent’s development environment with setup steps and Actions

Day 2

Module 5 Administration, policies and security
  • Licence assignment and policies at organisation and enterprise level
  • Content exclusions, model availability and public code filters
  • Using audit logs and usage metrics to steer adoption
  • Clarifying security risks, secrets and accountability for AI-generated code
Module 6 Practice lab: Tech Leads & Engineering Managers
  • Writing a team AI policy
  • Rule files and team conventions
  • Measuring impact
  • Slicing work for agents
  • Faster onboarding
  • Technical communication
Module 7 Data protection, quality & transfer to daily work
  • As a leader you own the legal framework: you learn to address licensing and copyright questions around generated code, protection of source code and secrets, works council co-determination rights when measuring performance and obligations under the GDPR and the EU AI Act in your team policies.
  • Ground rules for safe AI use in your team
  • Checking results: facts, sources, tests and the four-eyes principle
  • Personal action plan for the next 30 days
  • Open questions, outlook and resources for further learning

Practical scenarios from your field

Writing a team AI policy

Draft a practical guideline that clearly defines approved tools, permitted data classes, review obligations for generated code, handling of secrets and accountabilities, illustrated with concrete examples.

Rule files and team conventions

Build shared context files for coding agents covering architectural principles, testing strategy, style rules and banned patterns, keep them under version control and ensure consistent output across the team.

Measuring impact

Collect metrics such as DORA measures, pull request cycle time, change failure rate and developer satisfaction before and after rollout, and prepare the analysis with AI support.

Slicing work for agents

Write and break down backlog items so they can be delegated to agents with clear acceptance criteria, and decide which tasks deliberately stay with people.

Faster onboarding

Prepare codebases, architecture decisions and operational knowledge for new team members, create guided exploration tasks and have questions about the codebase answered with source references.

Technical communication

Draft incident post-mortems, roadmap updates, decision papers for senior management and release notes from tickets and commits, structured and tailored to each audience. This frees up time for actual leadership.

Possible hands-on projects

Team metrics dashboard

A small web app that pulls data from your Git platform and shows cycle times, review duration and deployment frequency over time.

PR summariser

A bot that collects all merged pull requests each week and turns them into a readable status report for stakeholders.

Onboarding guide generator

A script that analyses repository structure, README files and ADRs and produces a structured onboarding plan with learning tasks. It adapts to role and seniority.

Prerequisites

You develop software regularly, work with Git and GitHub issues and pull requests, and use a modern IDE. You lead a software team, either technically or as a line manager, and understand the development process; current hands-on coding is helpful but not required.

Technical requirements

Your own laptop with VS Code or a JetBrains IDE, the Copilot extension installed and a GitHub account with an active Copilot licence; the coding agent requires a suitable plan.

Data protection & compliance

As a leader you own the legal framework: you learn to address licensing and copyright questions around generated code, protection of source code and secrets, works council co-determination rights when measuring performance and obligations under the GDPR and the EU AI Act in your team policies.

Suggested dates

All dates are suggestions – your preferred date is always possible.

  • Mon, 23 November 2026 – Tue, 24 November 2026 Online Request
  • Tue, 1 December 2026 – Wed, 2 December 2026 Augsburg Request
  • Mon, 14 December 2026 – Tue, 15 December 2026 Online Request
  • Thu, 14 January 2027 – Fri, 15 January 2027 Online Request
  • Mon, 25 January 2027 – Tue, 26 January 2027 Bremen Request
  • Mon, 8 February 2027 – Tue, 9 February 2027 Online Request

Frequently asked questions

What is the difference between agent mode and the coding agent?

Agent mode runs inside your IDE: you work interactively with Copilot, see every step and approve commands. The coding agent, by contrast, works autonomously on GitHub once you assign it an issue, uses its own execution environment and opens a pull request that you then review just as you would a contribution from a colleague.

How can we make sure Copilot complies with our company policies?

At organisation and enterprise level you can enable or block specific features, models and extensions. Content exclusions keep sensitive files out of the context, and audit logs make usage traceable. During the course we show how to align these controls with data protection, information security requirements and your internal coding standards.

Is the course worthwhile if we already use Copilot?

Yes, especially then. Many teams rely on completions alone and barely touch chat, agent mode, custom instructions or the coding agent. The course shows how to use these features in a structured way, improve results with project knowledge and avoid common pitfalls. Experienced users benefit most from the sections on review and governance.

How do we tell whether AI coding tools are worth it?

Don’t count generated lines of code; look at outcomes: lead time from idea to production, change failure rate, review effort, defect rates and team satisfaction. A baseline before rollout and accompanying qualitative surveys are essential. In the course you design a lean measurement approach that fits your organisation and involves employee representatives.

Do junior engineers still learn enough when AI writes the code?

The concern is valid and can be managed. Proven practices include having engineers explain every generated section in review, deliberate practice phases without an assistant and pairing with experienced colleagues where AI acts as a learning partner. You learn to adapt learning paths and review culture so that skill building and productivity go hand in hand.

How much does “GitHub Copilot for Tech Leads and Engineering Managers” cost?

The course costs a flat €949 plus VAT per participant – whether online or on-site. This includes 2 training day(s) with a live trainer, course materials, a lab environment and a certificate of attendance.

Can I suggest my own date?

Yes. Our suggested dates are just a guide. In the request form you can always describe your preferred date or period in free text – we check availability and confirm within one working day.

Is the course online or on-site?

Both are possible: live online in a virtual classroom or on-site in Munich, Salzburg, Berlin, Augsburg, Hanover, Bremen, Stuttgart or Kaiserslautern. We can also run the course exclusively for your team.

More courses for Tech Leads and Engineering Managers

More GitHub Copilot courses

All 32 GitHub Copilot courses

GitHub Copilot · MunichGitHub Copilot · SalzburgGitHub Copilot · BerlinGitHub Copilot · AugsburgGitHub Copilot · HanoverGitHub Copilot · BremenGitHub Copilot · StuttgartGitHub Copilot · KaiserslauternGitHub Copilot · Online