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.
R.E. "I don't know what "agile has its own protocol" is supposed to mean."
It means that there's an Agile way of doing things, and an Agile way of talking about things. A specific example is in the subject line for this thread... Should tech writers be Pigs or Chickens? That's a question about Agile protocol -- protocol as a predefined mode of conduct. If you are currently on a waterfall project, and you will never work on an Agile project, then this thread will be meaningless to you. If you're on an Agile project, then it might interest you to consider whether you're involved at the right level -- in Agile speak, whether you're a pig or a chicken.
cud
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.
