devops_notes.md

Business Capability teams

Typical Role Composition

• Product owner
• Designer
• Tester(s)
• Developers (1-3 pairs)

Core roles

• Developer/Engineer

  • Software development
  • Application support

• Product Owner/Manager

  • Providing business and customer context
  • Prioritize tasks
  • Final decision maker

• Designer/Creative

  • Translates application features to user experiences
  • Developing working design elements; IA, userflows, wireframes, etc..
  • Developing creative design elements; visual design, copy, style guides, etc..

• Operations

  • Support application production needs
  • Knowledge sharing with developers
  • Designated or dedicated

• Testers (optional)

  • Functional tests
  • Security tests
  • Compliance tests

• Architect (optional)

  • Support product team by validating development and execution strategy
  • Provide application assessment of long-term quality and flexibility
  • Designated or dedicated

• Data scientist (optional)

  • Support team with data analysis expertise
  • Provide insights to product team
  • Designated or dedicated

Operations

• Application Operator

  • Member of the application team
  • Lifecyle and release management
  • Ensure application of automated tests
  • Ensure application monitoring
  • May support developmental tools in use by application team
  • 2nd level support, triage to appropriate application team member

• Platform Engineer

  • May support application operator with platform expertise
  • Developing and maintaining changes to the supporting application platform
  • Ensure the health and availablity of the supporting platform

• Physical Infrastructure Engineer

  • Maintains the physical network and systems supporting the application platform
  • Ensure the health and availability of supporting hardware

Org layering

• Business capability
  • Application developers
• Platform
  • Platform developers
• Site reliability
  • Application operator
  • Platform operator
• Infrastructure
  • Infrastructure Engineers

Silos vs Tribes

Traditional role-based teams (silos)

• Role centric rather than the product centric
• Creates gaps in knowledge and responsiblity; reducing innovation, product quality, and delivery speed
• Can create poor interactions between teams
• "Project" focused; short term cross team collaboration, rather than continuous iterative improvements
• Local optimization causing global optimization problems

Integrated teams (tribes)

• Self sufficient and autonomous
• Product centric
• Continuous product improvement
• End-to-end product expertise