Our "Operating Model"

(today & tomorrow)

What's 'operating model'?

It's the way we're organized.

To deliver value.

Issue of scaling

  1. the hardest stuff in IT (ever)
  2. Conway's Law
  3. communication mastery
  4. knowledge exchange
  5. expertise & mentoring
  6. different levels of abstraction
  7. people are ... people

What does the world do?

  1. Post-feudal reality
  2. Functional structures
  3. Project structures
  4. Matrix structures
  5. Does Google do Scrum?
  6. Holacracy (& its fallacies)
  7. BYOM

Three pillars

  1. Product
  2. Technology+Architecture
  3. People+Process

Role of a ... product Owner

  1. Business Vision
  2. Feedback - early & continuous
  3. Business Goals & Expectations
  4. Feedback - early & continuous
  5. Business Why
  6. Feedback - early & continuous
  7. Business Priorities
  8. Feedback - early & continuous

sins & fallacies ...
of '
faWLTY' Product Owners

  1. Throws over the wall
  2. Proxy
  3. Chronicler / 'Documentor'
  4. Indecisive
  5. Doesn't get the idea of evolutionary product building
  6. Too project-oriented
  7. Poor communicator
  8. Not fact-based

Role of aN ... ARCHITECT

  1. Technical / Arch Vision
  2. Feedback - early & continuous
  3. Technical / Arch Goals & Expectations
  4. Feedback - early & continuous
  5. Technical / Arch Why
  6. Feedback - early & continuous
  7. Technical / Arch Priorities
  8. Feedback - early & continuous

sins & fallacies ...
of 'faWLTY' Architects

  1. Throws over the wall
  2. Ivory Tower
  3. Chronicler / 'Documentor'
  4. Indecisive
  5. Perfectionist
  6. DIY / Knowledge Silo
  7. Poor communicator
  8. Not fact-based
  9. Ego > Team
  10. Lack of pragmatism

Role of aN ...
eNGINEERING MANAGER

  1. Impediment Remover
  2. Feedback - early & continuous
  3. GSD Custodian
  4. Feedback - early & continuous
  5. People Support & Development
  6. Feedback - early & continuous
  7. Continuous Improvement Watch
  8. Feedback - early & continuous
  9. Work Environment Management

sins & fallacies ...
of 'faWLTY' Engineering managers

  1. Micromanagement
  2. Ruinously empathic
  3. Doesn't ask 'why'
  4. No hands-on experience
  5. Doesn't challenge / empower
  6. Poor communicator
  7. Not fact-based
  8. Ego > Team
  9. Lack of pragmatism
  10. Tells, instead of asking

Getting shit done

  • everyday leadership
  • RACI
  • who's in charge?
  • servant leadership
  • we're all 'in the trenches'

F.A.Q.

  1. Who's my boss?
  2. Who'll give me feedback?
  3. Are we ditching Scrum?
  4. Are we firing Szymon?
  5. Are we getting managers?
  6. Are we reducing teams' autonomy?
  7. Are we getting split by area?
  8. What are my career progression options?

Our "Operating Model" (today & tomorrow)

By Sebastian Gębski

Our "Operating Model" (today & tomorrow)

Our "Operating Model" (today & tomorrow)

  • 58
Loading comments...

More from Sebastian Gębski