ISO/IEC 21827

ISO/IEC 21827:2002(E)
B.7.6.1
Description
Project and systems engineering activities may be selected from applicable standards, known best practice within the
industry segment, reference models such as the SSE-CMM®, or the organization's historical experience.
B.7.6.2
Example Work Products
• identified technical activities.
B.7.6.3
Notes
Use historical records from similar projects, where possible, to develop the list of activities and to gain confidence that
the list is complete. Use the "rolling wave" paradigm for planning. The "rolling wave" paradigm is used to define
near-term activities more precisely than activities that start later in the project.
For example, the systems engineering activities would be decomposed into activities planned for the next three months
until each activity is approximately two weeks in duration. Activities 3 to 12 months away should be planned at
approximately a month in duration. Activities starting more than a year away can be described at a very high level,
approximately two months in duration. For the non systems engineering technical activities, use this same method while
working with other disciplines according to the Integrate Disciplines process area (PA04).
B.7.7
BP.16.06 - Define Project Interface
Define specific processes to support effective interaction with customer(s) and supplier(s).
B.7.7.1
Description
Project interfaces include all those with organizations and individuals who are necessary to successful project
execution, whether they are inside or outside the project group. Types of interaction include information exchange,
tasking, and deliveries. Methods and processes (including controls) for interaction are established as appropriate for the
parties that are interacting.
B.7.7.2
Example Work Products
• defined processes for project interfaces.
B.7.7.3
Notes
For the project, identify the groups internal and external to your organization that the project needs to interact with in
order to be successful. For each group, perform the base practices of the Integrate Disciplines process area (PA04) to
define and implement each interface in terms of interaction mechanisms, interaction frequency, and problem resolution
mechanisms.
B.7.8
BP.16.07 - Develop Project Schedules
Develop technical schedules for the entire project life cycle.
B.7.8.1
Description
Project schedules include system and component development, obtaining procured items, training, and preparing the
engineering support environment. Schedules are based on verifiable effort models or data for identified tasks, and they
must allow for task interdependencies and the availability of procured items. Schedules should also include slack time
appropriate for identified risks. All affected parties must review and commit to the schedule.
B.7.8.2
Example Work Products
• project schedules.
© ISO/IEC 2002 – All rights reserved 91