by repeatedly finding the right idea by talking to customers and honing it into a vision. Avoiding assumption it’s the actually the idea that wins. Lean Startup
by repeatedly finding the right idea by talking to customers and honing it into a vision. Avoiding assumption it’s the actually the idea that wins. Building a minimal product (/service) iteratively Lean Startup
by repeatedly finding the right idea by talking to customers and honing it into a vision. Avoiding assumption it’s the actually the idea that wins. Building a minimal product (/service) iteratively by defining riskiest assumption Lean Startup
eliminating waste by repeatedly finding the right idea by talking to customers and honing it into a vision. Avoiding assumption it’s the actually the idea that wins. Building a minimal product (/service) iteratively by defining riskiest assumption, and validating it by devising a ”scientific experiment”.
eliminating waste by repeatedly finding the right idea by talking to customers and honing it into a vision. Avoiding assumption it’s the actually the idea that wins. Building a minimal product (/service) iteratively by defining riskiest assumption, and validating it by devising a ”scientific experiment”. Eventually, if you’re lucky
eliminating waste by repeatedly finding the right idea by talking to customers and honing it into a vision. Avoiding assumption it’s the actually the idea that wins. Building a minimal product (/service) iteratively by defining riskiest assumption, and validating it by devising a ”scientific experiment”. Eventually, if you’re lucky, you’ll have ”product/market fit”
eliminating waste by repeatedly finding the right idea by talking to customers and honing it into a vision. Avoiding assumption it’s the actually the idea that wins. Building a minimal product (/service) iteratively by defining riskiest assumption, and validating it by devising a ”scientific experiment”. Eventually, if you’re lucky, you’ll have ”product/market fit” and can concentrate on optimizing and scaling.
roles Scrum prescribes timeboxed iterations Kanban limits WIP per workflow state Both are empirical Scrum resists change within an iteration Scrum board is reset between each iteration Scrum prescribes cross-functional teams Scrum backlog items must fit in a sprint Scrum prescribes estimation and velocity Both allow working on multiple products simultaneously Left side by Henrik Kniberg http://www.crisp.se/file-uploads/Kanban-vs-Scrum.pdf No roles – everybody does Suggest quickest possible iterations Limits WIP by deciding what to learn Hyper-empirical – evidence based Discourages but allows change Ideas board could be reseted Assumes cross-functional team Tries to avoid big chunks Innovation accounting Irrelevant – product is the startup
fundamental hypothesis about the 1. product, 2. business model 3. growth engine. To persist in or remain constant to a purpose, idea, or task in the face of obstacles or discouragement.
Customer segment Customer need PlaOorm Business architecture Value capture Engine of growth Channel Technology Single feature as a product Whole product as a feature Good product, bad segment Reposi2oning or new product App to mul2sided High margin low vol reversed Change in revenue model Viral to s2cky Delivery New compe22veness
rossi
cbtlibrary
tetsuyaooooo
matleenalaakso
masatatsu
terasawat
lrm
uranoken
abap34
guvalif
bkeepers
smashingmag
lauravandoore
mongodb
reverentgeek
notwaldorf
irinanazarova
62gerente
scottboms
kneath
tammyeverts
trishagee
