Download normal - VTT Virtual project pages

MobileD/Release Project Process/0 Iteration/
ProjectSet-Up/
Author: Outi Salo
Modified: Juha Koskela
Version_02_20050110
Name
Project Set-Up
Type
Pattern type:
Phase pattern
Stage pattern
Task pattern
Practice pattern
Pattern classification:
Essential
Recommended
Supporting
Optional
Motivation
Goal
The purpose of this stage is to 1) set-up the physical and technical resources for the
project as well as the environment for project monitoring, 2) train the project team as
necessary, and 3) establish the project specific ways to communicate with the
customer group. All the tasks of Project Set-Up include the participation of project
team.
The goals of the Project Set-Up are to:
1.
2.
3.
4.
Entry
&
Inputs
Set-Up the physical resources for the project team,
Set-Up the technical resources for the project,
Familiarize the project team to the new tools and processes, and
Attain an agreement with the customer group of how the project team and
customer group will communicate throughout the project.
Entry criteria:
1.
2.
3.
4.
5.
6.
The metrics for both research and production purposes have been
defined,
The personnel has been allocated for the project,
The resources have been defined and allocated for the project,
The customer group has been identified for the project,
The training needs of the project team have been acquired, and
The base process has been defined for the project.
Inputs:
1.
2.
3.
4.
Project plan,
Training plan,
Base process description and
Measurement plan.
MobileD/Release Project Process/0 Iteration/
ProjectSet-Up/
Author: Outi Salo
Modified: Juha Koskela
Version_02_20050110
Exit
&
Outputs
Exit criteria:
1.
2.
3.
4.
The physical environment has been set-up for the project,
The technical environment has been set-up for the project, and
Adequate training has been arranged for the project team regarding
both the technical as well as the software development process issues.
Customer communication has been established.
Outputs:
1.
Process
Project plan
The following figure illustrates the sequence of the tasks needed to conduct the Project
Set-Up:
1. Environment
Set-Up
2. Training
3. Customer
Communication
Establishment
The individual tasks of Project Set-Up are:
Tasks
1.
Environment Set-Up is a task where the technical and physical
environment should be set for the project. This task may also involve
the software developers, especially concerning the technical
environment which may be part of the training task. Also, even though
the software developers do not implement any requirements for the
product they may, for example, experiment the implementation of
client-server communication.
2.
Training is a task where the software development team is trained
according to their specific needs. This may include training on software
development process issues, data collection for project monitoring as
well as technical issues related to the software development itself such
as new tools and methods.
3.
Customer Communication Establishment is an important task in
Mobile-D. The project management should establish and agree the
ways to communicate with the customer group throughout the project.
Different projects and environments require different approach for
communication that in Agile software development context will require
firm and constant communication with the customer. Customer will be
needed in certain tasks throughout Mobile-D, such as acceptance
testing, not depending if the customer is on-site of off-site. However,
whereas other project may have an on-site customer available all the
time another project may need other ways to communicate daily with
MobileD/Release Project Process/0 Iteration/
ProjectSet-Up/
Author: Outi Salo
Modified: Juha Koskela
Version_02_20050110
customer. Especially if the customer is off-site the specific needs of the
project team and the customer for communication should be defined
and the procedures for the communication should be established and
agreed. The main issue is to accept the level and means for the
communication to enable efficient software development, valid end
product and satisfied customer.
Roles
FAQ
The following roles can be identified in executing the Project Set-Up:
1.
Project team
2.
Project team/project manager
3.
Support group
4.
Support group/Training personnel
5.
Customer group
The answers to the frequently asked questions will provide the Project Set-Up with
additional in-depth information gained when applying it in practice.
Q What kind of training is found useful when adopting Mobile-D
process?
A First of all, the training needs that are relevant considering the base
process that has been tailored for the incipient project should be the
basis for the training. Thus, different Agile techniques that may be
novel to the project team should be included in the training in as
practical level as possible. These may include pair-programming
practices and planning day activities. Also, project monitoring and
quality assurance practices (e.g. Agile project management and
requirements management practices) and metrics collection
mechanisms should be well familiarized to the project team in
beforehand. Naturally, the more technical aspects are of vital
importance in the implementation of the project, such as version
management, software architecture issues and testing procedures (e.g.
test-driven development, pre-release testing and acceptance testing).
Related
patterns
Other patterns which are part of, composed of or associated closely to Project Set-Up
are identified here:


Project Establishment: The Project Establishment stage pattern and
its task patterns is closely associated to project set-up where the
personnel is allocated, the environment selected and training needs
defined. Thus, Project Establishment stage provides important input
for Project Set-Up stage.
0 iteration: Project Set-Up stage pattern is part of 0 iteration phase.
MobileD/Release Project Process/0 Iteration/
ProjectSet-Up/
Author: Outi Salo
Modified: Juha Koskela
Version_02_20050110
Variations
N/A
Risks
Possible risks which can result from Project Set-Up as well as the solutions including
pre-emptive actions for avoiding the risks and actions to take to minimise the risks’
effects are discussed here:

References
&
Further
Reading
N/A
Not establishing and agreeing ways of communication with the
customer group may result as delays in the software development or
defective implementation of requirements of the software product.