Technology & security
Git & Collaborative Development
Build an evidence-led Git & Collaborative Development foundation you can explain in a real workplace or interview.
Use version control to collaborate safely on technical work.
About this course
Learn repository setup, focused commits, branching, merging, conflict resolution, pull requests, code review, tagging, release discipline and collaborative documentation.
Career relevance
Where this can take you
Designed for learners exploring technology careers and building a practical, honest portfolio.
Portfolio project: Create a Git & Collaborative Development capstone pack that documents your purpose, method, evidence, quality check and next action.
Skills you will gain
Practical skills, not just theory
What you will learn
Understand the core workflow behind git & collaborative development.
Create practical evidence using controlled, workplace-ready methods.
Make evidence-led decisions, communicate limitations and escalate appropriately.
Present a portfolio-ready capstone and development plan.
Objective map
A numbered, measurable syllabus
Every lesson, knowledge check and practical activity maps to the objectives below. Domain weights show how much of the programme each area represents.
Domain 1
Git & Collaborative Development: role and foundations to Focused commits
- 1.1Complete and defend git & collaborative development: role and foundations in a realistic git & collaborative development context: establish the purpose, professional boundaries and workplace context for git & collaborative development.
- 1.2Demonstrate repository setup in a realistic git & collaborative development context: apply repository setup to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
- 1.3Demonstrate focused commits in a realistic git & collaborative development context: apply focused commits to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
Domain 2
Branching to Conflict resolution
- 2.1Demonstrate branching in a realistic git & collaborative development context: apply branching to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
- 2.2Demonstrate merging in a realistic git & collaborative development context: apply merging to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
- 2.3Demonstrate conflict resolution in a realistic git & collaborative development context: apply conflict resolution to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
Domain 3
Pull requests to Tagging
- 3.1Demonstrate pull requests in a realistic git & collaborative development context: apply pull requests to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
- 3.2Analyse and evaluate code review in a realistic git & collaborative development context: apply code review to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
- 3.3Demonstrate tagging in a realistic git & collaborative development context: apply tagging to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
Domain 4
Release discipline to Integrated Git & Collaborative Development workflow
- 4.1Demonstrate release discipline in a realistic git & collaborative development context: apply release discipline to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
- 4.2Complete and defend collaborative documentation in a realistic git & collaborative development context: apply collaborative documentation to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
- 4.3Complete and defend integrated git & collaborative development workflow in a realistic git & collaborative development context: connect the programme topics into one controlled workflow with clear inputs, checks, handover points and escalation boundaries.
How the programme works
Learn, practise, explain and prove it
This is a long-form, eight-week guided programme rather than a stack of short articles. Each module contains six substantial lessons that move from concepts and methods into a worked case, a quality clinic, a workplace lab and assessed reflection.
1. Guided learning
Study the purpose, process, risks and professional standard through structured readings and active notes.
2. Worked cases
Compare plausible options, expose missing evidence and defend a decision under realistic constraints.
3. Quality clinics and labs
Diagnose weak work, revise it against a rubric and create portfolio evidence with a full audit trail.
4. Hard assessment
Pass applied checks and the final assessment at 85%, with no unresolved critical-error questions.
Curriculum
A complete programme, module by module
The curriculum below shows the actual learning pathway, objective and evidence for every module. Full lessons remain locked until enrolment.
Build the base
Standards, vocabulary and the core method you will use throughout the programme.
01Git & Collaborative Development: role and foundationsEstablish the purpose, professional boundaries and workplace context for git & collaborative development.+
Measured objectiveComplete and defend git & collaborative development: role and foundations in a realistic git & collaborative development context: establish the purpose, professional boundaries and workplace context for git & collaborative development.
Evidence you will produceA technical git & collaborative development: role and foundations brief with requirements, safe method, sample output or architecture, validation evidence and handover notes.
Six guided lessons + worked case + quality clinic + workplace lab + hard knowledge check
02Repository setupApply repository setup to a realistic git & collaborative development brief, documenting the decision, evidence and next action.+
Measured objectiveDemonstrate repository setup in a realistic git & collaborative development context: apply repository setup to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
Evidence you will produceA technical repository setup brief with requirements, safe method, sample output or architecture, validation evidence and handover notes.
Six guided lessons + worked case + quality clinic + workplace lab + hard knowledge check
03Focused commitsApply focused commits to a realistic git & collaborative development brief, documenting the decision, evidence and next action.+
Measured objectiveDemonstrate focused commits in a realistic git & collaborative development context: apply focused commits to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
Evidence you will produceA technical focused commits brief with requirements, safe method, sample output or architecture, validation evidence and handover notes.
Six guided lessons + worked case + quality clinic + workplace lab + hard knowledge check
Milestone: You can explain the fundamentals and complete a first guided task.
Develop core skills
The working skills and tools of the role, practised one at a time.
04BranchingApply branching to a realistic git & collaborative development brief, documenting the decision, evidence and next action.+
Measured objectiveDemonstrate branching in a realistic git & collaborative development context: apply branching to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
Evidence you will produceA technical branching brief with requirements, safe method, sample output or architecture, validation evidence and handover notes.
Six guided lessons + worked case + quality clinic + workplace lab + hard knowledge check
05MergingApply merging to a realistic git & collaborative development brief, documenting the decision, evidence and next action.+
Measured objectiveDemonstrate merging in a realistic git & collaborative development context: apply merging to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
Evidence you will produceA technical merging brief with requirements, safe method, sample output or architecture, validation evidence and handover notes.
Six guided lessons + worked case + quality clinic + workplace lab + hard knowledge check
06Conflict resolutionApply conflict resolution to a realistic git & collaborative development brief, documenting the decision, evidence and next action.+
Measured objectiveDemonstrate conflict resolution in a realistic git & collaborative development context: apply conflict resolution to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
Evidence you will produceA technical conflict resolution brief with requirements, safe method, sample output or architecture, validation evidence and handover notes.
Six guided lessons + worked case + quality clinic + workplace lab + hard knowledge check
Milestone: You can carry out routine work independently and check it properly.
Apply it in realistic scenarios
Case studies and simulations with competing priorities and incomplete information.
07Pull requestsApply pull requests to a realistic git & collaborative development brief, documenting the decision, evidence and next action.+
Measured objectiveDemonstrate pull requests in a realistic git & collaborative development context: apply pull requests to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
Evidence you will produceA technical pull requests brief with requirements, safe method, sample output or architecture, validation evidence and handover notes.
Six guided lessons + worked case + quality clinic + workplace lab + hard knowledge check
08Code reviewApply code review to a realistic git & collaborative development brief, documenting the decision, evidence and next action.+
Measured objectiveAnalyse and evaluate code review in a realistic git & collaborative development context: apply code review to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
Evidence you will produceA technical code review brief with requirements, safe method, sample output or architecture, validation evidence and handover notes.
Six guided lessons + worked case + quality clinic + workplace lab + hard knowledge check
09TaggingApply tagging to a realistic git & collaborative development brief, documenting the decision, evidence and next action.+
Measured objectiveDemonstrate tagging in a realistic git & collaborative development context: apply tagging to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
Evidence you will produceA technical tagging brief with requirements, safe method, sample output or architecture, validation evidence and handover notes.
Six guided lessons + worked case + quality clinic + workplace lab + hard knowledge check
Milestone: You can make and justify decisions in realistic situations.
Prove it and plan your next step
Portfolio evidence, final review and a development plan you can show an employer.
10Release disciplineApply release discipline to a realistic git & collaborative development brief, documenting the decision, evidence and next action.+
Measured objectiveDemonstrate release discipline in a realistic git & collaborative development context: apply release discipline to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
Evidence you will produceA technical release discipline brief with requirements, safe method, sample output or architecture, validation evidence and handover notes.
Six guided lessons + worked case + quality clinic + workplace lab + hard knowledge check
11Collaborative documentationApply collaborative documentation to a realistic git & collaborative development brief, documenting the decision, evidence and next action.+
Measured objectiveComplete and defend collaborative documentation in a realistic git & collaborative development context: apply collaborative documentation to a realistic git & collaborative development brief, documenting the decision, evidence and next action.
Evidence you will produceA technical collaborative documentation brief with requirements, safe method, sample output or architecture, validation evidence and handover notes.
Six guided lessons + worked case + quality clinic + workplace lab + hard knowledge check
12Integrated Git & Collaborative Development workflowConnect the programme topics into one controlled workflow with clear inputs, checks, handover points and escalation boundaries.+
Measured objectiveComplete and defend integrated git & collaborative development workflow in a realistic git & collaborative development context: connect the programme topics into one controlled workflow with clear inputs, checks, handover points and escalation boundaries.
Evidence you will produceA technical integrated git & collaborative development workflow brief with requirements, safe method, sample output or architecture, validation evidence and handover notes.
Six guided lessons + worked case + quality clinic + workplace lab + hard knowledge check
Milestone: You have portfolio-ready evidence and a clear next step.
Suggested pace
Eight-week study plan
Plan for roughly 5–9 hours each week across readings, worked cases, practice, portfolio production and assessment remediation. Repeat a week when the knowledge checks show a gap.
Week 1
Git & Collaborative Development: role and foundations to Repository setup
- •Complete the six guided lessons for Git & Collaborative Development: role and foundations and Repository setup and build structured notes against the objective codes.
- •Analyse the worked case, compare two defensible options and submit a reasoned decision record.
- •Complete the quality clinic, correct the weak draft and document every revision against the rubric.
- •Produce the git & collaborative development: role and foundations and repository setup portfolio evidence and complete the hard knowledge checks.
- •Review every incorrect answer, explain why each distractor fails and schedule targeted retrieval practice.
Checkpoint: Reach at least 85% on the week’s checks, resolve every critical error and save the reviewed portfolio evidence before continuing.
Week 2
Focused commits
- •Complete the six guided lessons for Focused commits and build structured notes against the objective codes.
- •Analyse the worked case, compare two defensible options and submit a reasoned decision record.
- •Complete the quality clinic, correct the weak draft and document every revision against the rubric.
- •Produce the focused commits portfolio evidence and complete the hard knowledge checks.
- •Review every incorrect answer, explain why each distractor fails and schedule targeted retrieval practice.
Checkpoint: Reach at least 85% on the week’s checks, resolve every critical error and save the reviewed portfolio evidence before continuing.
Week 3
Branching to Merging
- •Complete the six guided lessons for Branching and Merging and build structured notes against the objective codes.
- •Analyse the worked case, compare two defensible options and submit a reasoned decision record.
- •Complete the quality clinic, correct the weak draft and document every revision against the rubric.
- •Produce the branching and merging portfolio evidence and complete the hard knowledge checks.
- •Review every incorrect answer, explain why each distractor fails and schedule targeted retrieval practice.
Checkpoint: Reach at least 85% on the week’s checks, resolve every critical error and save the reviewed portfolio evidence before continuing.
Week 4
Conflict resolution
- •Complete the six guided lessons for Conflict resolution and build structured notes against the objective codes.
- •Analyse the worked case, compare two defensible options and submit a reasoned decision record.
- •Complete the quality clinic, correct the weak draft and document every revision against the rubric.
- •Produce the conflict resolution portfolio evidence and complete the hard knowledge checks.
- •Review every incorrect answer, explain why each distractor fails and schedule targeted retrieval practice.
Checkpoint: Reach at least 85% on the week’s checks, resolve every critical error and save the reviewed portfolio evidence before continuing.
Week 5
Pull requests to Code review
- •Complete the six guided lessons for Pull requests and Code review and build structured notes against the objective codes.
- •Analyse the worked case, compare two defensible options and submit a reasoned decision record.
- •Complete the quality clinic, correct the weak draft and document every revision against the rubric.
- •Produce the pull requests and code review portfolio evidence and complete the hard knowledge checks.
- •Review every incorrect answer, explain why each distractor fails and schedule targeted retrieval practice.
Checkpoint: Reach at least 85% on the week’s checks, resolve every critical error and save the reviewed portfolio evidence before continuing.
Week 6
Tagging
- •Complete the six guided lessons for Tagging and build structured notes against the objective codes.
- •Analyse the worked case, compare two defensible options and submit a reasoned decision record.
- •Complete the quality clinic, correct the weak draft and document every revision against the rubric.
- •Produce the tagging portfolio evidence and complete the hard knowledge checks.
- •Review every incorrect answer, explain why each distractor fails and schedule targeted retrieval practice.
Checkpoint: Reach at least 85% on the week’s checks, resolve every critical error and save the reviewed portfolio evidence before continuing.
Week 7
Release discipline to Collaborative documentation
- •Complete the six guided lessons for Release discipline and Collaborative documentation and build structured notes against the objective codes.
- •Analyse the worked case, compare two defensible options and submit a reasoned decision record.
- •Complete the quality clinic, correct the weak draft and document every revision against the rubric.
- •Produce the release discipline and collaborative documentation portfolio evidence and complete the hard knowledge checks.
- •Review every incorrect answer, explain why each distractor fails and schedule targeted retrieval practice.
Checkpoint: Reach at least 85% on the week’s checks, resolve every critical error and save the reviewed portfolio evidence before continuing.
Week 8
Integrated Git & Collaborative Development workflow
- •Complete the six guided lessons for Integrated Git & Collaborative Development workflow and build structured notes against the objective codes.
- •Analyse the worked case, compare two defensible options and submit a reasoned decision record.
- •Complete the quality clinic, correct the weak draft and document every revision against the rubric.
- •Produce the integrated git & collaborative development workflow portfolio evidence and complete the hard knowledge checks.
- •Review every incorrect answer, explain why each distractor fails and schedule targeted retrieval practice.
Checkpoint: Submit the capstone evidence pack, defend the key decision, remediate every weak objective and pass the final assessment at 85% with no critical misses.
Technology & security
Continue your learning path
AI for Work & Prompting
Use generative AI responsibly to research, write, analyse and improve everyday work.
60–72 hours
AI Product Management
Plan responsible AI-enabled products around people, value and risk.
50–60 hours
API & Integration Foundations
Understand how systems exchange information safely and reliably.
55–66 hours
Assessment and certificate
A scenario-led git & collaborative development case, practical portfolio review and final knowledge assessment. It is a UGEN ACADEMY completion record, not an external professional credential.
Who this is for
- ✓Learners exploring technology careers.
- ✓Job seekers building practical git & collaborative development evidence.
- ✓Professionals developing a structured new capability.