stevefenton

5 ms·

1.
by stevefenton 3y ago
I'd start with small batches. Quite a lot of the benefits come out of just doing fewer things between each release.
2.
by stevefenton 3y ago
It's fair to say that culture eats everything else alive. It's also the hardest thing to change. I've worked in a few places where we felt helpless to impact the culture and creating a culture-bubble (i.e. to the extent of th
3.
by stevefenton 3y ago
Accelerate: The science of Lean Software and DevOps Nicole Forsgren, PhD, Jez Humble, Gene Kim IT Revolution ISBN 978-1-942788-33-1
4.
by stevefenton 3y ago
You may like Platform Engineering even more as there's a lot of crossover with what you mention. A key difference from your list is that you enable teams to build and run their own applications, so they remain responsible throughout. Y
5.
by stevefenton 3y ago
Companies who need every engineer to "Do Everything™" are doing it wrong. A team may need to cover a lot of ground, but by putting together folks who have different skills. It's a management skill to assemble a team with dive
6.
by stevefenton 3y ago
Yes, there is that! ;)
7.
by stevefenton 3y ago
DevOps part one was just "developers and operations working more closely together". It only really required the managers to update the goals of the two specilizations to remove the conflict (developers are rewarded for delivering
8.
by stevefenton 3y ago
Rather than a maturity model, DORA use metrics and a capability model. The idea is you use the metrics to decide on which capabilities to focus on. This tailoring to your context is the great thing about it - it's what you mention when
9.
by stevefenton 3y ago
Cynefin is a great model - I must admit I've been insterested in it for a long time (I think Liz Keogh brought it to my attention) - but I've not applied it practically. Anyone got ideas for using it IRL?