Facilitated By Tox. B.

You don’t need to write code to understand what your engineers mean when they talk about branches, merges, and pull requests — and understanding it makes you a far more effective partner to the technical team. This session demystifies Git for non-engineers.

We’ll cover the core concepts (repositories, branches, commits, merges, pull requests) at a conceptual level, how Git workflows map to sprint and release planning, and the vocabulary you need to follow a technical conversation without getting lost.

Learning Objectives

Understand core Git concepts without needing to write a single command.
Learn how branching strategies affect release planning and risk.
Build a shared vocabulary for participating in technical conversations.
Recognize how Git workflows connect to Definition of Done and CI/CD.

Who Should Attend?

Scrum Masters, Product Owners, and Project Managers who work with engineering teams but don’t have a technical background.

Key Takeaways

A working, non-technical understanding of Git concepts.
Vocabulary to follow (and contribute to) engineering conversations.
A clearer picture of how version control affects release risk and timing.