Join the next voyage
The Standard Voyage

Seven weeks. One team. One shipped product.

A remote, cross-functional team sprint. Developers, a designer, a Scrum Master and a Product Owner. Matched across timezones, building a real product you can put on your portfolio and your resume.

Join the next Voyage →
The seven-week arc

From kickoff to demo day.

  1. Wk 0

    Team formation

    You’re matched with a cross-functional team. Intros. Agree on a working rhythm across your timezones. First standup.

  2. Wk 1

    Sprint planning

    Scope the product together. Backlog comes together. Definition of done, negotiated. The Figma starts taking shape.

  3. Wk 2

    Build starts

    First PRs open. First design handoff. First “wait, does your API actually return that shape?” conversation.

  4. Wk 3–4

    The messy middle

    Merge conflicts. Timezone juggling. Someone’s feature breaks someone else’s. The team either gels here or it doesn’t. Usually it gels.

  5. Wk 5

    Final sprint

    Polish, bugs, acceptance. The PO says “ship it or cut it.” The team ships.

  6. Wk 6

    Demo day

    Demo to the cohort. Retrospective with your team. A live product, a repo under your name, and teammates you’ll still talk to next year.

How a team comes together

Cross-functional by default.

3–5 Developers

A mix of backend, frontend, full-stack, or app. Self-select on tech stack.

1 Designer

UX, UI, or Product. Leads research, design system, and handoff.

1 Scrum Master and 1 Product Owner

Run scrum events, keep scope constrained and unblock the team.

Tools & rhythm

The same stacks real teams use.

  • GitHub. Feature branches, PR review, merge workflows.
  • Discord. Async team channels, daily standups, office hours.
  • Jira or GitHub Projects. Backlog, sprints, story points.
  • Figma. Design file, prototypes, dev handoff.
  • ~10 hours a week. Two standups, one sync, async around your schedule.
  • Daily standups. Regular progress reports on Discord.
  • 1 retro / sprint. What worked, what didn’t, what we’re trying next.
  • A laptop and reliable internet. That’s the hardware floor.
“Six weeks flew by. We built, shipped, argued (productively), and grew into a tight remote team. I’m proud of what we accomplished — and grateful for the people who made it happen.”
Alexander MakoveevWeb Developer · Voyage alum
No Git experience?

Half our members arrive the same way.

50% of surveyed members started a Voyage without Git experience. We cover branching, PRs, and merge conflicts in context — because that’s how everyone on a real team learns them. If you can build something solo, you’re ready.

The next cohort opens soon.

Join the community on Discord and get the latest updates on upcoming voyages and events.

Join for free today →

No credit card needed.