Most engineering teams have no shared definition of “knows Git”. People arrive with wildly
different models, the gaps only surface during an incident, and onboarding is a link to some
documentation and a hope.
This is the programme and the paperwork to fix that.
30-day programme — four weeks (the model; working on a branch; working with the team;
CI/CD and security), each with reading, a lab and a checkpoint the learner and manager both see.
Ends with guidance on adapting it.
Every team tier includes the toolkit — the CODEOWNERS, pull
request and issue templates, five workflow templates, decision guides and repository checklists
the programme’s weeks refer to.
Editable throughout: Markdown for documents, CSV for the assessment, YAML for
workflow templates. Nothing is locked to a proprietary format, and everything is intended to be
adapted to your organisation rather than adopted verbatim.
Before buying, find out where your team stands. The
Git & GitHub Team Readiness Assessment is twelve questions,
takes five minutes, scores in your browser and points at the lessons that address each gap.
Payment is through the checkout provider’s hosted page; the receipt and download link arrive by
email, usually within minutes. The download is one archive with the ten team files and the
toolkit. First week: the manager reads manager/manager-checklist.md (“Before day 1”), runs
the skills assessment with the team, and picks the start date. The 30-day programme begins from
there. Questions about running it: contact us.
More than 50 engineers, or several teams?Enterprise licensing is
agreed directly.
The whole curriculum, all the labs and the learning paths are free and complete. Run a team
through a learning path first. If that works for you and the missing piece is structure,
assessment and standards documents, this is that piece. If it does not work for you, this will not
fix it.
Learning pathsThe sequenced routes this programme is built around. Free.
Hands-on labsThe practical exercises the programme uses. Free.
ContactQuestions about licensing or Enterprise terms.
Frequently asked questions
How is this different from the Professional Toolkit?
The toolkit is files for one engineer — templates and checklists to drop into repositories. This is a programme for a group: a four-week curriculum, an assessment to find where each person actually is, a standards document the team agrees to, and the checklists a manager runs it with. Every team tier includes the toolkit.
Is there an instructor, live session or support contract?
No. It is a programme you run yourself, built on the free lessons and labs. The manager checklist is the run-book.
What does the assessment measure?
Nineteen skills across six areas — Git model, branching, pull requests, GitHub, CI/CD and security — each at three levels. The scoring guide explains how to run it fairly, how to read the results and how to turn gaps into a plan. It is a CSV, so it drops into a spreadsheet.
How is it licensed?
By organisation and seat count: Small Team covers up to 10 engineers, Engineering Team up to 50. The Engineering Team tier includes editable source so the standards document can become your internal document. Larger organisations are handled on enquiry.
Can we see the material before buying?
The curriculum sequences the free learning paths and labs, so the substance is all public. The team readiness assessment is a free, shorter version of the skills assessment's approach. What you cannot see beforehand is the standards template and the manager checklists.
What is the refund policy?
Refund terms are stated in the Terms and at checkout.