Product development & operations. Antifragility, cynefin, flow, continuous learning. (ex- Spotify)
Stockholm
Joined January 2009
- Tweets529
- Following119
- Followers151
- Likes670
Marcus Hamrin retweeted
Agile folks seem to have forgotten it's original Intent:
“Working software is the primary measure of progress”
Marcus Hamrin retweeted
It's irresponsible to load teams to 100% capacity. Increased workload creates longer delays, lower quality, and higher costs.
#agile #leadership
Marcus Hamrin retweeted
Contrary to conventional Twitter wisdom, one does not have to always fail before succeeding. In many types of product work, it is possible to just directly succeed, without taking yourself and your teams through many rounds of failures disguised as “learnings” 🙂
Marcus Hamrin retweeted
Imagine you have a developer who doesn’t want to use the programming language of the project, so they write in BASIC and you have to rewrite it in Java/Kotlin/Whatever when they finish.
Tell me how you would deal with someone who put their preference over your costs.
Marcus Hamrin retweeted
Maybe it's time to replace the narrative of "effective versus efficient" with a narrative of "robust and resilient" #complexity – at Stockholm, Sweden
Marcus Hamrin retweeted
We need to allow for emergent architecture. So we've appointed a group of senior architects to design the architecture that will emerge.
#NotMyAgile
Marcus Hamrin retweeted
There is a belief that we can predict the future. That we can know what we want, analyze and understand all the details, figure out how to make that (or provide that), and then simply "execute on our plan".
1/?
Marcus Hamrin retweeted
På samma sätt som Twitter klarar sig ”bra” utan 75% av sin personal så funderade jag på vad som skulle hända om Stockholms stad drog bort allt underhåll och personal från Skolplattformen. Läs nedan en tråd om vad som faktiskt pågår varje månad i Skolplattformen🧵
Marcus Hamrin retweeted
Thread: “Predictability” is the most common leadership request I get. What is meant by that request varies widely. I first need to get companies to decide what “Predictability” they want, but I have a strong preference for “get what you need to do, done”
Marcus Hamrin retweeted
There is no iterative software development without rework.
And tons of rework do not indicate that you are practicing iterative development.
Marcus Hamrin retweeted
There's this thing where I state quite clearly, right here on Twitter, that some proposition X is incorrect, and yet people out there in the world continue to claim X anyway. Baffling.
Marcus Hamrin retweeted
A) Optimizing for efficiency to deliver the most stuff possible
is very different from
B) Optimizing for discovery to find the least amount of intervention needed to effect an outcome.
B not only creates less waste but, in the long run, is ironically also more efficient!
Marcus Hamrin retweeted
Being called “results-oriented” would be a compliment in many contexts. In poker it’s considered the an insult.
You can control process, but results are a combination of your process, random fluctuations, and forces outside your control. A principle of wide applicability.
Marcus Hamrin retweeted
Large projects are large batches and large batches cause many problems, one of which is the Batch Size Death Spiral. This is discussed on p 118-119 PPDF.
Marcus Hamrin retweeted
The most difficult of all simple ideas to internalize is probably this: To be done sooner, do less.
