Hardware Reference
In-Depth Information
Table 1.
(
continued
)
08-Work
Allocation
Work needs to be
shared between sites
with some criteria.
Find out what the
GSD Strategy
is in your company and check
Competence
information of persons in each site with help of
site managers. Make
Architectural Work Allocation
and/or
make
Phase- Based Work Allocation
and/or make
Feature
Based Work Allocation
and/or other allocation according to
some other criteria. Make a decision about division of work
between sites according to a company's
GSD Strategy
and the
above analysis.
Work needs to be
shared between sites
with architectural
criteria.
Check architectural analysis of your product and plan which
site will be responsible for maintaining and increasing
knowledge in some architectural area. Architectural area can
also be a whole subsystem or part of a subsystem.
09-
Architect-
ural Work
Allocation
Work needs to be
shared between sites
with phased-based
criteria.
Check how phase- based work allocation will be made. Also
check which site is possibly responsible for maintaining and
increasing knowledge in some phase-based area e.g. testing or
requirements engineering in a certain product area.
10-Phase-
Based
Work
Allocation
11-Feature-
Based
Work
Allocation
Work needs to be
shared between sites
with feature- based
criteria.
Check the
GSD Strategy
how feature- based work allocation
strategy has been described. Form a group of members from
different sites to realize the features, if needed.
12-Use
Common
Processes
Different processes
and templates at
different sites make
communication
inefficient.
Choose common upper level processes and allow local
processes if they do not cause problems with upper level
processes.
13-
Iteration
Planning
Persons do not
know what kinds of
features are needed
for a GSD project
and what the current
goal is.
Project manager will present prioritized features and other
tasks. Project members will participate in a planning meeting
either personally or by
Communication Tools
. The project
members will estimate amount of work for features and tasks. If
needed, more detailed discussion can be arranged in sites with
participants' mother language. In the end of planning, meeting
the list of selected features and tasks is created and is visible by
Common Repositories and Tools.
14-Multi-
Level
Daily
Meetings
Problems to have a
daily common
meeting with all
members with
different time zones.
Lack of trust and
long feedback loops.
Organize many daily meetings and organize another daily or
weekly meeting between project managers from different sites
to exchange information about the results of daily meetings.
With foreigners, written logs can be one solution to ensure that
communication messages are understood correctly in every site.
Choose the same working time for meetings in different sites.
15-
Iteration
Review
It's difficult to know
what the status of a
project is and the
feedback loop is
long.
Check the project status by a demo and present results to all
relevant members and stakeholders from different sites. Gather
comments and exchange requests for further measures for both
product and process. Make frequent deliveries to improve
visibility of the status of the product.
16-
Organize
Knowledge
Transfer
It's difficult to
transfer a huge
amount of knowl-
edge to new or
experienced
developers of
different sites.
Make sure that there is a product knowledge repository available
for project members. Train the product and get members also to
use. Specification with use cases will be presented in the
Iteration Planning
meeting or separate meetings. Also earlier
customer documentation and demo will be presented in some
cases.
Key Roles in Sites
network will be utilized by trying to
find solutions for problems. Use frequent or longer visits to
enhance knowledge transfer and be sure that there are good
communication channels between project members.
