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.
> I this that process maturity is one reason for frenetic activity
> occurring, especially as deadlines are approached, and long hours being
> worked. I would say that it is only an element of the problem.
>
> Clearly, if staff do not have the necessary skill to do a task efficiently
> it will take longer and if a department is understaffed initially,
> workloads will increase dramatically.
>
> Phil Saum
>
> -----Original Message-----
>
> It has been my observation that, within the software industry, the average
>
> total hours worked per week is inversely related to the organizations
> Process Maturity Level. That is, as the Process Maturity Level decreases
> (moving from 5 to 0), the avg number of hours worked increases. Has this
> been your experience also?
