Limited options gave me an unprecedented focus on what's important. I'd have created a better app now that I've created the spreadsheet. The thing is I don't need to as it brilliantly solves my problem.

Spreadsheets are underrated. It might seem that a spreadsheet would limit me in some ways, but its limitations turn out to be a superpower.

Careful. It's as addictive as years ago!

Yep.

what's the trakcer/logging app on the screenshot?

"You can’t do BDD. You might be able to write some scenarios or some acceptance tests, but they’re likely to be brittle and it’s unlikely that anyone will be interested. Here’s why."

lizkeogh.com/2011/03/04/s...

"Start by having conversations, engaging both testers and business stakeholders or their proxies (analysts are good here). If you can’t have those conversations, stop."

You need to turn around. Monitors are behind you!

Also, I can't stop giggling at "Full Snack Developer" 😂

- Your job isn’t to build more software faster: it’s to maximize the outcome and impact you get from what you choose to build.

- Stories aren’t the requirements; they’re discussions about solving problems for our organization, our customers, and our users that lead to agreements on what to build.

- Stories aren’t a written form of requirements; telling stories through collaboration with words and pictures is a mechanism that builds shared understanding.

"There’s always more to build than we have time or resources to build—always."

"Minimize output, and maximize outcome and impact."

"Remember: at the end of the day, your job isn’t to get the requirements right—your job is to change the world."

"Good story conversations are about who and why, not just what."

Impact.

Impact is a longer-term consequence of good outcomes. Outcomes are often something you can observe right away after delivery. The impact takes longer.