Dev Bootcamp · Berlin · 24 November 2026 · 1 day

Building the Agentic R&D Organization. One day, hands-on, as a team.

Building the Agentic R&D Organization. One day, hands-on, as a team.

Building the Agentic R&D Organization. One day, hands-on, as a team.

How Product, Design and Engineering work when everyone can build. You leave with the operating model for your own product team.

Save your seats

See the agenda

See the agenda

Limited seats. Bring your team.

Building session during our first Dev Bootcamp

Building session during our first Dev Bootcamp

Tue, 24 Nov 2026

09:00–18:00. A short setup check one week before.

Delta Campus, Berlin

All meals and drinks included. Limited seats.

From €999

Team ticket for 3 seats at €2,499. 100 % sponsor-free.

Jira, Figma and GitHub were never just tools. They were territories.

Jira, Figma and GitHub were never just tools. They were territories.

Product had Jira. Design had Figma. Engineering had GitHub. Agents move those borders.

Old way

New way

Click to see the new way.

OLD WAY

PRODUCT

Jira

Ticket

DESIGN

Figma

Spec

ENGINEERING

GitHub

Software

Each function had its own room. The tool flow became the org flow.

A PM could write a requirement but couldn’t build. A designer could go deep in Figma but couldn’t change the app. Engineering got defined inputs and turned them into software.

Product → Design → Engineering. With all the handoffs, tickets, specs and waiting that come with it.

Old way

New way

Click to see the new way.

OLD WAY

PRODUCT

Jira

Ticket

DESIGN

Figma

Spec

ENGINEERING

GitHub

Software

Each function had its own room. The tool flow became the org flow.

A PM could write a requirement but couldn’t build. A designer could go deep in Figma but couldn’t change the app. Engineering got defined inputs and turned them into software.

Product → Design → Engineering. With all the handoffs, tickets, specs and waiting that come with it.

Old way

New way

Click to see the new way.

OLD WAY

PRODUCT

Jira

Ticket

DESIGN

Figma

Spec

ENGINEERING

GitHub

Software

Each function had its own room. The tool flow became the org flow.

A PM could write a requirement but couldn’t build. A designer could go deep in Figma but couldn’t change the app. Engineering got defined inputs and turned them into software.

Product → Design → Engineering. With all the handoffs, tickets, specs and waiting that come with it.

We asked Claude to draw this.

Yeah we know. We are nerds :)

FIG. 01 — SILOS → ONE LAYER

MADE WITH CLAUDE

6 blocks. One operating model.

01

Why R&D silos existed

Why Jira, Figma and GitHub became separate rooms. What those borders protected, and what they cost you every sprint.

02

What agents change

Which skills move between roles right now. What a PM can do alone today. What a designer can try directly in the product. What changes for engineers when the input is a prototype instead of a spec.

03

Work directly on a product

We bring a realistic sample product. Your cross-functional group takes one problem from idea to working feature in a single agentic workflow. No brief, no ticket, no handoff.

04

Define the new boundaries

The core of the day. Your group maps the product into 3 zones: experimentation, review, protected. You decide who may change what, and what needs a gate.

05

Build the shared agentic layer

Agent rules, product context, design principles, architecture constraints, coding standards, testing requirements, security rules, deployment policies. Written once, used by every agent on the team.

06

Design your Agentic R&D operating model

Who may change what. What can be tried without asking. Which handoffs disappear. Where ownership stays. Which quality gates apply. What agents take over, and which decisions stay human on purpose.

Come as a team. That’s the point.

Come as a team. That’s the point.

The best version of this day is 1 PM, 1 designer and 2 or 3 engineers from the same product team. You work through the day together, and the operating model you build is already shared when you’re back at your desks.

Solo tickets work too. You’ll join a cross-functional group for the day.

Product Manager

Product Designer

Engineering Manager

Tech Lead

Senior Developer

Software Architect

Product Engineer

Head of Product

Head of Engineering

PRODUCT & DESIGN

No coding experience required for product and design roles.

You work with agents on the same product as the engineers, with scope adapted to your role.

Three zones. Your team draws the lines.

Three zones. Your team draws the lines.

Zone 1 – Experimentation

ZONE 1

Experimentation

Product, design and engineering change things on their own, with agents. Fast, cheap, reversible.

Open to everyone

Zone 2 – Review

ZONE 2

Review

Everyone can make changes. They need a functional or technical review before they ship.

Review before ship

Zone 3 – Protected

ZONE 3

Protected

Clear ownership. Changes need stronger approval, and some things never deploy automatically.

Ownership and gates

Every team draws these lines differently. You leave knowing where yours go.

One day, mostly hands-on.

Four hands-on blocks on one sample product. Your group builds, maps, writes and decides. The room challenges the result.

01

Understand

09:30 · Why silos existed, what agents do to them.

02

Build

10:45 · One feature, idea to working product.

03

Decide

13:30 · Zones, agentic layer, operating model.

09:00

Arrival, setup check, coffee

09:30

Opening

Why R&D silos existed, and what agents do to them.

10:15

Reality check

Where do handoffs cost your team time today?

10:45

Hands-on 1 · Work directly on the product

Cross-functional groups take one problem from idea to working feature on our sample product, agent-first.

12:30

Lunch

13:30

Hands-on 2 · Define the new boundaries

The product in 3 zones: experimentation, review, protected.

14:45

Hands-on 3 · Build the shared agentic layer

Rules, context and constraints your agents actually follow.

16:00

Hands-on 4 · Your Agentic R&D operating model

Who changes what, which handoffs go, which gates stay.

17:00

Showcase

Each group presents its model, the room challenges it.

17:45

Commit & close

Built by people who run product teams this way.

Built by people who run product teams this way.

alphalist is Germany’s no. 1 CTO community and organizer of the code.talks developer conference. The trainers run agentic product teams themselves and built the DEV Bootcamp Hamburg curriculum.

✓

Limited seats, cross-functional groups.

✓

Claude Code, Codex and Cursor all work.

✓

100 % sponsor-free. Made by practitioners, for practitioners.

Teams they’ve already worked with

  • IONOS

  • eventim

  • dm

  • Picnic

  • OTTO

  • adesso

  • Breuninger

  • Krombacher

  • bonprix

  • Blume2000

  • SIGNAL IDUNA

  • LichtBlick

  • XING

  • blau direkt

  • EGYM

  • Infoniqa

Stefan Munz

Stefan Munz

Trainer & Curriculum Lead

Hosted the first agentic coding meetup in Hamburg in July 2025, probably the first in Germany. Co-founded hackers & wizards with Benedikt in 2026.

Benedikt Stemmildt

Benedikt Stemmildt

Curriculum Lead

20+ years in enterprise engineering at OTTO and BLUME2000. Founder of hackers & wizards. Program Chair of code.talks.

Tereza Iofciu

Tereza Iofciu

AI & Agentic Engineering Coach

PhD in Computer Science. 15+ years leading data and AI teams at neuefische, FREE NOW and New Work (XING).

Bootcamp group at the beer garden
Hands-on session
Discussion at the bootcamp

Product describes less. Design simulates less. Engineering translates less. Everyone gets closer to the product.

Product describes less. Design simulates less. Engineering translates less. Everyone gets closer to the product.

What you leave with: Templates, files and a model your team can apply to your own product the next day.

A working zone model

Experimentation, review, protected, and how to map your own product onto it.

A shared agentic layer template

Rules, context and constraints as files, ready to adapt and commit.

A draft operating model for your team

Who changes what, which handoffs go, which gates stay.

One feature built together

From idea to working product, without a single handoff.

The starter kit

CLAUDE.md, rules, skills, MCP configs.

A 90-day rollout template

For the rest of your org.

Bring the whole team.

One product team, one price. Solo seats welcome too.

Team working together at the bootcamp

TEAM TICKET · RECOMMENDED

€2,499

net · 3 seats

Each additional seat €799. One product team, one price.

Save your seats

SINGLE TICKET

€999

net · 1 seat

Each additional seat €799. You join a cross-functional group for the day.

Save your seat

Included in both

✓

All sessions and 4 hands-on blocks

✓

Starter kit and 90-day rollout template

✓

All meals and drinks

✓

alphalist community access

Group of 5 or more? Write to sebastian@alphalist.com.

Group of 5 or more? Write to sebastian@alphalist.com.

100 % sponsor-free. Made by practitioners, for practitioners.

100 % sponsor-free. Made by practitioners, for practitioners.

Before you book.

Before you book.

I’m a PM or designer and I don’t code. Can I take part?

Do we work on our own codebase?

Can I come alone?

What do we need to bring?

Which tools do we use?

We were at the DEV Bootcamp in Hamburg. Is this the same?

One day. Your team.
Your new operating model.

One day. Your team.
Your new operating model.

One day. Your team.
Your new operating model.

Save your seats

Not this time? Get notified about the next bootcamp.