Start with the backlog[1] Plan the iteration, based on the capacity of the team[2] Work the iteration[3] Deliver an increment[4] Retrospect
Start with the backlog, feeding the Ready Queue[1] Flow items into the available slots, which represent the capacity of the team[2] This is the Work in Progress, which is explicitly limited in Kanban.[3] Other activities occur at cadences that are determined independently.
5000 - the number of problems a typical engineering undergraduate is given to solve, each one having a unique solution. In business the trick is finding the right problem to solve, not coming up with the one solution.
Start with the backlog[1] Plan the iteration, based on the capacity of the team[2] Work the iteration[3] Deliver an increment[4] Retrospect
Start with the backlog, feeding the Ready Queue[1] Flow items into the available slots, which represent the capacity of the team[2] This is the Work in Progress, which is explicitly limited in Kanban.[3] Other activities occur at cadences that are determined independently.
Daniel Kahnman - Thinking Fast and Slow
25-55% - imagine you run an experiment where you expect over a week that 25% of your userbase will give it a try. At the end of the experiment you get 55% to give it a try, if you don't write down the 25%, in your excitement you will skip confronting why your initial estimate was off by a factor of 2. Even in success you need to learn from comparing what you expected will happen vs. what actually happened