PD

Learning Objectives

  • Collaborate on defining what will be your Minimum Viable Product (MVP)

Preparation

Ensure your team has done all the prep work

Introduction

When product teams work together, having a good planning and preparation session ensures everyone is on the same page and knows how to collaborate best. It means you might not be coding much today, but learning how to do this work will make you a better software developer and ensure you develop features that generate user value.

Exercises

What is expected of your product (45 minutes)

Goal: Understand what an MVP (Minimum viable product) is and the key qualities of your product.

Discuss and agree on the points below with your product team.

Minimum Viable Product (MVP)

  1. What is an MVP (Minimum Viable Product)?
  2. How can you avoid increasing scope?
  3. How do we define what should be part of the MVP?

Functionalities

  1. What does it mean for your website to be interactive? 
  2. The product must be completed in four weeks of work. How can we ensure the scope is the right size?
  3. Be well-defined: what artefacts can we use to ensure all functionalities are well-defined?
  4. Visual Design Complexity: how can we avoid making our visuals too complex?
  5. Answers to questions: trainees are learning, so how can we, as a team, learn without giving each other just the answers - or expecting immediate answers from your peers?

Define your product (60 minutes)

Goal: Define your product and features

To ensure we can keep the scope lean and everyone understands the product, briefing and features the same way, follow these steps:
\

  1. Work on this Lean UX Canvas on this Miro board, Exercise 3.1

  2. Do a user story mapping (an example is on the same Miro board, Exercise 3.2)

  3. Define the features that will be included in your MVP.