1. Introductory
What role do you have in the software department?
What do you do?
How might this change or stay consistent with using the Telemetry Dashboard?
Have you participated in a race before? (90% probably no)
2. Data prioritization
Are you familiar with data visualization and the tools associated with it?
What data do you want to focus primarily on? (could do a card exercise similar to the one in the hardware guide)
What current tasks/projects in strategy require you to deal with lots of data viewing/visualization?
How much data do you usually view at once when you’re doing [task]?
The [task] will be based on what current tasks/projects they mention in the previous question
At what point is too much data overwhelming?
3. Process involved in performing tasks
Can you tell me about strategy’s role during the race?
What will strategy use the telemetry dashboard for during the race?
Can you walk me through a scenario of using the telemetry dashboard during the race?
[set-up question to find relevant task/scenario to dig into]
Walk me through how you’d normally do this task
What are your most common usage patterns?
[set-up question to find relevant task/scenario to dig into]
Are there any technical obstacles that you must typically go through when navigating a task?
4. Stakeholder stuff
What programming languages are you familiar with? (To get a better understanding of what languages people in the software dept know already)
What programming language will be used for the telemetry dash
Do you have experience with working on responsive designs?
Do you have past experience with working on telemetry dashboards or general data visualization?
Good question to ask the actual devs later on
What were your responsibilities for them and were you able to use them effectively?
What stacks & programming languages did it incorporate?
[set-up question to find the relevant task to dig into]
Describe the process you have for a programming task, from requirements to delivery (SDLC).
Does the team plan on using Agile software development when working on telemetry or do you have another ideation in mind?
What are your thoughts on software testing?
If a bug were to appear in the telemetry dashboard, how would you go about implementing your error handling?
How do you explain technical challenges to stakeholders who do not have technical knowledge or background in software?
Ideally how much time do you want to spend when working/performing on a specific task?
How do you determine a project’s success?