Stakeholder Management

The analysts will be aligned to the business units that are supported, and each stakeholder will know who their point of contact is. This allows the analyst to build relationships, embed in a specific group to become a subject matter expert, and advocate for prioritized engineering work as needed.

Group Stakeholder (VP/Dir)
Product/Engineering Quinn Slack, Steve Yegge
Customer Engineering Aimee Menne
Sales and Ops Ajay Uppaluri
Marketing TBD
Customer Support TBD
People/Recruiting Carly Jones
Finance TBD

The engineering team will be considered a shared service that will prioritize the requests across all business units and will adhere to an agreed upon ratio of prioritized tasks and self-directed tasks like addressing tech debt, optimizations, and platform health and administration.

Stakeholder Partnerships

Data and Analytics responsibilities

  • Align Data and Analytics priorities to stakeholder priorities
  • Gather project requirements and define the definitions of done for each project and task
  • Assign deadlines for projects
  • Communicate overall team priorities
  • Adhere to agreed upon deadlines and communicate as soon as deadlines need to shift
  • Gather feedback from stakeholders and teams as needed
  • Enablement/documentation

Stakeholder responsibilities (VP/Dir)

  • Keep us up to date on business needs to ensure alignment
  • Prioritize large projects
  • Help communicate resource constraints and priority trade offs to your teams/Be a tie-break when we cannot accommodate all requests
  • Communicate shifts in priorities
  • Enablement adoption
  • Champion adoption and engagement of data deliverables/solutions within your teams

Project Requestor or Point of Contact responsibilities (Dir and below)

  • Partner in requirements gathering sessions
  • Agree on timelines and definition of done
  • Respond to questions and clarification requests
  • Gather timely, actionable feedback from team members and communicate them back to Data and Analytics
  • Champion adoption and engagement of data deliverables/solutions within your teams
  • Provide testing and usability feedback
  • Enablement/documentation

Suggested Meetings

  • Stakeholder/Analyst meetings
    • Bi-Weekly or Monthly meetings to share updates of ongoing projects, talk through upcoming projects, priorities, and planning, and share new and notable work from other parts of the analytics organization.
  • Project Requestor/Point of Contact meeting
    • For the duration of a project, weekly or bi-weekly meeting to share updates, blockers, timelines, and progress
    • Depending on the scale of the project, these meetings could alternatively be asynchronous status updates
  • Retrospectives
    • Retrospectives will be held at the conclusion of any cross-functional, multi-month project

Project Intake

The Data and Analytics team will accept project/enhancement requests through GitHub issues in the Sourcegraph analytics repository. At this time, requests that are not attached to a GitHub issue will not have an assigned analyst/engineer or expected completion date, and will not be tracked by the team.

Examples of requests that require an issue:

  • New dashboard or enhancement to existing dashboard
  • Ad-hoc analysis (e.g. “I would like to know the number of MAUs for the Batch Changes feature.”)
  • Implementation of new business metrics (e.g. “Can we start tracking page views of our case studies?”)
  • Bug fixes in data pipeline, transformations, or reporting (e.g. “I expect this value to be 100 and it shows as 50.”)

When creating GitHub issues, please include as much relevant information as possible. Please use the relevant issue template in the repository and fill out the requested information. If no template matches, create a blank issue and include as many details around your request as possible.

This information is useful:

  • The problem: Describe the problem or question you have.
  • End state: What is the end state of the project? What decisions will be made? Be as specific as possible (i.e. if the end state is a graph, draw out the graph in a tool or paper)
  • The why: What will this request be used for? How does it support our goals?
  • Timeline: What’s the timeline of the project? Is it urgent? When does this need to be delivered, and how will it be followed up on in the future?
  • People: Who is involved, and what are the expectations of each person? Who will be responsible for driving the project forward? Does each person have the necessary bandwidth for driving the project forward? Does each person have the necessary bandwidth to uphold the expectations asked of them?
  • Frequency: Is this a one time ask or something that is needed ongoing? If ongoing, what is the cadence (daily, weekly, monthly, etc…)

A Data and Analytics team member will triage and assign issues to the relevant team member during sprint planning for items that are not time-sensitive or urgent.

For time-sensitive or urgent requests, please tag the issue with the urgent label. This will make the GitHub issue appear in the #analytics channel in Slack to ensure visibility, and where you can follow up with more details/asks.