Rod Molina

Perfect responses to problems do not exist. Every solution creates future problems. Good responses fix the problem and prevent it from happening again. Great ones make future problems easier and not harder.

Stories describe customer problems, not solutions, so the best you can get from a story-point estimate is a feeling for the complexity of the problem, not the solution. Using SPs to estimate build time is like using the color of a lemon to estimate how much lemonade you can make

We learn what to build through the act of building. Hard to reconcile that with estimation. What, precisely are we estimating? If we can estimate it, then "it" isn't flexible. There's no scope for learning. That's okay, but it's not agile.

The point of a user story is NOT to define your work. A backlog is NOT a list of things to do. A user story describes your users/customers working on things that are valuable to them. The whole point is to identify ways to make our customer's lives better. 1/2

New developer refactors legacy code

An interesting thought experiment: Build a set of end-to-end tests that verify that a story works as expected—no unit tests. Monitor execution paths as you run them. Delete everything that wasn't executed. Voilà, 100% coverage!

The total value of Y Combinator companies is over $250 billion. Including Airbnb, Stripe and Coinbase. Here are the 10 best resources from their startup library:

Steve Jobs famously said innovation is "saying no to 1000 things" before you say yes. For more than a decade, Apple has used Pablo Picasso's Bull to drive home the lesson. Here's a breakdown 🧵

“You’re standing in a room with 1000 doors, your job is to close 999 of them" - @TomBilyeu

"In science, every claim, every hypothesis, every cause is considered to be relevant only if it can be put to the test." #Goldratt #Popper

How about release to customer instead of release to production? I want it in my customer's hands, not in the hands of some production team who will sit on it for who knows how long. Let's get rid of the "Production" silo. It's not as if we're burning CDs any more.

That brand of “agile” that is rooted in story points, timeboxes, epics, and individual assignments? It is like someone went through Agile’s trash can. It is agile derived, as a junkyard is to a factory. It isn’t the thing, it is the leftover artifacts only.

"There is no sense in talking about the solution before we agree on the problem, and no sense talking about the implementation steps before we agree on the solution." —Efrat Goldratt-Ashlag #tocot #Goldratt

Beginner’s Mindset…

If you could get all the people in an organization rowing in the same direction, you could dominate any industry, in any market, against any competition, at any time — Gino Wickman

5 MB of data ... 1966

Consistency > #tweet100

MVP is the: _M_inimum thing you can build that tests the _V_iability of a _P_roduct idea. It is a TEST, not a product.

If you don't get feedback until your "Sprint Review," you cannot incorporate that feedback into your work, so you're not "done." Your Sprint has failed. Pretty much all Sprints will fail if you do that, in fact.