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.
Didn't see this in the archive anywhere, so here goes:
I want to create a kind of status form for a particular project where I
can log things like: issues currently unresolved w/ the developers,
tasks held up for other reasons, wanted future improvements that aren't
going to get in this release, etc.
Project and task management in this situation is rather loose, so this
kind of info isn't getting logged anywhere but in my and the other
writer's heads, which are getting rather full. :)
All of the project status reports I've ever seen or have in my
reference works are more oriented toward time and cost tracking, etc.
Does anyone have suggestions for ways to layout this kind of document,
items and headings to include, and/or ways to make it easy to use?
If anyone has a template for a similar document that they'd be willing
to share w/ me or point me to online or in a book, that would be great
as well.
Have a great weekend,
Laura Tarwater
ltarwater -at- yahoo -dot- com
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
