TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I see it as an advantage to have frequent releases, as your developer
colleagues quickly learn how to manage their bug cases in a way that
reduces the workload for everyone involved.
If the frequent releases also include new functionality, then figure out
how docs work can be part of the feature development.
If input-, review- and publication processes take up too much of your time,
take it up as a team responsibility to see how the workload can be
distributed among different people, or how the processes can be improved.
Can developers or support engineers deliver text for bug cases? Do they
have good mechanisms for sorting which bug cases should be included in the
release notes? How is your review process? Can anything be automated?
Personally, I prefer working in agile environments, as it's always clear
what the developers are working on and what's up next (if they truly work
agile and don't use the word agile for not having any useful processes!).
Also, you can finish small bits of content while the developers are working
on a new feature and have it all fresh in mind.
On 25 December 2017 at 21:43, Gene Kim-Eng <techwr -at- genek -dot- com> wrote:
> Create a comprehensive note for the first release. The you just need to
> update it with changes as needed.
> Gene Kim-Eng
> On 12/24/2017 10:31 PM, Erika Yanovich wrote:
>> The rule over here is to accompany each customer release with release
>> notes. In Agile environment, this is could happen every 2 weeks. How do you
>> deal with the extra effort?
> This email has been checked for viruses by Avast antivirus software.
> Visit TechWhirl for the latest on content technology, content strategy and
> content development | http://techwhirl.com
> You are currently subscribed to TECHWR-L as charlotteclaussen -at- gmail -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com