Having a technical writer on a team is taken for granted or as something that raises the question “Who are you? What are you doing here? "
But when a tech writer leaves the team, his absence is like missing a small piece in a large, complex puzzle. You can do without this piece. But an attentive observer will notice that the picture of the team is not complete, there is clearly someone missing in it.
, . .
?
, . . .
.
.
.
.
.
.
1.
. ? -, : .
. , . , . , . - , , .
, . . . . ? ? , ?
. - . , , . .
, , , . , , 1 1 .
, . . – – , , , , – ?
– , . , , . , . , ? ?
: , . – , , . ( .) .
- , , ( ). - , ? , , - , - , ?
– . . . , – – . , . . , ?
2.
, n- . . , , .
. . , … .
, , . , , , . . , , .
, . , .
– . – ! , , .
. . , .
: . . , , - .
, “ ” “ ”, , . . – , . , … . , , . , .
. . , ?
3.
. . -, “ ” , , , – .
-, , , .
“”? , -? , -?
: , , , – -.
: . , , , . . , . !
- -, , , , , . . , , ?
4.
– -! .
, . , , .
– . . , ? .
. , , , . , – – , , .
, , , . 10-15? 2-3 , , , , ?
. . , . , . - . ( .)
: , - , , . , , . , .
, – . – , product owner. , – , . , ?
5.
, , , . , . , .
, “ ” “ , ”, “ , ”, .
: , . ?
: , . 1 1 , , ( ), , .
. , . , , .
, , , , , . , . , . .
: . , ? ? ? , – . - , .
, , , . . , . , . , , .
But if you can't give yourself an answer to any of the questions above, just don't hire a technical writer. Let developers, QA engineers, analysts, architects, team leads, managers write the documentation. Anyone. And a little later you will be able to hire a technical writer, because you will understand why you still need him.
Good luck!