Uploaded by anita.molnar

ActivityList

advertisement
Activity List Template
1. Introduction
This document describes a template for an activity list based on a project WBS, which is typical
on the development of new products for the electromechanical industry like industrial
automation equipment.
The Activities List is an output of the Define Activities process, described as “The process of
identifying and document the specific actions to be performed to produce the project
deliverables.” [A Guide to the Project Management Body of Knowledge (PMBOK Guide)—Fifth
Edition, Chapter 6]
The Activity List is then used as input for the following processes: Sequence Activities, Estimate
Activity Resource, Estimate Activities Duration and Develop Schedule.
The PMBOK Guide—Fifth Edition provides essential guidelines to produce an Activity List,
mainly on the following chapters:

Chapter 6.2.2.1: The activity list, WBS and WBS dictionary can be developed either
sequentially or concurrently, with the WBS and WBS dictionary as the basis for
development of the final activity list. Each work package within the WBS is decomposed
into the activities required to produce the work package deliverables.

Chapter 6.2.3.1: The Activity List is a comprehensive list that includes all schedule
activities required on the project. The Activity List also includes the activity identifier and
a scope of work description for each activity in sufficient detail to ensure that the project
team members understand what work is required to be completed. Each activity should
have a unique title that describes its place in the schedule, even if that activity title is
described outside the context of the project schedule.
2. Purpose
The purpose of this document is to offer an activity list based on the key disciplines that
distinguish a development of a new product for the electromechanical industry.
Project managers working on this type of projects can take it as a basis to identify the activities
of their projects, keeping the consistency with the project WBS, covering the generation of
specifications, design, manufacturing and validation at module and system levels.
The template also suggests several review activities, recommended to be planned in order to
improve the quality of the work packages deliverables.
3. Reference WBS
This template uses the following basic WBS as reference for the activity list:
Electromechanical
Product
Development
System
Requirements
Specification
System
Test
Specifications
Design
Specifications
Electromechanical
Development
Module
Test
Specifications
SW
Development
PCB
Development
System tests
Module tests
Other WBS elements (e.g. Project Management, Training, etc.) are also typical for similar
projects but are not on the focus of this template.
4. Activity list template
The activity list template is delivered as a series of tables organized by the WBS elements and
work packages. Each activity has its description, scope and deliverables when applicable.
4.1.
System requirements specification
4.1.1. System requirements specification generation
WBS discipline
System requirements
specification
Work package
System
requirements
specification
generation
Activity
Create system
requirements
specification
Review system
requirements
specification
Approve system
requirements
specification
Activity scope
Identify and register the system
requirements, e.g.
- Interfaces with other systems
- User interfaces
- Code and market requirements
- Functional and non-functional
requirements.
- System behavior for normal operation and
exception handling (e.g. input overvoltage or
undervoltage).
Review the document with the involved parts
(e.g. developers, marketing, production,
installation and maintenance teams)
preferably during its elaboration.
Collect the review findings and plan the
corrections.
Get formal approval from the main
stakeholders for the system requirements
specification.
Work package deliverables
Review report with findings.
Correction plan.
Approved system
requirements specification
4.2.
Design specifications
4.2.1. Electromechanical device specification generation
WBS discipline
Design specifications
Work package
Electromechanical
device specification
generation
Activity
Create
electromechanical
device specification
Activity scope
Identify and register the electromechanical
device requirements, e.g.
- Physical dimensions
- Electrical and mechanical interfaces
- Operating temperature range
- Maximum operating altitude
- Maximum weight
- EMC (Electromagnetic Compatibility)
requirements.
- Vibration and shock requirements
- Protection degrees (e.g. touch, water
resistance, etc.).
- Required certifications (e.g. CSA, UL, etc.)
- Operating voltage range
- Maximum power consumption
- Ecology and health related requirements
(e.g. prohibited substances, disposal
requirements, etc.)
- Labelling requirements (e.g. warning
labels, required languages, etc.)
- Production related requirements (e.g.
hanging points, test points, BOM - Bill Of
Material- concept, configuration levels, etc.)
- Logistic related requirements (e.g.
minimum and maximum volumes for
consolidation, preferred suppliers, etc.).
- Installation related requirements (e.g.
fixation points, wiring, power up sequence,
etc.).
- Maintenance (spare parts selection,
periodic maintenance concept, periodic
replacement of components, etc.).
Work package deliverables
WBS discipline
Design specifications
Work package
Electromechanical
device specification
generation
Activity
Review
electromechanical
device specification
Approve
electromechanical
device specification
Activity scope
Review the document with the involved parts
(e.g. electromechanical designers,
production, installation and maintenance
teams) preferably during its elaboration.
Record the review findings and plan the
respective corrections.
Get formal approval of electromechanical
device specification from involved parts.
Work package deliverables
Review report with findings.
Correction plan.
Approved electromechanical
device specification
4.2.2. PCB specification generation
WBS discipline
Design specifications
Work package
PCB specification
generation
Activity
Create PCB
specification
Activity scope
Identify and register the PCB requirements,
e.g.
- Physical dimensions
- Electrical and mechanical interfaces
- Operating temperature range
- Maximum operating altitude
- EMC (Electromagnetic Compatibility)
requirements.
- Vibration and shock requirements
- Protection degrees (e.g. touch, water
resistance, etc.).
- Required certifications (e.g. CSA, UL, etc).
- Operating voltage range
- Maximum power consumption
- PCB features (e.g. functions to be
performed by the PCB)
- Memory and I/O mapping
- Safety related requirements (e.g. minimum
distance between tracks, minimum pitch of
connectors, etc.).
- Reliability requirements (e.g. MTBF)
- Decisions from the Failure Mode and
Effects Analysis (FMEA)
- Ecology and health related requirements
(e.g. prohibited substances, disposal
requirements, etc.)
- Production related requirements (e.g.
maximum dimensions for assembly
machines, programming points, test points,
etc.)
- Logistic related requirements (e.g.
minimum and maximum volumes, preferred
suppliers, etc.).
- Maintenance (e.g. repair concept).
Work package deliverables
WBS discipline
Design specifications
Work package
PCB specification
generation
Activity
Review PCB
specification
Approve PCB
specification
Activity scope
Review the document with the involved parts
(e.g. PCB developers, production,
installation and maintenance teams)
preferably during its elaboration.
Record the findings and plan the respective
corrections.
Get formal approval of PCB specification
from involved parts.
Work package deliverables
Review report with findings.
Correction plan.
Approved PCB specification
4.2.3. SW specification generation
WBS discipline
Design specifications
Work package
SW specification
generation
Activity
Create SW
specification
Review SW
specification
Approve SW
specification
Activity scope
Describe the SW functional and nonfunctional requirements, e.g.
- Interfaces with other systems (e.g.
communication protocols)
- User interfaces
- System behavior for normal operation and
exception handling (e.g. input overvoltage or
undervoltage).
- Backwards compatibility.
- HW limitations (e.g. maximum code and
data sizes).
- Required monitoring functions from the
Failure Mode and Effects Analysis (FMEA)
- Manufacturing requirements (e.g. SW
download during production, dummy
configurations for production tests, etc).
- Installation requirements (e.g. minimum
system requirements, SW distribution media,
etc).
- Maintenance requirements (e.g. SW
update).
Review document with the involved parts
(requirements engineers, SW developers,
testers, production, installation and
maintenance team, etc.) preferably during its
elaboration.
Record the review findings and plan the
respective corrections.
Get formal approval of SW specification from
involved parts.
Work package deliverables
Review report with findings.
Correction plan.
Approved SW specification.
4.3.
System test specifications
4.3.1. System test specification generation
WBS discipline
System test
specifications
Work package
System test
specification
generation
Activity
Create system test
specification
Review system test
specification
Approve system test
specification
Activity scope
Based on the system requirements
specification, define the tests to be
performed at system level, e.g.
- Functional tests
- Performance tests
- Configuration tests
- Installation tests
- Customer acceptance tests
Define the configurations to be tested.
Review the document with the involved parts
(e.g. developers, testers, etc.) preferably
during its elaboration.
Collect the review findings and plan the
corrections.
Get the formal approval of the involved parts
for the document
Work package deliverables
Review report with findings.
Correction plan.
Approved system test
specification
4.3.2. Piloting test specification generation
WBS discipline
System test
specifications
Work package
Piloting test
specification
generation
Activity
Create piloting test
specification
Review piloting test
specification
Approve piloting test
specification
Activity scope
Define the number and characteristics of
pilot units where tests at system level shall
be repeated.
Based on the system requirements
specification, select the meaningful tests to
be repeated at pilot units, e.g.
- Functional tests
- Performance tests
- Configuration tests
- Installation tests
- Customer acceptance tests
Review the document with the involved parts
(e.g. developers, testers, etc.) preferably
during its elaboration.
Collect the review findings and plan the
corrections.
Get the formal approval of the involved parts
for the document
Work package deliverables
Review report with findings.
Correction plan.
Approved piloting test
specification
4.4.
Module test specifications
4.4.1. Electromechanical device test specification generation
WBS discipline
Module test
specifications
Work package
Electromechanical
device test
specification
generation
Activity
Create
electromechanical
device test
specification
Activity scope
Based on the electromechanical device
specification, define the tests to be
performed at module level, e.g.
- Electrical interface tests
- Temperature tests
- EMC (Electromagnetic Compatibility) tests.
- Vibration and shock tests.
- Protection degree tests (e.g. IPX3)
- Certification tests (e.g. CSA, UL).
- Overvoltage and undervoltage tests.
- Configuration tests
- Installation tests
Work package deliverables
Review
electromechanical
device test
specification
Review the document with the involved parts
(e.g. electromechanical developers, testers,
etc.) preferably during its elaboration.
Collect the review findings and plan the
corrections.
Review report with findings.
Correction plan.
Approve
electromechanical
device test
specification
Get the formal approval of the involved parts
for the document.
Approved electromechanical
device test specification
4.4.2. PCB test specification generation
WBS discipline
Module test
specifications
Work package
PCB test
specification
generation
Activity
Create PCB test
specification
Review PCB test
specification
Approve PCB test
specification
Activity scope
Based on the PCB specification, define the
tests to be performed at module level, e.g.
- Electrical interface tests
- Temperature tests
- EMC (Electromagnetic Compatibility) tests.
- Vibration and shock tests
- Protection degree tests (e.g. IPX3).
- Certification tests (e.g. CSA, UL).
- Overvoltage and undervoltage tests
- Short circuit protection tests
- PCB functional tests
Review the document with the involved parts
(e.g. PCB developers, testers, etc.)
preferably during its elaboration.
Collect the review findings and plan the
corrections.
Get the formal approval of the involved parts
for the document.
Work package deliverables
Review report with findings.
Correction plan.
Approved PCB test
specification
4.4.3. SW test specification generation
WBS discipline
Module test
specifications
Work package
SW test specification
generation
Activity
Create SW test
specification
Review SW test
specification
Approve SW
specification
Activity scope
Based on the SW specification, define the
tests to be performed at module level, e.g.
- Unit tests
- Interface tests (e.g. communication tests)
- User interface tests
- Functional tests (normal and exceptional
scenarios)
- Backwards compatibility tests
- Monitoring function tests
- SW configuration tests
- SW installation and update tests
Review the document with the involved parts
(e.g. SW developers, testers, etc.) preferably
during its elaboration.
Collect the review findings and plan the
corrections.
Get the formal approval of the involved parts
for the document.
Work package deliverables
Review report with findings.
Correction plan.
Approved SW test
specification
4.5.
Electromechanical development
WBS discipline
Electromechanical
development
Work package
Electromechanical
device development
Activity
Design
electromechanical
device
Review
electromechanical
device prototype
documentation
Manufacture
electromechanical
device prototype
Review
electromechanical
device prototype with
production.
Module tests
Electromechanical
device tests
execution
Perform module tests
with the
electromechanical
device prototype.
System tests
System tests
execution
Perform system tests
with the
electromechanical
device prototype.
Activity scope
Based on the electromechanical device
specification, design the electromechanical
device.
Prepare the prototype documentation for
production.
Prepare documentation for installation and
maintenance.
Review prototype documentation with the
production team.
Collect the review findings and plan the
corrections.
Based on the approved documentation for
production, manufacture the
electromechanical device prototype.
Review the electromechanical device
prototype against the approved
documentation for production.
Collect the review findings and plan the
corrections.
Perform tests with the electromechanical
device prototype according to the
electromechanical device test specification.
Collect the test findings and plan the
corrections.
Integrate the electromechanical device into
the system and perform the tests at system
level (e.g. interface, functional, EMC,
temperature, shock and vibration tests)
according to the system test specification.
Perform the required certifications tests.
Collect the test findings and plan the
corrections.
Work package deliverables
Review report with findings.
Correction plan.
Approved prototype
documentation for
production.
Review report with findings.
Correction plan.
Prototype ready for module
tests.
Test report with findings.
Correction plan.
Prototype ready for system
tests.
System test report with
findings.
Correction plan.
WBS discipline
Electromechanical
development
Work package
Electromechanical
device development
Activity
Implement correction
from tests at module
and system levels.
Electromechanical
development
Electromechanical
device development
Review
electromechanical
device
documentation for
piloting
Release
electromechanical
device
documentation for
piloting
Manufacture
electromechanical
device for piloting.
Review
electromechanical
device produced for
piloting.
System tests
Piloting tests
execution
Perform piloting tests
Electromechanical
development
Electromechanical
device development
Implement correction
from piloting tests
Review
electromechanical
device
documentation for
full production.
Activity scope
Based on module and system test reports,
implement the mandatory corrections on the
electromechanical device documentation
before releasing it for piloting.
Review manufacturing documentation with
the production team.
Review installation and maintenance
documentation with the respective teams.
Collect the review findings and plan the
corrections.
Get formal approval from production,
installation and maintenance teams to
release the electromechanical device
documentation for piloting.
Based on the approved documentation for
production, manufacture the
electromechanical device for piloting.
Review the electromechanical device
produced for piloting against the released
documentation for production.
Collect the review findings and plan the
corrections.
Install the electromechanical device on a
real environment.
Perform functional, installation and
maintenance tests based on the piloting test
specification.
Collect the findings and plan the corrections.
Implement the corrections based on the
piloting test reports.
Update the electromechanical device
production, installation and maintenance
documentation.
Review the electromechanical device
production, installation and maintenance
documentation with the respective teams.
Collect the findings and plan the corrections.
Work package deliverables
Review report with findings.
Correction plan.
Electromechanical device
documentation released for
piloting.
Review report with findings.
Correction plan.
Electromechanical device
ready for piloting tests.
Piloting test reports with
findings.
Correction plan.
Review report with findings.
Correction plan.
WBS discipline
Work package
Activity
Release
electromechanical
documentation for
full production.
Activity scope
Get formal approval from production,
installation and maintenance teams to
release the electromechanical device
documentation for full production.
Work package deliverables
Electromechanical device
documentation released for
full production.
Activity
Design PCB
Activity scope
Based on the PCB specification, design the
PCB.
Prepare the PCB prototype documentation
for production.
Review the PCB prototype documentation
with the production team.
Collect the review findings and plan the
corrections.
Work package deliverables
4.6. PCB development
WBS discipline
PCB development
Work package
PCB development
Review PCB
prototype
documentation
Manufacture PCB
prototype
Review PCB
prototype with
production.
Module tests
PCB tests execution
Perform module tests
with the PCB
prototype.
System tests
System tests
execution
Perform system tests
with the PCB
prototype.
PCB development
PCB development
Implement correction
from tests at module
and system levels.
Based on the approved documentation for
production, manufacture the PCB prototype.
Review the PCB prototype against the
approved documentation for production.
Collect the review findings and plan the
corrections.
Perform tests with the PCB prototype
against the PCB test specification.
Collect the review findings and plan the
corrections.
Integrate the PCB into the system and
perform the tests at system level (e.g.
interface, functional, EMC, temperature,
shock and vibration tests) according to the
system test specification.
Perform the required certifications tests.
Collect the test findings and plan the
corrections.
Based on module and system test reports,
implement the mandatory corrections on the
PCB documentation before releasing it for
piloting.
Review report with findings.
Correction plan.
Approved prototype
documentation for
production.
Review report with findings.
Correction plan.
Prototype ready for module
tests.
Test report with findings.
Correction plan.
Prototype ready for system
tests.
System test report with
findings.
Correction plan.
WBS discipline
Work package
Activity
Review PCB
documentation for
piloting
PCB development
PCB development
Release PCB
documentation for
piloting
Manufacture PCB for
piloting.
Review PCB
produced for piloting.
System tests
Piloting tests
execution
Perform piloting tests
PCB development
PCB development
Implement correction
from piloting tests
Review PCB
documentation for
full production.
Release PCB
documentation for
full production.
Activity scope
Review prototype documentation with the
production team.
Review installation and maintenance
documentation with the respective teams.
Collect the review findings and plan the
corrections.
Get formal approval from production,
installation and maintenance teams to
release the PCB documentation for piloting.
Based on the approved documentation for
production, manufacture the PCB for
piloting.
Review the PCB produced for piloting
against the released documentation for
production.
Collect the review findings and plan the
corrections.
Install the PCB on a real environment.
Perform functional, installation and
maintenance tests according to the piloting
test specification.
Collect the findings and plan the corrections.
Implement the corrections based on the
piloting test reports.
Update the PCB production, installation and
maintenance documentation.
Review the PCB production, installation and
maintenance documentation with the
respective teams.
Collect the findings and plan the corrections.
Get formal approval from production,
installation and maintenance teams to
release the PCB documentation for full
production.
Work package deliverables
Review report with findings.
Correction plan.
PCB documentation released
for piloting.
Review report with findings.
Correction plan.
PCB ready for piloting tests.
Piloting test reports with
findings.
Correction plan.
Review report with findings.
Correction plan.
PCB documentation released
for full production.
4.7.
SW development
WBS discipline
SW development
Work package
SW development
Activity
Implement SW beta
Review SW beta
Module tests
SW test execution
Perform module tests
with the SW beta.
System tests
System tests
execution
Perform system tests
with the SW beta.
Activity scope
Based on the SW specification, implement
meaningful pieces of SW to be integrated on
a SW beta and delivered for review and
tests.
Create SW prototypes to review the
implementation of interfaces with other
systems and users.
The delivery of SW betas shall follow a SW
delivery plan coordinated with the availability
of HW modules required for tests (e.g.
PCBs, electromechanical devices, other
systems, etc.).
This activity shall be repeated until the
complete SW agreed scope is delivered.
Review the SW implementation with the
requirements and test teams as soon as
meaningful pieces of SW are available for
test.
This activity shalll be repeated until the
complete SW agreed scope is delivered.
Perform tests according to the SW test
specification for the agreed scope of the SW
beta.
Collect the review findings and plan the
corrections.
This activity shall be repeated until the
complete SW agreed scope is tested
according the SW test specification
Provide a SW beta, selected according to
the SW delivery plan, to be used during the
tests at system level.
Collect the test findings and plan the
corrections.
This activity may be repeated until the
complete SW agreed scope is tested.
Work package deliverables
Review report with findings.
Correction plan.
Test report with findings.
Correction plan.
System test report with
findings.
Correction plan.
WBS discipline
SW development
Work package
SW development
Activity
Prepare SW for
piloting
Review SW for
piloting
Release SW for
piloting
System tests
Piloting tests
Perform piloting tests
SW development
SW development
Generate SW for full
production
Review SW for full
production.
Release SW for full
production.
Activity scope
Implement the mandatory corrections and
provide a SW beta or official release for
piloting.
Prepare the corresponding SW
documentation for piloting (e.g. download
and update instructions, user instructions,
etc.)
Review SW test reports and SW
documentation with the production,
installation and maintenance teams.
Collect the review findings and plan the
corrections.
Get formal approval from production,
installation and maintenance teams to
release the SW for piloting.
Install the SW on a real environment.
Perform installation, functional and update
tests according to the piloting test
specification.
Collect the findings and plan the corrections.
Implement the SW corrections based on the
piloting test reports.
Update the SW production, installation and
maintenance documentation.
Review the SW changes since piloting and
the SW documentation for production,
installation and maintenance with the
respective teams.
Collect the findings and plan the corrections.
Get formal approval from production,
installation and maintenance teams to
release the SW and the respective
documentation for full production.
Work package deliverables
Review report with findings.
Correction plan.
SW released for piloting
tests.
SW beta and documentation
released for piloting.
Piloting test reports with
findings.
Correction plan.
Review report with findings.
Correction plan.
SW documentation released
for full production.
4.8.
System tests
4.8.1. System tests execution
WBS discipline
System tests
Work package
System tests
execution
Activity
Perform system tests
Activity scope
Integrate the system modules according the
configurations prescribed by the system
tests specification.
Perform system tests according to the
system test specification.
Work package deliverables
System test report
Activity
Perform piloting tests
Activity scope
On the selected pilot units, perform the tests
at system level according to the piloting test
specification.
Work package deliverables
Piloting test reports
4.8.2. Piloting tests execution
WBS discipline
System tests
Work package
Piloting tests
execution
Download