China Translation Blog     powered by www.chinafanyi.com 2007


«Mar.2024»
12
3456789
10111213141516
17181920212223
24252627282930
31


公告

欢迎来到萝卜的空间

本空间所有日志信息或文章及相关资料皆萝卜原创或精心整理。如转载复制,请注明来源!建此空间的目的在于——以文会科技翻译同行,结识一批志同道合、志趣相投的译友,共同为科技翻译贡献自己的微薄之力!


我的分类(专题)

日志更新

最新评论

留言板

链接

我的搜狐博客:http://runrola.blog.sohu.com/


Blog信息
blog名称:Tech Writer—萝卜在跑步
日志总数:141
评论数量:12
留言数量:1
访问次数:1200192
建立时间:2008年4月15日


广告位招租





[TW]转载:Technical writer and project management
Rola 发表于 2011/10/10 15:59:00
本文转载自:http://www.cnblogs.com/techcomm/archive/2011/03/10/1980262.html

For technical writers, it is not surprising to receive documentation request a week or so before product release or launch. Situation worsens when lone technical writer is assigned to handle multiple product lines with very tight, and often conflicting schedules, leaving virtually no margine for internal technical review, peer review, language and style review. However, on the other hand, technical writer is directly responsible for the quality matrix of documentation: correctness, completeness, consistency, clarity, structure and style. So how to ensure the quality while meet the deadline, the answer is: plan in advance and review in details.

I have been working under different organization structures with my current and former employers: under PM, designer, tester, marketing, application engineer and customer support. It is not esay to pick out one and declare the best solution for technical communication -- all of them are target customer of documentation. Therefore, in order not to miss any valuable comments or feedback, lead time with controled process is essential for ensuring the quality. If technical writer is involved in project meeting, one point; if involved in project planning, ten points.

Pros:

  • Early involvement secures writer resources by planning in advance
  • Writer can control and drive doc development: to proactively ask for information rather than merely waiting for "input"
  • Writer knows product better: to view the benefits, potential issues and limitations from user point of view
  • Ample review time (80% doc errors are found in rounds of review; even some system bugs are discovered in doc review)
  • Reduce SME load in conventional documentation: SME no longer needs to write the first drafts and have technical writer "edit the language and style"
  • Review meeting with stakeholders involved: eliminate future dispute over the content
  • Review meeting with SME who owns part of the product: to help SME understand the parts they are not in charge of and view the product as a whole

Cons:

  • Technical writer are most likely to get overloaded
  • Communication cost increased

阅读全文(4494) | 回复(0) | 引用(1299)作者的个人空间

 



发表评论:
昵称:
密码:
主页:
标题:



博客频道首页 | 联系我们 | 博客注册 | 博客登陆| 中国译典| 译典论坛| 翻译文库| 在线翻译| 网站首页

Powered by Chinafanyi.com © Copyright 2004. All rights reserved.
Processed in 0.060 second(s), page refreshed 3606343 times.