Scaling Your Self-Service as a Service

Our topic for Episode 37 was originally on scaling self-service of configuration management (the source code kind, not the infrastructure kind!) good practices, but quickly morphed into a discussion of what organizations need to pay attention and foster to support their tools teams in their often-cited mission of creating a self-service culture and self-service infrastructure. Paul and Sascha square off over the notions of traditional “service” teams and the newer notion of integrated “tools” (“DevOps?”) teams. We also touch on warning signs for automating self-service processes, including in the CM space, really examining how and why you convert which processes into self-service, ways to get teams to buy into your self-service initiatives, and what’s in the best interests of the entire system that is your software development organization. Join us as we discuss the finer points of:

Scaling Your Self-Service as a Service

Join J. Paul Reed, aka @SoberBuildEng, Sascha Bates, aka @sascha_d, Youssuf El-Kalay, aka @buildscientist, and Seth Thomas, aka @cheeseplus for the discussion, plus a the last couple of weeks in News & Views and a review!

Or, download Episode 37, or any of our previous shows!

Show Links/Notes

Review

Paul reviews Venkat Rao’s The Gervais Principle (Or The Office According to “The Office”): losers, clueless, and sociopaths: oh my!

The ebook contains an extra essay on Office Space.

Join Us!

What issues have you run into while trying to sell or scale self-service initiatives?

Have you had to encode culture into your self-service policies to work around problems?

Join the discussion!

Tags: , , , , ,

Comments are closed.