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.
Subject:60 Hours per Week at Level 1 Process Maturity From:"Anthony Markatos" <tonymar -at- hotmail -dot- com> To:TECHWR-L -at- LISTS -dot- RAYCOMM -dot- COM Date:Thu, 02 Sep 1999 15:12:07 PDT
Question to all listserv members:
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?
Note: If Process Maturity Level (also called Capability Maturity Level)= 5,
the organization has (among other things) a very sophisticated project
management system in place. If Process Maturity Level = 1, things are done
in a very add-hoc fashion. Level 0 is anarchy.
All responses appreciated
Tony Markatos
(tonymar -at- hotmail -dot- com)
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
