10 minutes video series from Rahul Karn
In this video, Rahul Karn from Information Developers Foundation shares his view about the use of automation in technical writing.
According to Rahul technical communicators should not fear automation and try to automate content creation as much as possible so that writers can focus on more productive work.
In this video, he quotes the example of many publishing houses which is already using bots for automated content creation.
InfoDev also provides training of technical communication "Masters in Information Development" in the training Rahul Karn talk in details about how to identify what you should automate, possibilities to automate API documentation and Release notes.
Technical writing effort estimation in Scrum process.
In this video, Rahul Karn is explaining why we do not estimate the documentation separately. Use of Kanban in the technical documentation.
Use of poker card for estimation.
In the scrum, during planning meeting team give story points to the user story that also includes documentation task. We do not separately estimate it.
In technical writing Information gathering is considered to be a most challenging part and many Information gathering techniques for technical writers are available. In this video I talk about the use of Information radiators like clear user stories, Epics or well written SRS/FRS. Follow basic etiquette of meeting like to be on time, book a quite place. The information gathering meeting should be time boxed, an agenda should be fixed, if possible send questions prior to the meeting. Go well prepared, do your homework, frame your questions properly.