Week 10: MVP scoping and implementation planning#
Studio abstract#
In this studio, your team will use its Iteration 2 learning to define an evidence-based MVP scope, plan the first implementation work, and consider which workflows or repository skills may support Iteration 3.
The activities total 140 minutes and begin after the 30-minute innovation seminar and a 10-minute transition.
By the end of the studio, your team should have:
identified the important assumption its MVP will test;
described and prioritised a set of concrete MVP features;
agreed the initial MVP scope using MoSCoW;
allocated the first implementation tasks, with an owner and deadline for each;
ensured that every team member has a meaningful coding task;
outlined one workflow or repository skill that may support Iteration 3; and
started the first implementation work.
1. Review Iteration 2 learning#
⏱️ 20 minutes — team
Begin with the evidence and decisions already recorded in your repository. Review your:
accepted, refuted and unresolved hypotheses;
solution-testing evidence;
learning cards;
Business Model Canvas and Value Proposition Canvas; and
competitor analysis.
Agree on the most important assumption that the MVP now needs to test. Write a short statement that identifies:
the customer or early adopter;
the problem or need;
the value the MVP is intended to provide; and
what the team still needs to learn.
Do not begin with a list of features. Begin with the evidence and the assumption the team needs to test.
2. Define and scope the MVP features#
⏱️ 35 minutes — team
Describe the concrete features that could allow the team to test its important assumption. For each proposed feature, record:
Field |
Team decision |
|---|---|
Feature |
What can the user do? |
Evidence |
Which earlier evidence or learning supports it? |
Hypothesis |
What assumption will this feature help test? |
Priority |
Must have, Should have, Could have, or Will not have in this MVP? |
Use MoSCoW to define the initial scope:
Must have: required for the MVP to provide and test its core value;
Should have: important, but the MVP can still test its core assumption without it;
Could have: useful only if time and capacity remain; and
Will not have: deliberately excluded from this MVP.
Keep the Must-have list small. The goal is not to capture every feature the final product might contain. The goal is to identify the smallest functional product that can produce useful evidence.
Break#
⏱️ 10 minutes
3. Plan the first implementation work#
⏱️ 25 minutes — team
Work only from the Must-have features. Break enough of the immediate work into small tasks for the team to begin implementation.
Each initial task must have:
a small, observable outcome;
one accountable owner;
a credible deadline;
any known dependency; and
a clear condition for moving from Review to Done.
Add the tasks to the existing GitHub Project and use the workflow established in Week 9:
Todo → In Progress → Review → Done
Every team member must leave the studio with at least one meaningful coding task. You are not expected to identify or allocate every task required to complete the MVP today. Add and refine tasks as implementation reveals new work.
4. Review workflows and skills for Iteration 3#
⏱️ 20 minutes — team
Implementation and renewed customer testing introduce repeated work that may benefit from a documented workflow or repository skill. Review the possible skill outlined in Week 9 and ask whether it is still useful for Iteration 3.
Consider activities such as:
starting and reviewing a feature implementation;
checking that another person can run the MVP locally;
preparing and recording an MVP-testing interview;
converting test evidence into a learning card;
checking links between features, evidence, test cards and learning cards; or
preparing a change for human review before it is merged.
Choose one useful workflow. It may be an update to an existing skill or a new candidate. Outline—but do not yet implement—its:
Element |
Team decision |
|---|---|
Purpose |
What useful outcome would the workflow support? |
Inputs |
What information, files or tools may it use? |
Steps |
What sequence should be followed? |
Checks |
What must be verified, and by whom? |
Output |
What observable result should it produce? |
Boundaries |
What must it never receive, invent or decide? |
The workflow may be completed manually, with hosted AI, or with local AI. The intended output, privacy boundaries and human-review expectations must remain clear whichever pathway is used.
5. Begin project work#
⏱️ 30 minutes — individual implementation within the team
Begin the first allocated implementation tasks. Each person should:
move their task to In Progress;
work in an appropriate branch or agreed workspace;
make the intended outcome visible in the repository;
record blockers or newly discovered work on the board; and
request review if the task reaches the Review stage.
Use this time to test whether the initial plan is workable. Adjust task size, ownership or sequencing when the work reveals a better approach.
Exit ticket#
Show your legend:
the important assumption the MVP will test;
the feature list with evidence links and MoSCoW priorities;
the Must-have scope;
the initial GitHub tasks, including a meaningful coding task for every team member;
the outline of one Iteration 3 workflow or repository skill; and
evidence that the first implementation work has started.
After the studio, continue refining the plan as the team builds, tests and learns. Keep the GitHub Project aligned with the work actually being performed rather than treating today’s plan as fixed.