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.
Believe me, I want it to work and as I mentioned it did for a while and everyone was diggin' it. We were pretty much doing by the book....but we got sloppy. Stopped payin the pig when we are late. Lost our SM. Just finish almost a whole release of hardening. Buzz kill.
Will check out the video, thanks Tony.
> The product managers need to prioritize the levels and types of
> documentation required by each product. A lot of companies think that
> because Product A rolled out with a suite of documents, then Product B
> needs the same suite, even if the intended user base is different.
> "Just because we've always done this" is not a good reason to
> perpetuate the crazy cycle.
> I would also push for more content reuse, and for more content
> generation by engineers, especially in the case of highly technical
> information. Some great advice can be found in Robert Levy's
> presentation on "Flying Solo: When you're the only one with a pencil"
> yes... I watched the whole thing. You'll love the changes to his
> response when asked to take on more than physically possible.
> Regarding scrum, since stand-up meetings are only supposed to be 15
> minutes to discuss status and roadblocks, make sure the master knows
> to keep discussions on track: problems are only to be identified, but
> not solved (or even hashed), during these meetings.
> If you have multiple conflicting meetings, ask to have your say first
> to point out what you need, then get back to work.
> Personally, I hate meetings with a passion, but I enjoy participating
> in the development of the product. I've found that from a core
> documentation perspective, I cut a lot of corners by supplying the
> engineers with templates for their requirements, specifications, and
> design docs.
> Create and publish documentation through multiple channels with Doc-To-Help.
> Choose your authoring formats and get any output you may need. Try
> Doc-To-Help, now with MS SharePoint integration, free for 30-days.
> LavaCon 2010 in San Diego Sept 29 - Oct 2 is now open for registration.
> Use referral code TECHWR-L for $50 off conference tuition!
> See program at: http://lavacon.org/
> You are currently subscribed to TECHWR-L as katkuvinka -at- hotmail -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit http://lists.techwr-l.com/mailman/options/techwr-l/katkuvinka%40hotmail.com
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwr-l.com/ for more resources and info.
> Please move off-topic discussions to the Chat list, at:
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
LavaCon 2010 in San Diego Sept 29 - Oct 2 is now open for registration.
Use referral code TECHWR-L for $50 off conference tuition!
See program at: http://lavacon.org/
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-