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
a group of people who started using at the same week. Week : 1 2 3 Cohort from week Signed up Signed in Used feature X Usefulne ss Signed in Used feature X Usefulne ss Signed in Used feature X Usefulnes s 1 1111 1111 666 60% 333 167 50% 111 72 65% 2 1555 1555 277 18% 467 70 15% 3 888 888 191 21% Sums: 3554 1111 666 1888 444 1466 333