├── README.md
├── community-items.md
├── documentation-items.md
├── outcome-items.md
└── writing-and-shipping-code-items.md


/README.md:
--------------------------------------------------------------------------------
1 | # State of the Octoverse 2021 survey items
2 | Survey questions from State of the Octoverse 2021
3 | 
4 | * [Outcome items](/outcome-items.md)
5 | * [Writing and shipping code items](/writing-and-shipping-code-items.md)
6 | * [Documentation items](/documentation-items.md)
7 | * [Community items](/community-items.md)


--------------------------------------------------------------------------------
/community-items.md:
--------------------------------------------------------------------------------
 1 | # Community items
 2 | 
 3 | * [Mentorship available](#mentorship-available)
 4 | * [Clear governance](#clear-governance)
 5 | * [Community demonstrates trust and respect](#community-demonstrates-trust-and-respect)
 6 | 
 7 | ## Mentorship available
 8 | | Survey item |
 9 | |---|
10 | | People are interested in mentoring others<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
11 | | People who want mentorship can get it<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
12 | | My team/project explicitly offers mentorship to new contributors or new hires<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
13 | | New contributors or new hires receive friendly code reviews<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
14 | | New contributors or new hires receive timely code reviews<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
15 | 
16 | ## Clear governance
17 | | Survey item |
18 | |---|
19 | | Who has the authority to perform certain tasks (like making commits)<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul> |
20 | | Who has influence over decisions<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul> |
21 | | How to gain authority, influence, or rank<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul> |
22 | 
23 | ## Community demonstrates trust and respect
24 | | Survey item |
25 | |---|
26 | | I understand what the intended purpose of my work is<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
27 | | My team allows me to make my own decisions about managing my time<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
28 | | My team allows me to use my personal judgement in carrying out my work<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |


--------------------------------------------------------------------------------
/documentation-items.md:
--------------------------------------------------------------------------------
 1 | # Documentation items
 2 | 
 3 | * [Share knowledge](#share-knowledge)
 4 | * [Source knowledge](#source-knowledge)
 5 | * [Clear documentation available](#clear-documentation-available)
 6 | * [Clear information search](#clear-information-search)
 7 | 
 8 | ## Share knowledge
 9 | | Survey item |
10 | |---|
11 | | I share knowledge and expertise publicly in forums and message boards (e.g., StackOverflow, HackerNews, GitHub Discussions)<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
12 | | I am a regular contributor to official team or project/org documentation<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
13 | | I edit and improve existing documentation for projects<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
14 | | I share knowledge and expertise publicly using videos (e.g., YouTube, TikTok, etc.<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
15 | ## Source knowledge
16 | | Survey item |
17 | |---|
18 | | I look for a timestamp or other way to know that I am reading the most up-to-date info<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul>|
19 | | I judge the validity or usefulness of information by the number of upvotes it has<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul>|
20 | | Detailed documentation plays a critical role in my work<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul>|
21 | | I follow tutorials to learn how to apply a concept to my own work<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul>|
22 | | I want to know best practices for working with a tool or product<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul>|
23 | | I prefer to use videos or vlogs (like YouTube or TikTok) to learn about new ideas or solve problems<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul>|
24 | | I prefer forums (like StackOverflow, HackerNews, or GitHub Discussions) to learn about new ideas or solve problems<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul>|
25 | ## Clear documentation available
26 | | Survey item |
27 | |---|
28 | | Documentation is easy to read for people outside the project or team<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul>|
29 | | Documenation makes dependencies clear<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul>|
30 | | Comments describe how each part of the code works<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul>|
31 | 
32 | ## Clear information search
33 | | Survey item |
34 | |---|
35 | | New contributors or new hires can easily find solutions<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul> |
36 | | It is obvious where to go for help<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul> |
37 | | It is obvious where to ask questions<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul> |


--------------------------------------------------------------------------------
/outcome-items.md:
--------------------------------------------------------------------------------
 1 | # Outcome items
 2 | 
 3 | * [Hybrid/Remote work](#hybridremote-work)
 4 | * [Software delivery performance](#software-delivery-performance)
 5 | * [Collaborate with others](#collaborate-with-others)
 6 | * [Empowered to work](#empowered-to-work)
 7 | * [Make progress](#make-progress)
 8 | * [Feel fulfilled](#feel-fulfilled)
 9 | * [Identify with the team/community and its mission](#identify-with-the-teamcommunity-and-its-mission)
10 | 
11 | ## Hybrid/Remote work
12 | | Survey item |
13 | |---|
14 | | Before the pandemic, I typically worked with others: <ul><li>Collocated: In an office all the time or part-time</li><li>Hybrid: Some team members were in an office and others were remote</li><li>Fully remote: All team members were remote</li></ul>|
15 | | After the pandemic, I expect to work with others:<ul><li>Collocated: In an office all the time or part-time</li><li>Hybrid: Some team members will be in an office and others will be remote</li><li>Fully remote: All team members will be remote</li></ul>|
16 | 
17 | ## Westrum
18 | | Survey item|
19 | |---|
20 | | On my team, conflicts are resolved quickly<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul>|
21 | | On my team, information is actively sought<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul>|
22 | | On my team, responsibilities are shared<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul>|
23 | | On my team, cross-functional collaboration is encouraged and rewarded<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul> |
24 | | On my team, failure causes productive inquiry<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul> |
25 | | On my team, new ideas are welcomed<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul> |
26 | ## Software delivery performance [^DORA]
27 | | Survey item |
28 | |---|
29 | | For the primary application or service you work on, what is your lead time for changes (that is, how long does it take to go from code committed to code successfully running in production)?<ul><li>More than six months</li><li>One to six months</li><li>One week to one month</li><li>One day to one week</li><li>Less than one day</li><li>Less than one hour</li><li>I don’t know or not applicable</li></ul> |
30 | | For the primary application or service you work on, how often does your organization deploy code to production or release it to end users?<ul><li>Fewer than once per six months</li><li>Between once per moth and once every six months</li><li>Between once per week and once per month</li><li>Between once per day and once per week</li><li>Between once per hour and once per day</li><li>On demand (multiple deploys per day)</li><li>I don’t know or not applicable</li></ul> |
31 | | For the primary application or service you work on, what percentage of changes to production or releases to users result in degraded service (for example, lead to service impairment or service outage) and subsequently require remediation (for example, require a hotfix, rollback, fix forward, patch)? [^2]<ul><li>0-15%</li><li>16-30%</li><li>31-45%</li><li>46-60%</li><li>61-75%</li><li>76-100%</li><li>I don’t know or not applicable</li></ul> |
32 | | For the primary application or service you work on, how long does it generally take to restore service when a service incident or a defect that impacts users occurs (for example, unplanned outage, service impairment)?<ul><li>More than six months</li><li>One to six months</li><li>One week to one month</li><li>One day to one week</li><li>Less than one day</li><li>Less than one hour</li><li>I don’t know or not applicable</li></ul> |
33 | ## Collaborate with others
34 | | Survey item|
35 | |---|
36 | | I work with other people<ul><li>None of the day</li><li>A little of the day</li><li>Some of the day</li><li>Much of the day</li><li>All of the day</li></ul> |
37 | | I help other people<ul><li>None of the day</li><li>A little of the day</li><li>Some of the day</li><li>Much of the day</li><li>All of the day</li></ul> |
38 | | On an average workday, I have meetings:<ul><li>Never</li><li>Once</li><li>Twice</li><li>Three or four times</li><li>Five or more times</li></ul> |
39 | | I have the tools I need to do my job<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul>|
40 | ## Empowered to work
41 | | Survey item|
42 | |---|
43 | | My team allows me to make my own decisions about managing my time<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
44 | | My team allows me to use my personal judgement in carrying out my work<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
45 | | I understand what the intended purpose of my work is<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
46 | ## Make progress
47 | | Survey item |
48 | |---|
49 | | I do a lot of work<ul><li>None of the day</li><li>A little of the day</li><li>Some of the day</li><li>Much of the day</li><li>All of the day</li></ul> |
50 | | I make progress toward my goals <ul><li>None of the day</li><li>A little of the day</li><li>Some of the day</li><li>Much of the day</li><li>All of the day</li></ul> |
51 | | I do high-quality work <ul><li>None of the day</li><li>A little of the day</li><li>Some of the day</li><li>Much of the day</li><li>All of the day</li></ul> |
52 | ## Feel fulfilled
53 | | Survey item|
54 | |---|
55 | | I feel happy when I am working on software<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
56 | | I feel worthwhile when I am working on software projects <ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul>|
57 | | Software development is satisfying to me <ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul>|
58 | | I feel empowered when dealing with difficult problems in my team <ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul>|
59 | | Doing development at work or in my open source projects is meaningful to me <ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul>|
60 | | When I write code or work with my taem, I feel like I'm making valuable contributions <ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul>|
61 | ## Identify with the team/community and its mission
62 | |Survey item|
63 | |---|
64 | | Working on my team or on my projects is meaningful to me<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul> |
65 | | I feel a strong sense of belonging to this team / on project<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul>|
66 | | I identify with the mission and purpose of my team or project<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul>|
67 | | I care about the future of my team or project<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul>|
68 | | I identify strongly with my organization / open source project<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul>|
69 | | My contributions are valued in my organization/open source project/the developer community<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul>|
70 | 
71 | [^DORA]: We thank the DORA team for developing the measures used in the software delivery performance section of this survey
72 | [^2]: This item didn’t load, which is typical for the DORA measures when used in constructs, which is consistent with prior research, see Accelerate 2018 and prior SODRs. All four measures are still predictive when used in a clustering classifier, see [2021 State of DevOps Report](https://cloud.google.com/devops/state-of-devops) (registration required)


--------------------------------------------------------------------------------
/writing-and-shipping-code-items.md:
--------------------------------------------------------------------------------
 1 | # Writing and shipping code items
 2 | 
 3 | * [Detailed code reviews](#detailed-code-reviews)
 4 | * [Easy to reuse code](#easy-to-reuse-code)
 5 | * [Clear contribution and support](#clear-contribution-and-support)
 6 | * [Code designed for reuse](#code-designed-for-reuse)
 7 | * [Use automation to ship code](#use-automation-to-ship-code)
 8 | 
 9 | ## Detailed code reviews
10 | | Survey item|
11 | |---|
12 | | Pull requests /merge requests include descriptions about why the change is needed<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
13 | | Pull requests /merge requests describe how the change addresses the need<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
14 | | Code reviews improve the quality of our codebase<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul> |
15 | | Our team has a culture of delivering positive, helpful feedback through code review<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul> |
16 | | I enjoy my team's code review process<ul><li>1 (Strongly disagree)</li><li>2 (Disagree)</li><li>3 (Neither Agree or Disagree)</li><li>4 (Agree)</li><li>5 (Strongly Agree)</li><li>Prefer not to answer</li></ul> |
17 | | In my team, organization, or project, most code reviews are typically completed by:<ul><li>No reviewers; we don't do formal code reviews</li><li>One reviewer</li><li>Two or more reviewers</li></ul> |
18 | 
19 | ## Easy to reuse code
20 | | Survey item |
21 | |---|
22 | | I would like to use or continue to use code or libraries from outside my team or repository<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
23 | | I currently use code or libraries from outside my team or repository<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul>|
24 | 
25 | ## Clear contribution and support
26 | | Survey item |
27 | |---|
28 | | I know how to submit pull requests (e.g. there are contribution guidelines)<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
29 | | Contributions get attention quickly<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
30 | | They use common toolchains and communication channels<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
31 | | I can tell whether other projects' code will be supported in the future<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul>|
32 | | I know how to submit issues or feature requests<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
33 | | I can reuse individual code components<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
34 | 
35 | ## Code designed for reuse
36 | | Survey items |
37 | |---|
38 | | Accept pull requests from people outside the project or team<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul>|
39 | | Respond to pull requests or issues from people outside the project or team quickly<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
40 | | Describe whether the code will be supported in the future<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
41 | | Design documentation to make dependencies clear<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
42 | | Write comments that describe how each part of the code work<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
43 | | Modularize code so that people can reuse individual <ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
44 | 
45 | ## Use automation to ship code
46 | | Survey item |
47 | |---|
48 | | Are confident tests will pass<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
49 | | We run automated builds and automated tests against the builds when our code changes<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
50 | | We release new code through automated pipelines<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
51 | | Bugs and defects are captured by automated tests<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
52 | | Our bug finding process is efficient and effective<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
53 | | We continuously merge code changes into the main branch as often as possible<ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |
54 | | If a build fails, we prioritize troubleshooting the <ul><li>Never</li><li>Rarely</li><li>Sometimes</li><li>Often</li><li>Always</li></ul> |


--------------------------------------------------------------------------------