📗
Processes
  • Intro
  • Getting Started
    • Your first day
    • General work ethic
    • Important contacts
    • Important Links
    • Team Communication
    • Remote work code of conduct
  • Product processes
    • Roles & Responsibilities
    • Meeting Structure
      • 1:1 Meetings
      • Design Kick-Off
      • Design Review
      • Dev Kick-Off
      • Estimation Meeting
    • How to Introduce a Feature
    • Writing Effective User Stories
    • Writing a Design Overview
    • Prioritization (with RICE)
    • How to roughly estimate as PM & Designer
    • Design Sprints
      • Setup/ Preparations
      • Monday
      • Tuesday
      • Wednesday
      • Thursday
      • Friday
      • Sprint Decision Making Process
      • Recruiting customers for Friday's interviews
    • Project Management - Product, Dev and Design
    • Definition of Ready (for development)
  • Stakeholder requests
  • Submit a Bug Report or Feature Request
  • Data Protection: User Deletion Requests
  • Testing structure
    • Testing mobile
    • Manual Regression Tests
  • Technology
    • Development Process
Powered by GitBook
On this page
  • Basics
  • Goal

Was this helpful?

  1. Product processes
  2. Meeting Structure

Dev Kick-Off

The goal of dev kick-offs is to introduce upcoming features to the dev team. During the meeting, they have the opportunity to ask questions to understand the issue better and to challenge assumptions & motivation. Lastly, the goal is to split the feature into several work packages (stories in clubhouse) that can be built and estimated separately.

Basics

Frequency: Ad-hoc

Duration: As short as possible

Participants: PM, Designer, Devs

Goal

1. Introduce new feature

  • Inform about upcoming product features:

    1. Which screen(s) are affected

    2. User journey changes

    3. Design changes

    4. The motivation for the changes

    5. Assumption/ design tests completed

  • Developers can challenge assumption & motivation and ask questions to understand better

2. Split feature into separate stories

  • Split feature into separate stories and create tickets in clubhouse

  • Create work packages for front-end and back-end

  • Pre-sort into must-have and nice-to-have features

  • Get a very rough estimation

PreviousDesign ReviewNextEstimation Meeting

Last updated 4 years ago

Was this helpful?