๐Ÿš€
Stellar Kickstart
  • ๐Ÿ•๏ธWelcome to the SCF Kickstart Week
    • ๐Ÿ’ฐFunding Overview
    • โœ๏ธDear changemakers, visionaries, and problem solvers
    • โ„น๏ธTL;DR: How to Maximize Your SCF Kickstart Week Experience
  • ๐Ÿ“šFundamentals of Integrating with Stellar
    • ๐Ÿš€Stellar For
    • ๐Ÿ—๏ธBuilding with Stellar
    • ๐Ÿ”งTools
    • ๐Ÿ‘ทResources
      • Fundamental Concepts
        • โญIntroduction to the Stellar network
        • โ›“๏ธIntroduction to blockchain technology
        • ๐Ÿ’ตIntroduction to payments in Stellar
        • ๐Ÿง‘Accounts
      • Core Features & Mechanisms
        • ๐Ÿ”Assets: Powering Digital Value Exchange
        • Assets Issuance: Manage digital assets effortlessly on Stellar
        • ๐Ÿ’ธTransactions: At Stellar Core
        • ๐Ÿ‘ฎโ€โ™‚๏ธSignatures in Stellar: Who, how much and to what is authorized
      • Payments & Transactions
        • ๐Ÿ’ฐPayments: Simplifying Transactions with Stellar
        • โ›“๏ธPath Payments: Convert Assets at Minimal Cost
        • โ›ฝFee-Bump: How to pay for other people's transactions
      • Developer & Integration Tools
        • ๐Ÿ‘ฉโ€๐Ÿ”ฌStellar Laboratory: Stellar at hand for everyone
        • ๐ŸšชFaucet: Easy Access to Free Blockchain Assets
        • ๐ŸงฐStellar Wallets Kit: A kit to handle all Stellar Wallets at once with a simple API
        • โœ๏ธSimple Signer: A wallet aggregator and transaction signer
      • Advanced Development & Testing
        • ๐ŸงชHow to Create Integration Tests Using GitHub Actions and Stellar's Docker Image
  • ๐ŸŽจDesign Sprint
    • ๐ŸŒ…Introduction
    • 1๏ธโƒฃDay 1 - Validate your problem and define your MVP's Scope
    • 2๏ธโƒฃDay 2 - Build a prototype to validate with real users
    • 3๏ธโƒฃDay 3 - Define the technical architecture
    • 4๏ธโƒฃDay 4: Develop your Go To Market Strategy & Pitch Deck
    • 5๏ธโƒฃDay 5: Compile all the information
    • ๐Ÿ‘€Sample Completed Design Sprint
Powered by GitBook
On this page
  • Define your Proof of Concept (POC), Minimum Viable Product (MVP), Minimum Marketable Product (MMP)
  • Size and Risk your POC User Stories
  • UX Mockups
  1. Design Sprint

Day 2 - Build a prototype to validate with real users

Welcome to day 2! Now that you know what you're building, itโ€™s time to create a roadmap and UX mockups.

PreviousDay 1 - Validate your problem and define your MVP's ScopeNextDay 3 - Define the technical architecture

Last updated 5 months ago

As part of your Stellar Community Fund submission, you must ensure your Proof of Concept is achievable in 1-2 months. To do that, youโ€™ll take the user stories from Expanded Golden Path, organize them into the MOSCOW canvas; and then size your POC (the items in the Must Have) using t-shirt sizes (S, M, L, XL). Your best guess is okay.

Define your Proof of Concept (POC), Minimum Viable Product (MVP), Minimum Marketable Product (MMP)

  1. Proof of Concept (POC):

    • Timeframe: 1-2 months

    • Definition: A proof of concept is a small-scale demonstration to validate the feasibility of a concept or idea. It aims to verify whether a certain concept can be implemented effectively.

  2. Minimum Viable Product (MVP):

    • Timeframe: 4-6 months

    • Definition: A minimum viable product is a basic version of a product with only essential features to satisfy early adopters and collect feedback for future development iterations.

  3. Minimum Marketable Product (MMP):

    • Timeframe: 6-12 months

    • Definition: A minimum marketable product is the version of a product that includes enough features and functionality to satisfy early customers and generate revenue.

For the activation award, you must present a project that can be delivered in 1-2 months (a proof of concept)

In this section, you are required to organize the tasks that you created in the USER STORY MAP into items that it must have to test the solution in 1-2 months (this is your POC), items it should have in the next 4-6 months (this is your MVP), and items it could have (this is your MMP) in the next 6-12 months. Everything else will go into the Will Not Have section.

Size and Risk your POC User Stories

As part of your Stellar Community Fund submission, you must ensure your Proof of Concept is achievable in 1-2 months. To do that, size your POC (the items in the Must Have) using t-shirt sizes (S, M, L, XL). Your best guess is okay.

UX Mockups

A low-fidelity wireframe is a skeleton of a digital screen, web page, or application. It'll have the bare-bones elements that will be included in the finished project. Low-fidelity wireframes give designers and programmers an idea of where images, text, buttons, and interactive elements might be placed.

You will use a tool called to determine your POC, your MVP, and your MMP.

๐ŸŽจ
2๏ธโƒฃ
MoSCoW
Must Have: This is what you'll be applying for your in your Activation Award submission
Should Have: This is likely to be your Community Award submission roadmap
Could Have: Together with the "Should Have," this is likely to be a good base for determining", your Total Expected Roadmap. These are stories that will make it into your MMP.
Won't Have: These are items that are 1+ years away from being built, and therefore are not worth spending any time over right now.
You should not have XL tickets. If you deem one of them to be XL, break it up into smaller chunks!
If you have a designer on your team, you can make it as high-level as you want. If not, a simple mockup (even pen & paper) will do.