Fork me on GitHub
#bof-arch-engineering-ops
<
2020-06-25
>
Ferrix Hovi - Head of DevOps - Siili06:06:00

Hmm... sounds interesting. Still browsing for where I would be going. My own antidote to featuritis is a story I tell teams: There is a point where the business and PO step into your area of engineering pride. The only responsible thing to do is to say: "Sorry, but you can't have it that way. You will have to hire a team of unprofessionals for that."

Simon Rohrer, [Sooner Safer Happier contributor] Saxo Bank, Head of EA and DevEx07:06:47

(Also worth noting featuritis isn’t even good from a product management perspective https://melissaperri.com/book)

Ferrix Hovi - Head of DevOps - Siili07:06:31

My customer has gone 70:20:10 in ALL operations, meaning not just IT. The principle is splitting focus as follows • 70% of planned work on core business • 20% of planned work on increasing work effectiveness • 10% of unplanned work on learning, innovating Agreeing and following up on getting those investments is a real challenge them and I get to help a lot on that and there is even a 90 min introductory workshop on "what kind of work goes into which bucket and when". It was just adopted enterprise-wide, so I don't know how it will roll out but at least it helps in making featuritis visible.

Ferrix Hovi - Head of DevOps - Siili07:06:31

My customer has gone 70:20:10 in ALL operations, meaning not just IT. The principle is splitting focus as follows • 70% of planned work on core business • 20% of planned work on increasing work effectiveness • 10% of unplanned work on learning, innovating Agreeing and following up on getting those investments is a real challenge them and I get to help a lot on that and there is even a 90 min introductory workshop on "what kind of work goes into which bucket and when". It was just adopted enterprise-wide, so I don't know how it will roll out but at least it helps in making featuritis visible.

Kurt A (Speaker) Blameless, SRE Architect10:06:44

Not quite sure if this is the right/best channel to ask this, but gotta start somewhere: One of the problems that we are wrestling with is the "you build it, you run it" mantra that doesn't work very well with internal/external mobility (move from one team to another at will). We often end up with zombie microservices that have no one running them because they have gone on to other projects or entire teams vanish through re-structuring. Thoughts on dealing with that problem? Who ends up having to "take out the trash"?

Kurt A (Speaker) Blameless, SRE Architect10:06:44

Not quite sure if this is the right/best channel to ask this, but gotta start somewhere: One of the problems that we are wrestling with is the "you build it, you run it" mantra that doesn't work very well with internal/external mobility (move from one team to another at will). We often end up with zombie microservices that have no one running them because they have gone on to other projects or entire teams vanish through re-structuring. Thoughts on dealing with that problem? Who ends up having to "take out the trash"?

Simon Maple13:06:30

Hey folks 👋 - for todays BoF session, please join me on this zoom https://snyk.zoom.us/j/7318247290

Ferrix Hovi - Head of DevOps - Siili15:06:10

@ewa.kostrzewa Good luck with the Kubernetes 😄

Ron Chittaro15:06:20

Thanks everyone. Enjoyed talking with you!