Hardware Reference
In-Depth Information
Table 1.
(
continued
)
17-Manage
Compe-
tence
It's difficult to know
what the
competence of each
project member is.
Create a competence database for gathering information of
members' competence levels at different sites. Otherwise at
least site manager and/or project manager knows the
competence of team members. Define competence levels and
criteria for them. Define the areas of competence you want to
monitor. Ask site managers and /or project managers to gather
information about their team members.
18-Notice
Cultural
Differences
Certain methods are
appropriate in one
nation's culture and
might not be
appropriate in
another.
Raise the awareness of your team nations' culture for team
members. Use site visits, ambassadors and liaisons, if possible.
Notice cultural differences when you are applying
GSD Strategy
and
Work Allocation
.
Use Common Processes
. Use
Communication Tools
and
Common Repositories and Tools
.
Allow local approaches in processes, tools, meeting methods etc.
to decrease problems with cultural differences, if they do not
disturb common processes etc.
Table 2.
An example of GSD pattern
Name
:
GSD 04
Divide and Conquer with Iterations
Problem
:
One big project plan is a risk in distributed development and long feedback loops.
Solution
:
Implement the following actions:
Plan many iterations to describe the project plan
Develop new application architecture and module structure during first iterations,
if needed
Explore the biggest risks (e.g. new technologies) in the beginning of a project
The length of iteration can be e.g. 2-4 weeks to improve control and visibility.
Main site can have 4 weeks iteration and other sites 2 weeks to improve
visibility.
Resulting
Context:
Iterations improve the visibility of a project and motivation of project members
Iterations make it easier to control a project when you split the whole project into
many manageable parts
Administration work is increased with many iterations
3.2 Pattern Language Organization with PRINCE2
In this section the pattern language organization is described based on the PRINCE2
project management method [14]. The PRINCE2 (PRojects IN Controlled Environ-
ments2) process overview is presented in Figure 1.
PRINCE2 is comprised of eight major processes which are collections of sub-
processes. We organize the pattern language by attaching the patterns to the main
processes of PRINCE2. In this way, PRINCE2 acts as a structuring device for the
pattern language: a project manager can easily identify the patterns applicable for a
particular main process in PRINCE2. In Table 3 the eight PRINCE2 major processes
are rows and the (numbers of the) GSD patterns are columns. An x-mark in the matrix
means that the column pattern is related to the row process.
