Marcus Hamrin

Product development & operations. Antifragility, cynefin, flow, continuous learning. (ex- Spotify)

[Marcus Hamrin @hamrin]

Stop asking what to measure & start asking what to care about. Then measure that.
#measureoutcomes #outcomedriven

[Marcus Hamrin @hamrin]

There is no perfection. There is only the right thing at the right time. And time moves on.

[Marcus Hamrin @hamrin]

@JustAnotherPM I’d ask them “given what you DO know, what’s the forecast range?” The range illustrates their level of uncertainty, it’d be up to me to determine if that is ok. (Ideally I’d have flow data and not worry about estimating at all)

[Marcus Hamrin @hamrin]

Push = emergent need for predictability
Pull = emergent ability to predict

[Marcus Hamrin @hamrin]

@PatThePM 1: I separate actions from FYIs
2: I write actions in a notebook by hand. I get the time needed slow down and evaluate actions.
3: I review notes often, strike non-essentials
4: I set Slack reminders for FYIs
5: I have a tab group named “to read”
6: Breathe. Slow down.

[Marcus Hamrin @hamrin]

@patrickdebois How would you notice that you have it? What would you see more/less of?

[Marcus Hamrin @hamrin]

If you have two teams dependent on each other to deliver value, you actually have ONE team. Treat WIP & queues accordingly.

[Marcus Hamrin @hamrin]

If you're not doing TDD, you're so missing out on continuous dopamine hits

[Marcus Hamrin @hamrin]

@ant_murphy No/yes/doesn’t matter. Good roadmaps are good, bad roadmaps are bad 🤷

[Marcus Hamrin @hamrin]

@eldsjal Death metal 🤘

[Marcus Hamrin @hamrin]

“Four Kinds of Value”

https://t.co/W8FyqkcrU0

[Marcus Hamrin @hamrin]

@cliffhazell Reminds me of ”The Bear is Sticky with Honey”
https://t.co/hJ6veAWGIP

[Marcus Hamrin @hamrin]

@johncutlefish I call it Tech Health

[Marcus Hamrin @hamrin]

“Protect Value” is work to ensure validated user value continues. It is NOT tech debt. PV-work is maybe not as fancy as “Create New Value”, but it’s validated and valued, unlike “New Value”. Should be easy to prio most of the time.

[Marcus Hamrin @hamrin]

If you care about predictability, you should care about product quality first.

Bugs, incidents & tech debt will ruin any attempt at increasing predictability of product delivery.

[Marcus Hamrin @hamrin]

@CGLambdin But how would you know?

[Marcus Hamrin @hamrin]

@tottinge That could be useful! How might one avoid hindsight and/or selection bias? Many things influence flow, couldn’t it be tricky to attribute the “right” cause(s)?
Then again, that problem remains without this feature. It could enable identifying patterns over time 🤔

[Marcus Hamrin @hamrin]

Beware: “Align” might sometimes mean “make sure everyone understands all project requirements before we get started”.

[Marcus Hamrin @hamrin]

@PatThePM We use the same word but often expect different behaviors. Should prio 1:
- start first?
- end first?
- get most funding?
- other?
Priority is hard when we don’t agree on what behaviors to expect as a result of using it.

[Cliff Hazell 🚀 @cliffhazell]

Agile folks seem to have forgotten it's original Intent:

“Working software is the primary measure of progress”

[Doc Norton @DocOnDev]

It's irresponsible to load teams to 100% capacity. Increased workload creates longer delays, lower quality, and higher costs.
#agile #leadership