Skip to content

Latest commit

 

History

History
138 lines (105 loc) · 6.55 KB

personas.md

File metadata and controls

138 lines (105 loc) · 6.55 KB

CD Foundation Stakeholder Personas

The following personas have influence over processes and decisions that the CD Foundation seeks to innovate and govern. These individuals participate in the community flywheel of open source software awareness, adoption, and advocacy. On some level, they all make decisions about using software to advance organizational goals. This makes them ideal target audiences for CDF content and programs. CD Foundation content and programs should identify a primary audience for each offering, and any secondary audiences.

Application Developer

I develop web, mobile, and business applications for my organization. I am usually an individual contributor (IC) on a team. I use SDLC tooling as a means to an end and usually have some freedom to choose tools and environments. I may have strong opinions about enablers and constraints to my success as a developer, such as standard toolchains workflows at my organization, personal DevOps habits, and team behaviors.

Content & Programs that appeal to me:

  • Podcast
  • Meetups
  • "Solving" solution-specific blog post
  • Stackoverflow answers
  • How-to / educational content

Example title: How to Bake & Deploy Your App to EC2

Key Pain Points:

  • Context switching
  • Observability of status & processes after code check-in
  • Potentially limited coding experience and needs GUI-based tools
  • Monolith-breaking is hard

DevOps Specialist/Cloud Engineer

I enable application teams to build software, and often build and maintain software and systems to enable them. I have firsthand knowledge of the way software is being developed and delivered at my organization. I must think about our SDLC from a macro perspective to make good decisions about tools and projects to invest team time and money in. Automation appeals to me because I often focus on scalability, repeatability, and productivity in my solutions.

My job title could be:

  • Delivery Engineer
  • DevOps Engineer
  • Platforms Engineer
  • Security Engineer
  • Site Reliability Engineer (SRE)
  • Cloud Architect
  • Systems Operator
  • Engineering Manager
  • Engineering Team Lead
  • Cloud Engineer
  • CD Architect
  • Developer Productivity Engineer

Content & Programs that appeal to me:

  • Newsletter
  • Release notes
  • Podcast
  • Meetups
  • "Solving" solution-specific blog post

Example title: How to Use LaunchDarkly Feature Flags to Empower Your Developers (and get more sleep)

Key Pain Points

  • Desire to foster self-service in consumers (like appdevs, security, etc.) is often frustrated
  • Amount of time it takes code to go to prod
  • How can I support various workload types or application targets - cloud, on prem, blah! Lots - heterogeneity
  • How to select the correct tools? Are part of selecting tooling for the organization - OSS vs. vendor - hard to make decisions with a complicated integration matrix
  • Managing integrations becomes complicated
  • Hard to get consumers like app dev to adopt new tools (people are set in their ways, plus legacy workloads, costs)
  • Educating and onboarding new users is a big challenge and doesn’t guarantee successful adoption

Delivery Director

I direct my organization tactically to maximize return on our investment in software and information systems. I often manage DevOps Champion individual contributors (ICs) and guide them to drive agility and systemic improvement. I optimize our ability to meet business, customer, product, and engineering needs by delivering reliable infrastructure, processes, and tooling to support complex systems. I trust my engineers to recommend the right tools for our workflows.

Content & Programs that appeal to me:

  • Case studies - logo wall that links to detailed case studies
  • Featured solutions and case studies
  • Problem-specific solution briefs
  • Webinars
  • Partnerships & Tool interoperability
  • Productivity boosters

My job title could be:

  • Product Manager
  • DevOps Transformational Lead
  • Director of Delivery
  • DevOps Manager
  • Developer Productivity Manager

Example: Why Implementing a Service Mesh Made Our Engineering Team More Productive

Key Pain Points

  • Budgeting & cost management (finOps)
  • Business agility
  • Engineering resource allocation for maintaining software (considering SaaS for ex.)
  • Build or buy decisions
  • Hiring
  • Developer Productivity e.g. reducing context switching for team members
  • Keeping legacy workloads safe and available despite aging tech and tool soup

Technology Executive

I offer executive guidance on the alignment of technical resources to our organizational needs. I drive digital transformation and other technology initiatives by building a vision and around the systems and infrastructure our org uses and adopts, and leading adoption. I ensure that strategic plans honor security, compliance, user experience, and other business focus areas that technology impacts.

My job title could be:

  • CIO/CTO/CXO
  • VP of Engineering
  • VP of Productivity Engineering

Content & Programs that appeal to me:

  • Case studies - logo wall that links to case studies
  • Infographics about the benefits of CD and digital transformation
  • Stats on OSS contribution activity and maturity
  • FinOps Collaborative Content

Example title: Deutsche Bank Saves Millions by Automating CI & Artifact Management with Jenkins

Key Pain Points

  • Cost and time savings are needed
  • Business agility
  • Showing progress in digital transformation
  • Budgeting & FinOps
  • Selling new/different ideas to the board - balancing the new stuff with primary business needs/motivators

Developer Advocate

I research and develop hands-on projects and solutions using open source tools as part of my developer relations or advocacy role. While building solutions, I develop a deep understanding of the pros and cons of different tools/platforms. I have a strong connection to the technical implementation and business application of the projects because of my work with stakeholders from different companies, and make solution recommendations to my customers. I have awareness of many projects and may contribute and engage heavily in those I'm passionate about, but I also need to maintain a broad knee-deep familiarity with a variety of tools and platforms.

My job title could be:

  • Developer Advocate
  • Developer Relations Engineer
  • Developer Evangelist
  • Technical Marketer
  • CTO group engineer

Content & Programs that appeal to me:

  • Newsletter
  • Podcast
  • Release notes
  • Meetups
  • Comparative content
  • High-level analysis and detail aggregation content
  • Cloud-native technology deep dives and theory

Example title: Why JenkinsX Helps You Write Tekton Pipelines Faster than Travis