Information Technology Reference
In-Depth Information
Figure 8.1
The process environment.
case for processes in general. It is better to withdraw such pro-
cesses. As an extension to this point, do not define a process for
the 20 percent of the team that will not follow it anyway.
The complexity and criticality of the system being managed by the
processes
. There is a distinct difference between a process required
to select a new corporate CEO compared to the one to hire a
marketing intern for the summer.
Project constraints related to schedules, resources, and quality
expectations
. Sometimes, the processes selected are overkill for a
project of that type.
Take Care of the Basics
A good process provides a predictable operating framework to take care
of the basics. This relieves one of the need to think and reinvent the steps
each time one embarks on a project. Coding standards, definition of IDEs
(integrated development environments) and toolsets, naming conventions,
and documentation styles or templates can be decided once, and followed
without further discussion at each stage of the development. Such pro-
cesses allow one to focus one's energy on the creative and high-risk
aspects of the project.
Include Communication Mechanisms
Communication is the cornerstone of any good process. A good process
provides not just the mechanisms for this communication, but also
