If you don't understand the Problem,— Cliff Hazell (@cliffhazell) September 4, 2020
Anything can look like a solution.
X : One of our customers wants a new feature in our product.— Simon Wardley (@swardley) September 3, 2020
Me : Sounds good. Add it to the backlog.
X : No other customer seems to want this. It's unique to them.
Me : Is it a generally useful feature that others might want?
X : I doubt it
Me : Then super low priority.
Your career is not a ladder, it's a game. Those who treat it like ladder will make linear progress at best and let their fear hold them back. Those who treat it like a game will collect the resources, find the people, and build the skills that compound — and have fun doing it!— Kevin Yien (@kevinyien) August 25, 2020
When we did our compare & contrast of the working models underpinned by Change-Harvesting theory (CHT) vs Rework Avoidance Theory (RAT), we temporarily sidestepped the specific differences of the implementation part. Let's drill in on that today. https://t.co/dFglpKkgAz— GeePaw Hill (@GeePawHill) August 23, 2020
Wow. Sometimes a picture paints a thousand words.— Gary Fleming (@garyfleming) August 21, 2020
My thinking had been stuck in diagram two, while doing strategic thinking (Cynefin, Real Options) as a separate thing. An input.
In 30 seconds of seeing this, I could imagine a much better way. https://t.co/SwbALyv3r0
“We’re so busy”— Cliff Hazell (@cliffhazell) August 21, 2020
a fancy way of saying
“We don’t know what’s important”
Am I alone in not liking the term “platform team”? Makes me worried that the team just ends up focusing on the tooling, rather than their actual job which should be enabling other teams to do their job. I much prefer “delivery support” or “delivery services”.— Sam Newman (@samnewman) August 20, 2020
A flow app, one that steps the user through an acyclic graph, typically gathering info at each stage, can be built to provide iterative user value by gradual refinement. Let's look at how that's done.— GeePaw Hill (@GeePawHill) August 16, 2020
Teams/Orgs should also have a Branches In Progress (BIP) limit. The point at which we go - We are not creating another branch till one is eliminated. My preferred number of BIP would be 1.— Prateek Singh (@singhpr) August 11, 2020
The correlation principle says that our productivity is tightly correlated with the internal quality of software. The two go up together, and they go down together, and you can't trade away the one to get more of the other.— GeePaw Hill (@GeePawHill) August 9, 2020
Let's talk it over.