The idea of independent, autonomous service teams is not new. Amazon, Akamai, Google, Facebook; at some level all of these companies have embraced the idea of autonomy for developers, tooling to support a self-service model and at their core, the idea of what most of us would consider cross-functional responsibility for the delivery and the running of the service.
My engineering background is reasonably unique in that I’ve worked professionally in the capacity of a software developer and a system administrator. Sometimes, acting in both capacities at once (You guessed it I worked at startups!)
I progressed in to management at Workday, running our EMEA Technical Operations group. That Technical Operations organisation was the last stop for most developers on their way to delivering to production. As Workday scaled, we imagined there were more efficient ways to scale delivery & operations.
Right now, I report up in to our Technology Services / Engineering organisation running our first cross functional groups which are responsible for some core elements of our platform. The monitoring team which provides our monitoring platform is the first example of a self-service team and we are using those learnings to help hire, guide & build other self-service units within the business.
This talk is meant to be useful for anyone currently transitioning or looking to transition towards cross functional scrum teams.
Engineering background in both development, build and operations. Internet systems
Comments on this page are now closed.
For exhibition and sponsorship opportunities, contact Gloria Lombardo at email@example.com
For information on trade opportunities with O'Reilly conferences contact firstname.lastname@example.org
For media-related inquiries, contact Maureen Jennings at email@example.com
View a complete list of Velocity contacts