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.
Deviation must be done only if it enhances the goal.
The deviation must be incorporated into the plan so the change to the plan
ripples through all related factors.
Suppose the plan was to install a major release SQL database application
upgrade for enterprise deployment on 300 servers at 15 sites around the
world. It includes all the normal backup, rollback, delta/benchmarks,
testing, and deployment tasks. It has 30 steps (obviously, it would be much
more). Now, at around step 10, it is determined that because of something
else, the OS that the database is to be installed on changes from Win2000
Enterprise Server to Linux. Obviously, if step 20 was "Check MS for all
required SQL Security Patches", that step (along with many others) is no
longer valid. So, from step 10 on, you must rewrite it as new plan.
Senior Technical Writer
jposada -at- book -dot- com
Although she lives with seven other men, she's not easy.
------ Magic Mirror
--- John Posada <john -at- tdandw -dot- com> wrote:
> The bad way to work a plan is to create the plan, then stick to that plan
> without deviation, saying...sorry, it's not in the plan.
Well, a good plan is more like a good idea. You follow it when it makes
and deviate from it when that makes sense.
This is why reason is more important than process. With reason, you make
decisions based on fact and current events, not blind obedience to the
Unfortunately, a lot of folks have a tough time with reason, and therefore
resort to the "if its not in the plan, we don't do it" sort of thinking.
Purchase RoboHelp X3 in April and receive a $100 mail-in
rebate, plus FREE RoboScreenCapture and WebHelp Merge Module.
Order here: http://www.ehelp.com/products/robohelp/
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.