What should my API team look like?

1 0 1,830

Now that you've started your journey with Apigee Edge, it's time to gather your team. We've been lucky enough to work alongside many customers as they build their API team, and we've observed teams overcome challenges ranging from part-time availability and time zone differences to assessing comfort level for risk management. We think the best way for us to share the lessons we've learned from seeing API teams in action is by reviewing a list of key team members and then asking a few questions.

  • API Product Owner
  • Executive Sponsor
  • Solution Architect
  • API Proxy Developers
  • Test Lead
  • API Evangelist
  • DevOps
  • Scrum Master

Additional team members engaged as needed during project:

  • Security Architect
  • Network Engineer
  • Marketing

In no particular order, here are a few important questions to consider when building your API team:

  • Is every member of your team dedicated full-time to your API initiative? If not, how will you react when a team member gets pulled into another assignment?
  • Is your team based in the same location? If not, how will you account for time zone differences for team commitments such as daily stand up calls and sprint work?
  • Does your team use agile management?
  • Do you have executive sponsorship for your API project and team?
  • Does your team feel empowered to take action in the best interest of your API initiative?
  • Is your team risk averse or willing to take calculated risks?
  • Have you identified success metrics for your team?

Now that we've got you thinking about your API team, check out a few additional community posts that may help you fine-tune your approach to building your team.

Version history
Last update:
‎04-08-2016 12:00 PM
Updated by: