Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab UX Research
GitLab UX Research
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 249
    • Issues 249
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 2
    • Merge requests 2
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab UX ResearchGitLab UX Research
  • Issues
  • #56

Closed
Open
Created Mar 17, 2018 by Sarah Jones@sarahj🚼Maintainer

DevOps Insights: Operations Report & User Interviews

As part of the UX team's OKR to: 'Establish Operations Engineers as a first class citizen' we conducted a survey to test the following assumptions:

  • Operations Engineers focus on keeping things running smoothly and efficiently. They take the output of development and run it in production. With DevOps movement, they are trying to talk more closely with developers.

  • Operations Engineers aren't different people. At many organizations, DevOps means one person does both development and operations. You wrote it, you operate it, you carry the pager.

Results showed that the second statement was found to be most true.

We also found that within small organisations (less than 100 employees) respondents responsible for undertaking DevOps tasks identified as a Software Engineer. In contrast, respondents working for mid to large organisations (101+ employees) identified as a DevOps Engineer in addition to Software Engineer. Operations Engineer as a job title was not as popular as DevOps or Software Engineer.

We've comprised survey results into a report format:

https://drive.google.com/file/d/1sgPETOKc53QBLvd438gPljRRjeBOm8jr/

The report covers

  • Who is responsible for DevOps? (Team sizes, common tasks, etc)
  • Challenges
  • Technologies
  • Monitoring
  • Continuous Integration and Auto DevOps

We conducted users interviews on Monday 26th and Tuesday 27th March to discuss survey answers in more detail and to establish what GitLab could potentially offer those working in Operations.

We recorded each interview, you can listen to them here:

  • User 1
  • User 2
  • User 3
  • User 4
  • User 5

We've comprised findings from the user interviews into a report format:

https://drive.google.com/file/d/18r1cU8NVxFEHcI6RaJEQ_c-_-7SCNpAr/

The report covers

  • Who we spoke with
  • What users want from a monitoring solution
  • How GitLab CI can be improved
  • How GitLab (in general) can be optimised further

We've scheduled user interviews for Monday 26th and Tuesday 27th March to discuss some survey answers in more detail and to establish what GitLab could potentially offer those working in Operations.

If you have any questions/prototypes that you would like to be included in the interviews. Please ensure they are posted in this issue by Friday 23rd March. Thank you.

cc @tauriedavis @pedroms @dimitrieh @cperessini @jkarthik @hazelyang @katokpara @sarrahvesselov @markpundsack @bikebilly @joshlambert

Edited Apr 03, 2018 by Sarah Jones
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking