LIST
ROI - cost estimates don’t matter prioritize based on cost of delay “how much would we have earned if this was in production” We’re more wrong than not in guessing which features will be valuable (90% wrong in uncertain/new markets, xx>50% in well known markets) So what do we do? (src: Video_ Why Scaling Agile Doesn’t Work - Jez Humble)
start with signals, not requirements have a problem statement, not features plan with hypotheses, not estimates experiments around a hypothesis, not backlog of stories analysis and conclusion, not guesses analysis and conclusion, not guesses if you have good problem solving teams, what good are estimates? within constraints here is my constraints here is my problem (src: Video_ The Future of Software Engineering - Mary Poppendieck)
[planning] reflection every week know at beginning of the week reflect at end of week 3 outcomes / day & week gettingresults.com - Scott Hanselman (src: Video_ Scaling Yourself - Scott Hanselman)
Dreyfus model Novice: needs rules best practices nothing else keep it simple Advanced beginner: test rules break rules test the limits Competent: applies rules has internalised Proficient: falls back on rules instinct, instinct, insight don’t trust it yet Expert: transcends rules no longer think in rules Dreyfus Squared novice + expert = x-( someone dies advance + advanced massive learning don’t put into prod competent + novice = :-) proficient + expert = :-D...
(https://www.youtube.com/watch?v=6K4ljFZWgW8) Book_ Antifragile - Nicolas Taleb Paper_ Resilience Engineering_ Learning to Embrace Failure - Acm Queue Book_ The DevOps Handbook - Gene Kim, Jez Humble, Patrick Debois, John Willis Book_ Continuous Delivery - Jez Humble, David Farley Paper_ Online Experimentation at Microsoft - Kohavi, Crook, Longbotham Paper: Standis Group Study Reported at XP2002 by Jim Johnson, Chairman Book_ Sprint - Jake Knapp, John Zeratsky, Brad Kowitz Video_ The Design Sprint - Google I_O 2014 scale out more servers CAP theorem less communication autonomous teams...
TDD, Where Did It All Go Wrong - Ian Cooper https://www.youtube.com/watch?v=EZ05e7EMOLM Book_ Refactoring - Martin Fowler Book_ Refactoring to Patterns - Joshua Kerievsky Book_ Test Driven Development_ By Example - Kent Beck Article_ Is TDD Dead_ - Martin Fowler Ian Cooper - TDD, Where Did It All Go Wrong https://www.youtube.com/watch?v=EZ05e7EMOLM Trigger for writing test != new method != new class = requirement test api System Under Test (SUT) !...
Why Scaling Agile Doesn’t Work • Jez Humble https://www.youtube.com/watch?v=2zYxWEZ0gYg Article: The IT Measurement Inversion - Douglas Hubbard Paper: Black Swan Farming using Cost of Delay - Joshua J Arnold and Ozlem Yuce Book: Impact Mapping - Gojko Adzic Video: Better product definition with Lean UX and Design Thinking - Jeff Gothelf Paper: Online experimentation at Microsoft - Kohavi Book: A Practical Approach to Large-Scale Agile Development - Gruver, Young, Fulghum Book: Leading Change - John Kotter [[model-prioritization-cost-of-delay-vs-cost-to-build....
(notebook4 p24)