agile scrum and tech docs survey - Dashboard
100%
timelapse Completion Rate
48
flag Completed
2,067
remove_red_eye Viewed
48
play_circle_outline Started
0
remove_circle Dropouts
30 mins
access_time Average Time
 
Countries Responses
US 60.42%
CA 8.33%
DE 4.17%
SE 4.17%
IN 2.08%
NL 2.08%
BY 2.08%
NZ 2.08%
PH 2.08%
RO 2.08%
DK 2.08%
RU 2.08%
FR 2.08%
GB 2.08%
UA 2.08%
Total 100.00%
"Docs as code" should include not only using engineering tools for docs but also aligning documentation work methodologies with engineering work methodologies (such as agile scrum).
Answer Count Percent
20% 40% 60% 80% 100%
Strongly disagree 2 4.17%
Disagree 3 6.25%
Neutral 8 16.67%
Agree 19 39.58%
Strongly agree 15 31.25%
Other 1 2.08%
Total 48 100 %
Docs as code should include not only using engineering tools for docs but also aligning documentation work methodologies with engineering work methodologies (such as agile scrum). - Text Data for Other
08/23/2019 42015314 When possible
I like the agile scrum approach for docs that you recommend in this article.
Answer Count Percent
20% 40% 60% 80% 100%
Strongly disagree 1 2.08%
Disagree 2 4.17%
Neutral 5 10.42%
Agree 26 54.17%
Strongly agree 14 29.17%
Other 0 0%
Total 48 100 %
I like the agile scrum approach for docs that you recommend in this article. - Text Data for Other
No Data To Display
My approach at work loosely follows what you describe in this article.
Answer Count Percent
20% 40% 60% 80% 100%
Strongly disagree 3 6.25%
Disagree 9 18.75%
Neutral 8 16.67%
Agree 19 39.58%
Strongly agree 7 14.58%
Other 2 4.17%
Total 48 100 %
My approach at work loosely follows what you describe in this article. - Text Data for Other
08/23/2019 42015314 Past, current, and future tickets are part of my Doc Change Control spreadsheet. I share the sheet with my teams and management, but am looking forward to assigning points and building out a report. Fun!
08/21/2019 41837601 Hard to explain.
I review my docs following a similar process as you describe (review with 1. doc team, 2. product team, 3. other stakeholders such as support and field engineers, 4. legal, 5. beta partners).
Answer Count Percent
20% 40% 60% 80% 100%
Strongly disagree 6 12.5%
Disagree 17 35.42%
Neutral 6 12.5%
Agree 14 29.17%
Strongly agree 4 8.33%
Other 1 2.08%
Total 48 100 %
I review my docs following a similar process as you describe (review with 1. doc team, 2. product team, 3. other stakeholders such as support and field engineers, 4. legal, 5. beta partners). - Text Data for Other
08/21/2019 41837601 It is just me.
I prefer to join engineering scrums rather than creating my own documentation scrums
Answer Count Percent
20% 40% 60% 80% 100%
Strongly disagree 2 4.17%
Disagree 10 20.83%
Neutral 8 16.67%
Agree 16 33.33%
Strongly agree 12 25%
Other 0 0%
Total 48 100 %
I prefer to join engineering scrums rather than creating my own documentation scrums - Text Data for Other
No Data To Display