Developer path

Week 6: Catalogue, demo and final package

Write your Product Catalogue, record a demo, and present your Product Package.

Outcome: you present a complete Product Package and show evidence that you managed your epics.

Part 1: Product Catalogue

The Product Catalogue standard describes your product in four layers: Master, ORBITAL, ANDROID and Tech. This week you write at least the Master Catalogue well, and a short version of the others.

Also write one catalogue entry per product or service. See Catalogue entry.

Rules:

  • Record only what you verified. Use “Not confirmed” when you do not know.
  • Mark each item FOUND, NOT FOUND or PLANNED.
  • Never put passwords or keys in the catalogue.

Part 2: The demo

A demo shows the product working. Keep it to five minutes.

  1. Say who the user is and what problem she has.
  2. Show the journey from start to finish. Use fake data.
  3. Show one thing that is not finished yet and say so.
  4. End with the next epic and why it comes next.

Record the demo as a short video or prepare a live walk-through. Do not show real customer data.

Part 3: Evidence of complete epic management

Collect proof that you managed the plan:

  • Your epics, with history, in git.
  • Dates that were moved and the reason in a comment.
  • Your decision log.
  • Your weekly notes.
  • Milestones closed with evidence.
  • Your AI-use notes.

Part 4: Present your Product Package

Use the Product Package standard. Present for 15 minutes, then answer questions. Self-score with the rubric first.

Exercises

  1. Finish the Master Catalogue. Short versions of the other three.
  2. Write catalogue entries.
  3. Rehearse the demo twice.
  4. Assemble the Product Package folder in git.
  5. Present. Write down every question you could not answer.

After the presentation

Your coach or panel scores you. If you reach level 3 on every skill, you have passed the Developer path. Next: the Master Developer rank.

Back to the library