Program guide

Why the program exists and who it is for

What a Master Developer is, why we teach whole-product planning, who should join, and how the program fits with the free foundation track that comes before it.

  • Foundation
  • 30 min
  • 6 min read

After this lesson you can

  • Explain in two sentences what a Master Developer does and why it matters.
  • Say who the program is for and what you should already be able to do.
  • Describe how the foundation track and this program fit together.
  • State the one idea behind the program: the human owns the idea and the roadmap, agents build.

Read these first

You may already know how to build parts of a product: a front end, some full stack, a chat with an AI agent. Those skills let you build parts. This program teaches the skill many builders do not have yet: seeing how every piece of a product ties together, and owning the plan for the whole product.

Why it matters

A single repository is easy to hold in your head. A real product is not one repository. It has a public website, an app, small cloud services, a payment gateway, a customer database, and the people who use all of it. An AI agent works on one task in one place at a time. It does not know what the customer said on the phone last week, what the sales team promised, or what money is left. A person who can hold the whole picture is rare and valuable.

That person is the Master Developer.

What a Master Developer is

A Master Developer orchestrates across many repositories. They steer AI agents to build products that work across several disciplines and make customers happy. Two sentences carry the whole job:

  • The human owns the idea and the epic roadmap.
  • The agents build the repositories.

An agent can turn a clear milestone into issues and code very well. An agent cannot hold a whole product in its head. That is your job.

Who it is for

The program is for people who can already make parts of a product and want to see how everything ties together.

You are Good fit? Why
A front-end or full-stack builder who works with AI agents Yes You can build parts; you now learn to plan the whole
A product or project person early in your career Yes You know the words; you now use them on a real product
Someone who has finished the free foundation track Yes This is the next step
Someone who wants a certificate without doing the work No Your roadmap and your capstone are the proof, not a certificate
Someone who wants an agent to write the plan for them No The one rule of the program forbids it

You do not need to finish the foundation track first. You can start while you finish it. If you already did a course on the same topic, such as agile or GitLab project management, skip the duplicate.

How it fits with the foundation track

The free foundation track teaches the tools and the words. This program asks you to use them on a whole product, with real repositories, real customers and real agents.

Foundation track This program
The question it answers Do I know the tools and the words? Can I own a whole product’s plan?
Shape A set of short courses over about 12 weeks, in five areas: product sense, iteration, launch and experience, orchestration, tooling Hands-on weeks on one real product
Evidence Provider certificates and screenshots of finished courses Workbooks, epics in git, a defended roadmap
Planning Learning items on a board Your product’s epics, milestones and roadmap
Coach Walk the board with a coach A weekly checkpoint and a final review

Key ideas

  • Parts versus whole. Building a part is a skill. Owning the whole is a different skill.
  • Humans decide, agents build. This is the rule that organises the rest.
  • Evidence over certificates. A certificate shows you know the words. A defended roadmap shows you can do the job.
  • Real product, real customers. You work on one product, not a toy exercise. A fictional product (TrailMug) is used in the pages to show the shape.

Steps to start

  1. Read the 2030 Product Development Manager for the big picture.
  2. Read the two levels and the capstone.
  3. Read the five rules of The Way.
  4. Choose a product. Write one paragraph about it, yourself.
  5. Start Week 1.

Working with AI agents

  • May: explain a word you do not know, summarise a long document so you can read the original faster, check spelling after you write.
  • May not: choose your product, write your idea paragraph, or tell you what the whole product is. You must look at it yourself.
  • A safe brief: “Explain in plain words what an epic is in agile planning. Give two examples. Do not write one for my product.”

Common mistakes

  1. Treating this as a coding course. The planning is the course.
  2. Skipping the “whole product” idea and describing one repository.
  3. Believing a certificate is the goal.
  4. Picking a product you cannot talk to customers about.
  5. Letting an agent write the idea paragraph.

Practice

  1. Write two sentences on what a Master Developer does, in your own words.
  2. List the parts of one product you know beyond its main app.
  3. Say in one sentence why an agent cannot own the plan.

Checklist

  • I can explain the job in two sentences.
  • I know what I should already be able to do.
  • I know the rule: people write epics, agents build.
  • I have picked a product.

The 2030 Product Development Manager lens

  • You decide: which product, what it is for, and what the whole looks like.
  • You delegate to agents: reading documents, listing repositories, drafting issues from milestones you wrote.
  • A sample brief: “List every repository in this group with its description. Do not guess how they connect.”
  • You verify by: opening two of them and checking the description against the code.
  • Disciplines involved: product, engineering, design, marketing, sales, finance and operations.
  • On the agent ladder: this program moves you from use towards delegate, orchestrate and govern.

Further learning

Continue with the two levels and the capstone. Read the roadmap standard to see what you will write.

Go deeper

Further learning

Free or low-cost material from other publishers. We opened every link; check the cost label before you start.

  • Atlassian

    Epics (opens the publisher's site in a new tab)

    • Free
    • Article
    • Beginner

    Atlassian's explanation of epics: large bodies of work broken into smaller stories. Note that Atlassian's meaning of epic is looser than the Dojo's, which crosses several parts of a product. Compare the two and be ready to say how they differ.

  • Silicon Valley Product Group

    SVPG: Product roadmaps (opens the publisher's site in a new tab)

    • Free
    • Article
    • Intermediate

    An experienced product coach explains why roadmaps often fail and what a useful one looks like. It gives a view that challenges simple feature lists. Read it critically and compare with this program's outcome-based epics.

  • 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.

  • Anthropic

    Building effective AI agents (opens the publisher's site in a new tab)

    • Free
    • Article
    • Intermediate

    An engineering essay on the difference between workflows and agents, and on the simple patterns that work: prompt chaining, routing, parallelisation and evaluator loops. It argues for the simplest design that works. Read it before you give an agent a big job.

Back to the library