- Foundation
- 30 min
- 7 min read
After this lesson you can
- Say what each week of the learning path is for and how long it takes.
- Tell which items are core reading and which are long, optional courses.
- Use the three-lines rule after every item.
- Find the skill track that matches your week.
Read these first
The learning path is a free-first list of reading, documentation, videos and courses. It has two tracks. Track A (plan the whole product) matches the four planning weeks of the Developer level. Track B (platform and GitOps) matches the four weeks of the Master Developer level. This page is the map. The lists themselves are on Plan the product, the Platform track and Optional paid courses.
Why it matters
A list of 66 links is not a plan. A week-by-week map tells you what to read first, how long it takes, and what to skip. It also protects you from the most common mistake: spending a month on a certificate and not building anything.
The rules of the path
- Do the items of each week in order.
- After each item, write three lines in your own words about how it changes your product. Reading and watching are not enough.
- Free first. Almost everything is free reading or documentation. Where there is a cost, the list says so.
- Certificates are optional. A certificate shows you know the words. Your roadmap and your capstone show you can do the job.
- Every link was checked. Each address was opened with an automated check and kept only if it answered successfully. Sites that block automated tools are not listed, and we never bypass a wall.
- Prices change. Always confirm on the provider’s site before you pay.
- Skip duplicates. If you already finished a foundation course on the same topic, for example agile or GitLab project management, skip the repeat.
Track A: plan the product
| Week | Focus | Items and hours (about) | What dominates the time |
|---|---|---|---|
| 1: See the whole product | Roadmaps, epics, personas, journeys, GitLab epics | 8 items, 3.4 hours | Short articles and documentation |
| 2: Know the people | Roadmaps as problems to solve, journeys versus flows, personas, GitLab roadmap and milestones, the Scrum Guide | 7 items, 3.5 hours | Short articles and documentation |
| 3: From problems to epics | User research, GitLab training, agile course, cloud basics | 8 items, 78.5 hours | A few long optional courses. The core reading is only a few hours. |
| 4: Defend the roadmap | Certificates, architecture guides, multi-customer products, microservices | 9 items, 259 hours | Optional long certificates. The architecture reading is about 5 hours. |
Week 3 and week 4 totals look large because they include long optional courses and certificates. You do not need to finish them. Pick the short items first and add a long course only when you want it.
Track B: platform and GitOps
| Week | Focus | Items and hours (about) |
|---|---|---|
| 1: The company platform | Portal tools, the cloud-native landscape, GitOps principles, a GitOps delivery tool, a registry, security findings, update bots | 7 items, 4.5 hours |
| 2: The OSS-first ladder and licences | Licence summaries, approved lists, short licence ids, contribution guides, a licence-per-file convention, software bills of materials, project health checks, a scanner | 8 items, 5 hours |
| 3: Patch-forks, infrastructure as code, GitOps and drift | Sync policies, getting started with a delivery tool, declarative infrastructure, overlays, packages, secrets in git without exposing values | 10 items, 15 hours |
| 4: Service management on our stack and capstone preparation | Service management frameworks, merge trains, code owners, service levels, error budgets, blameless reviews, how to send a patch upstream, a database operator | 9 items, 25.5 hours |
The Master Developer weeks are mostly documentation and are much shorter. Read the documents. Then do the exercise in git. See Deck 10 to Deck 16.
Long courses and the honest notes
- Long courses. A full project-management certificate from a large course provider takes about six months. In Track A week 3 only its agile course fits.
- Courses with fees. A research-methods course, a GitLab exam and cloud exams may have fees. Check the provider.
- Project-management and Scrum bodies block automated tools. For those we list official handbooks only. They may be dated, so confirm current rules and fees on the provider’s own site.
- One certificate is deliberately not listed: a professional Scrum certificate, because its pages could not be verified.
- Do not copy answers. Reading is not the exercise.
Which skill track matches your week
Use the skill tracks for depth. Only tracks that exist are linked.
Topics the lists cover
Agile and product certifications; cloud fundamentals and architecture; GitLab epics and roadmaps; GitOps; service management; infrastructure as code; open source and licences; patch-forks; the platform (portal and catalogue); the platform (registry and security); product management and roadmapping; reliability and service levels; software-as-a-service architecture; user and customer journey mapping and personas.
Steps for each week
- Open the week’s list and pick the shortest three items.
- Read or watch one item. Write three lines in your own words.
- Do the week’s exercise in your own repository.
- Add a long item only if you have time and want it.
- Write the weekly note, including your AI use line.
Working with AI agents
- May: explain a word from a reading, summarise a long page so you can read the original faster.
- May not: write your three lines, or answer the exercise. The point is that you change your own product.
- A safe brief: “Explain what a ‘service level objective’ is in four sentences. Give one example. Do not apply it to my product.”
Common mistakes
- Reading everything. Pick three.
- Starting with the longest course.
- Reading without writing the three lines.
- Paying before reading the provider’s current page.
- Using a certificate as proof of the work.
Practice
- Choose three items for this week. Write the hours.
- Read one and write three lines about how it changes your product.
- Find the skill track for your week and read its first lesson.
Checklist
- I chose items for this week and know the hours.
- I wrote three lines after each item.
- I checked any price on the provider’s site.
- I did the exercise in git.
The 2030 Product Development Manager lens
- You decide: which items you read and what changes in your product.
- You delegate to agents: summaries of long pages so you can read the original faster, checking that links still open.
- A sample brief: “Open each link in this list and report the HTTP status and title. Do not summarise the pages.”
- You verify by: reading one source page yourself before relying on a summary.
- Disciplines involved: product, engineering, platform, finance and operations.
- On the agent ladder: the path trains use first, then the platform weeks train delegate, orchestrate and govern.
Further learning
Start with how to use the learning path. Then go to Plan the product or the Platform track.
Go deeper
Further learning
Free or low-cost material from other publishers. We opened every link; check the cost label before you start.
Atlassian
Product Roadmap Guide: What is it & How to Create One (opens the publisher's site in a new tab)
- Free
- Article
- Beginner
A step-by-step guide to what a product roadmap is, the common formats and the questions it must answer. Read it before you write your own roadmap so you know the standard shapes and can explain why you chose one.
GitLab
Epics (opens the publisher's site in a new tab)
- Free
- Docs
- Intermediate
GitLab's documentation for epics, which group related issues across projects. Check the page for which GitLab tier includes the feature before you rely on it. On the free plan, use labelled issues instead.
GitLab
Roadmap (opens the publisher's site in a new tab)
- Free
- Docs
- Intermediate
GitLab's roadmap view draws epics and milestones on a timeline. Read it to see the shape of a roadmap view, and check which tier offers it.
GitLab
Milestones (opens the publisher's site in a new tab)
- Free
- Docs
- Beginner
Explains GitLab milestones: dated goals that group issues and merge requests, with progress tracking. Milestones are how you give dates to a plan on the free plan.
OpenGitOps (CNCF)
OpenGitOps (opens the publisher's site in a new tab)
- Free
- Docs
- Beginner
States the four GitOps principles: declarative, versioned, pulled automatically and continuously reconciled. A short page that gives the idea in a few lines. Read it first, then the tool docs.
Google
Google SRE Book: Service level objectives (opens the publisher's site in a new tab)
- Free
- Book
- Intermediate
Defines SLIs, SLOs and SLAs and shows how to choose them. It gives the vocabulary for the service level sheet in the capstone. Read the first sections for the definitions.
SPDX
SPDX License List (opens the publisher's site in a new tab)
- Free
- Docs
- Beginner
The reference list of short licence identifiers such as MIT and Apache-2.0. These identifiers are what you write in a licence check record. Use it as a lookup, not as reading material.
Scrum.org
Scrum Guide (opens the publisher's site in a new tab)
- Free
- Docs
- Beginner
The official, short definition of Scrum by its creators: the accountabilities, events and artifacts, and the commitments behind them. It is the source other guides interpret, and reading the original once is worth it.



