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.
If a job posting is calling for SDLC experience, they probably want someone who
will be comfortable documenting theirs. This is common if the company is
developing in a regulated environment where their entire development process
must be documented from end-to-end. User manuals will not differ significantly,
but you'll probably also be writing a lot of internal, "under the hood" stuff
that documents the actual development of the product.
Gene Kim-Eng
----- Original Message -----
From: "Tech Writer" <tech-writer -at- live -dot- com>
>
> I've seen job postings requesting SDLC experience for tech writers. I've
> worked within software delivery cycles, but have never been aware of a name
> for the particular methodology being employed.
>
> For those that have worked under a strict standard methodology, how does it
> impact your technical writing? For instance, how does your documentation
> differ between an Agile development vs Scrum vs Unified Process?
Gain access to everything you need to create and publish documentation,
manuals, and other information through multiple channels. Choose
authoring (and import) as well as virtually any output you may need. http://www.doctohelp.com/
- Use this space to communicate with TECHWR-L readers -
- Contact admin -at- techwr-l -dot- com for more information -
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
