Hardware Reference
In-Depth Information
Table 1.
GSD Patterns for project management
ID-
Name
Problem(s)
Solution outline
01-GSD
Strategy
A lack of a company
level GSD strategy.
List the reasons and motivation to start GSD based development
in a company. Make a short and long term plan about GSD. Find
out the competence of different sites and make a SWOT and risk
analysis for GSD strategy. Also measure the real costs of GSD.
02-Fuzzy
Front End
Unclear how to
gather product needs
globally from
external and internal
customers and how
to form plans and
change requests
from these needs.
The needs of different customers will be gathered to a global
database. It is also important to have the possibility for global
access regardless of time and place as well as have the possibility
to use a discussion forum inside the tool. Product managers will
go through gathered needs and make decisions about them with
e.g. architects. A new feature or requirement will be made if it is
accepted in a decision meeting.
Product managers will make a
Road Map and a Business plan for a product including many
features. These features will be realized in development projects.
03-
Communi-
cate Early
What is the goal of a
GSD project and
who are the members
of a project?
Lack of trust.
Arrange kick-off meeting for all relevant members. Present
common goal and motivation of this project and present release
plan made by
Divide and Conquer with Iterations
. Also present
responsibilities made by
Work Allocation
. Present used
Common Processes
and
Common Repositories and Tools.
Organize leisure activities for teams to improve team spirit.
04-Divide and Conquer with
Iterations
See an example below (Table 2).
05-Key
Roles in
Sites
Difficult to know
who to contact in
different sites with
your questions.
A project manager will have negotiations with site managers or
other supervisors about team members before final decisions.
Also needed roles will be formed in every site (e.g. Site project
Manager, Architect, IT Support, Quality assurance etc.) The main
site person is in a leading position and the persons from other
sites will help to take care of the issues, tasks and responsibilities
in their sites. Publish the whole project organization with roles for
every site to improve communication. One person can have many
roles in a project.
06-
Communi-
cation
Tools
Lack of
communication,
communication
tools can also vary
between sites.
Have reliable and common communication methods and tools
in every site. Use different tools at the same time as net meeting
to show information and project data, conference phones to
have good sound and chat tool to discuss in written form if
there are problems to understand e.g. English language used in
other sites. Also train and motivate project members to use
these tools.
07-
Common
Repos-
itories and
Tools
Separate Excel files
are difficult to
manage and project
data is difficult to
find, manage and
synchronize
between many sites.
Provide a common Application Lifecycle Management (ALM)
tools for all project artefacts (documents, source code, bugs,
guidelines etc.). ALM provides almost real-time traceability,
reporting, visualization and access to needed information etc. for
all users in different sites. It can be implemented as a single tool
or it can be a group of different tools which has been integrated
with each other. ALM tools can include means to support
operation according to the organisation's processes and
development methods (state models, process templates,
workflows). Use different levels (team, project, and program)
reports to improve visibility of status of projects.
