Trillium Capability Areas, Roadmaps and Practices
Capability Area 4: Management

This Capability Area covers the 5 management-oriented Roadmaps:
They address items that interface with customers and suppliers of the organization\qs products, as well as the most significant areas of sizing, scheduling, tracking and managing projects.

Roadmap 4.1: Project Management

This Roadmap covers practices that address project management issues.

Level 2

Statement of work

4.1.2.1
A documented and approved statement of work exists for the project [SEI SPP Ability 1] [Trillium].

4.1.2.2
The engineering group participates on the project proposal team [SEI SPP Activity 1] [Trillium].

4.1.2.3
Project commitments and changes to commitments made to individuals and groups external to the organization are reviewed with senior management prior to making contractual commitment according to a documented procedure [SEI SPP Activity 4] [SEI SPT&O Activity 3] [ISO 9001 4.4.9] [Trillium].

Accountability & Authority

4.1.2.4
A project manager is designated to be responsible for the project's activities and results [SEI SPT&O Commitment 1] [Bellcore TR-NWT-000179 3.4.4.1].

4.1.2.5
For any given project activity or task, there is a single owner having responsibility and authority over the completion of that activity and the quality of its output(s) [Roadmap Trillium 4.1.2.3].

Planning

4.1.2.6
Adequate resources and funding are provided for planning the project [SEI SPP Ability 3] [ISO 9001 4.1.2.2] [Trillium].

4.1.2.7
Project planning includes all project related planning activities (e.g., quality planning, verification and validation planning) [ISO 9000-3 5.4.1] [Bellcore TR-NWT-000179 3.4.1] [Trillium].

4.1.2.8
Project planning activities identify and document methods for ensuring that all activities are carried out correctly [ISO 9001 4.4.2] [ISO 9000-3 6.2.2] [Trillium].

4.1.2.9
Project development and management planning documentation includes purpose, scope, goals, objectives, deliverables and primeships for the project [ISO 9000-3 6.2.2] [Bellcore TR-NWT-000179 3.4-1].

4.1.2.10
Software project planning activities are initiated in the early stages of, and conducted in parallel with, the overall project planning activities [SEI SPP Activity 2].

4.1.2.11
Responsibilities for developing the product development plan are assigned [SEI SPP Ability 2] [Trillium].

4.1.2.12
The project development plan is developed, documented and approved according to a documented procedure [SEI SPP Activity 6 & 7 and SPT&O Ability 1] [ISO 9000-3 5.4.1] [Bellcore TR-NWT-000179 3.4.1-1] (Ref. IEEE Std. 1058.1).

4.1.2.13
The development group participates with other affected groups in the overall project planning throughout the life of the project [SEI SPP Activity 3].

4.1.2.14
Work products that are needed to establish and maintain control of the project are identified [SEI SPP Activity 8].

4.1.2.15
Required inputs and outputs to each project phase are defined and documented [ISO 9001 4.4.3] [ISO 9000-3 5.4.4 & 5.4.5] [Bellcore TR-NWT-000179 3.4-1].

4.1.2.16
Input and output criteria for each project phase are defined and documented [ISO 9000-3 5.5.2] [Trillium].

4.1.2.17
The project manager explicitly assigns responsibilities for work products and activities [SEI SPT&O Ability 2] [ISO 9001 4.4.2] [Trillium].

4.1.2.18
Plans for the project's engineering facilities, environments, and support tools are prepared [SEI SPP Activity 14].

4.1.2.19
Project quality planning specifies and documents measurable product quality objectives [ISO 9000-3 5.5.2] [Trillium].

4.1.2.20
Project planning specifies and documents schedules, resources and approval authorities for verification and validation activities [ISO 9001 4.4.2, 4.4.7, 4.4.8] [ISO 9000-3 5.5.2] [Trillium].

4.1.2.21
Project planning identifies and documents procedures to be used to assure timely compliance with all development performance and review standards to be used throughout the life-cycle [ISO 9001 4.4.2, 4.4.6] [Trillium].

Risk Management

4.1.2.22
The technical, cost, resource and schedule risks are identified, assessed and documented [SEI SPP Activity 13] [ISO 9000-3 5.4.2.2].

4.1.2.23
The technical, cost, resource, and schedule risks are tracked throughout the life of the project [SEI SPT&O Activity 10] [ISO 9000-3 5.4.2.2].

Scheduling

4.1.2.24
The project's schedule is derived according to a documented procedure [SEI SPP Activity 12] [Bellcore TR-NWT-000179 3.4.3-1, 2].

Data collection

4.1.2.25
Planning data are recorded for use by the project [SEI SPP Activity 15].

4.1.2.26
Actual measurement and replanning data for the project are recorded for use by the current project and future projects [SEI SPT&O Activity 11].

Tracking

4.1.2.27
Adequate resources and funding are provided for tracking the project [SEI SPT&O Ability 3] [Trillium].

4.1.2.28
The project development plan is used to track activities and communicate project status [SEI SPT&O Activity 1] [ISO 9000-3 5.4.1] [Bellcore TR-NWT-000179 3.4.1-1] (Ref. IEEE Std. 1058.1).

4.1.2.29
The project's product development plan is revised according to a documented procedure [SEI SPT&O Activity 2].

4.1.2.30
Approved changes to commitments that affect the project are communicated to the members of the development group and other related groups [SEI SPT&O Activity 4] [ISO 9001 4.4.9].

4.1.2.31
The size of the work products is tracked and corrective actions are taken as appropriate [SEI SPT&O Activity 5].

4.1.2.32
The project's costs are tracked and corrective actions taken as appropriate [SEI SPT&O Activity 6].

4.1.2.33
The project's critical target computer resources are tracked and corrective actions are taken as appropriate [SEI SPT&O Activity 7].

4.1.2.34
The project's schedule is tracked and corrective actions taken as appropriate [SEI SPT&O Activity 8] [ISO 9000-3 5.4.3] [Bellcore TR-NWT-000179 3.4-1].

4.1.2.35
Engineering technical activities are tracked and corrective actions taken as appropriate [SEI SPT&O Activity 9].

4.1.2.36
The critical dependencies and critical paths of the project's schedule are managed according to a documented procedure [SEI ISM Activity 9].

4.1.2.37
Representatives of the software development function work with representatives of the other engineering functions to monitor and coordinate activities and resolve project-level technical issues [SEI IC Activity 2].

Reviews

4.1.2.38
The developers and their managers conduct regular reviews to track technical progress, plans, performance, and issues against the software development plan [SEI SPT&O Activity 12] [ISO 9000-3 5.6.4].

4.1.2.39
Formal reviews, to address the accomplishments and results of the project, are conducted at selected project milestones and at the beginning and completion of selected stages according to a documented procedure [SEI SPT&O Activity 13] [ISO 9000-3 5.6.4] [ISO 9001 4.4.6] [Bellcore TR-NWT-000179 3.4-1 & 3.4.4-2].

4.1.2.40
Products produced as input to other project groups are reviewed by representatives of the receiving groups to ensure that the products meet their needs [SEI IC Activity 5].

4.1.2.41
All intergroup issues are documented, negotiated, and, if unresolved, reported to the appropriate managers [SEI IC Activity 6].

4.1.2.42
Periodic technical reviews and interchanges are held with the task leaders of the project groups [SEI IC Activity 7] [Bellcore TR-NWT-000179 3.4.4-2 & 3.4.4-3].

Level 3

Funding

4.1.3.1
Adequate resources and funding are provided for managing the project using the project defined process [SEI ISM Ability 1] [ISO 9001 4.1.2.2].

4.1.3.2
Adequate resources and funding are provided for the internal coordination of all product and service engineering activities [SEI IC Ability 1] [ISO 9001 4.1.2.2] [Trillium].

Policy

4.1.3.3
The organization follows a written policy requiring that projects be managed according to a documented procedure [SEI ISM Commitment 1].

4.1.3.4
The project is managed in accordance with the project's defined product development process [SEI ISM Activity 4] [Trillium].

Process Tailoring

4.1.3.5
The project's defined product development process is developed by tailoring the organization's standard product development process according to documented procedure [SEI ISM Activity 1] [Trillium].

Project Planning

4.1.3.6
The project's development plan, which describes the use of the project's defined process, is developed and changed according to a documented procedure [SEI ISM Activity 2, 3] [Trillium].

4.1.3.7
A documented plan is used to communicate intergroup commitments and coordinate and track the work performed [SEI IC Activity 3] [ISO 9001 4.4.3].

4.1.3.8
Critical dependencies are identified and negotiated according to a documented procedure [SEI IC Activity 4].

Resource Management

4.1.3.9
The size of the work products is managed according to a documented procedure [SEI ISM Activity 6].

4.1.3.10
The project's costs are managed according to a documented procedure [SEI ISM Activity 7].

4.1.3.11
The project's critical target computer resources are managed according to a documented procedure [SEI ISM Activity 8].

Risk Management

4.1.3.12
The project's development risks are identified, assessed, documented, and managed according to a documented procedure [SEI ISM Activity 10].

4.1.3.13
A team exists to coordinate defect prevention activities for the project [SEI DP Ability 2] [Trillium].

4.1.3.14
There is a formal mechanism for independently identifying project's process and product issues and escalating these to the project manager [ISO 9001 4.9] [Trillium].

Management Reviews

4.1.3.15
Formal reviews of the development project are conducted periodically to determine the actions needed to bring the project's performance and results in line with the current and projected business, customer, and end-user needs according to a documented procedure [SEI ISM Activity 11] [ISO 9001 4.4.5, 4.4.6] [Bellcore TR-NWT-000179 3.4.4-3 & 3.4.4-4].

Level 4

Defect Prevention

4.1.4.1
The project develops and maintains a plan for defect prevention activities [SEI DP Activity 1] [Trillium].

4.1.4.2
Revisions to the project's defined process resulting from defect prevention actions are incorporated according to a documented procedure [SEI DP Activity 7] [Trillium].

New Technology Introduction

4.1.4.3
Appropriate new technologies are incorporated into the project defined processes according to a documented procedure [SEI TCM Activity 8] [Trillium].

Roadmap 4.2: Subcontractor Management

This Roadmap covers practices that address the management of suppliers and subcontractors. "Subcontractors" is the term used in the SEI CMM and is thus more focused toward a product development context. "Supplier" is the term used by ISO 9001 and the Malcom Baldridge National Quality Award Criteria and is thus more generic, encompassing "subcontractors". Both terms are used in the set of practices for traceability purposes. These terms do NOT apply to individuals brought in to work as part of the development team on a contract basis.

Level 2

Resources

4.2.2.1
Adequate resources and funding are provided for selecting the subcontractor or supplier and managing the contractual agreement [SEI SSM Ability 1] [ISO 9001 4.1.2.2] [Trillium].

Selection Process

4.2.2.2
Subcontractors and suppliers are selected according to a documented procedure, based on a thorough evaluation of the subcontractor's or supplier's ability to perform the work and/or supplying the product or service. [SEI SSM Activity 2] [ISO 9001 4.6.1, 4.6.2] [ISO 9000-3 6.7.2] [Bellcore TR-NWT-000179 4.7-1] [Trillium].

Contractual Agreement

4.2.2.3
The contractual agreement with the subcontractor (or supplier) establishes the basis for managing the subcontractor (or the supplier) [SEI SSM Activity 3] [ISO 9001 4.6.3] [ISO 9000-3 6.7.1] [Bellcore TR-NWT-000179 4.7-1] [Trillium].

4.2.2.4
The work to be subcontracted is defined and planned according to a documented procedure [SEI SSM Activity 1] [ISO 9001 4.6.3].

Contract Management

4.2.2.5
A documented subcontractor's development plan, which covers (directly or by reference) the appropriate items from the prime contractor's development plan, is reviewed and approved by the prime contractor [SEI SSM Activity 4] [ISO 9001 4.3] [Bellcore TR-NWT-000179 4.7-3].

4.2.2.6
A documented and approved subcontractor's product development plan is used for tracking the development activities and communicating status [SEI SSM Activity 5] [Bellcore TR-NWT-000179 4.7-2].

4.2.2.7
The prime contractor's management conducts regular status and coordination reviews with the subcontractor's management [SEI SSM Activity 7] [ISO 9001 4.3] [Bellcore TR-NWT-000179 4.7-3].

4.2.2.8
Periodic technical reviews and interchanges are held with the subcontractor [SEI SSM Activity 8] [ISO 9001 4.7] [Bellcore TR-NWT-000179 4.7-3].

4.2.2.9
Formal reviews are conducted at selected milestones and the completion of selected stages to address the subcontractor's engineering accomplishments and results according to a documented procedure [SEI SSM Activity 9] [ISO 9001 4.3, 4.4.6, 4.6.4].

4.2.2.10
Changes in the subcontracted scope of work, subcontract terms and conditions, and other commitments are resolved according to a documented commitment review procedure involving affected groups of both the prime contractor and the subcontractor [SEI SSM Activity 6] [ISO 9001 4.3].

4.2.2.11
The prime contractor's quality assurance function monitors the subcontractor's quality assurance activities according to a documented procedure [SEI SSM Activity 10] [Bellcore TR-NWT-000179 4.7-4] [ISO 9001 4.10.2] [Trillium].

4.2.2.12
The prime contractor's configuration management function monitors the subcontractor's configuration management activities according to a documented procedure [SEI SSM Activity 11] [ISO 9001 4.10.2] [Bellcore TR-NWT-000179 4.12-3].

Acceptance

4.2.2.13
The prime contractor conducts acceptance testing as part of the delivery of the subcontractor's product according to a documented procedure [SEI SSM Activity 12] [ISO 9001 4.6.4, 4.7] [ISO 9000-3 6.7.3] [Bellcore TR-NWT-000179 4.7-1].

Subcontractor Performance Evaluation

4.2.2.14
The subcontractor's performance is evaluated on a periodic basis and the evaluation is reviewed with the subcontractor [SEI SSM Activity 13] [ISO 9001 4.6.2].

Level 3

Quality Requirements

4.2.3.1
The organization defines and communicates its quantitative product and process quality requirements to subcontractors [SEI SQM Activity 5] [MB 5.4a] [Trillium].

Quality Performance

4.2.3.2
The organization has in place a formal program to assess trends and current levels for critical indicators of supplier (subcontractor) quality [MB 6.4a] [Trillium].

4.2.3.3
The organization has in place a formal program to compare its supplier (subcontractor) quality levels with those of appropriately selected benchmarks [MB 6.4b] [Trillium].

Quality Improvement Program

4.2.3.4
The organization has in place a formal program to help its suppliers improve their ability to meet key quality and response time requirements [MB 5.4b] [Trillium].

Roadmap 4.3: Customer-Supplier Relationship

This Roadmap covers practices that address the relationship between customers and suppliers in a contract environment and, in a more mature environment, a partnering mode.

Level 2

Liaison

4.3.2.1
The organization has a representative with responsibility for dealing with the other party of a given contractual arrangement on contractual matters [ISO 9001 4.7] [ISO 9000-3 4.1.2] [Trillium].

Contractual Information

4.3.2.2
The contractual information (e.g., contract, requirements, warranties, return procedures, purchase orders) is reviewed, agreed to and coordinated formally [ISO 9000-3 5.2.1 & 5.2.2] [Bellcore TR-NWT-000179 3.2-1].

Customer Project Reviews

4.3.2.3
Formal reviews of the project are conducted with the customer at selected project milestones and at the beginning and completion of selected stages to address the accomplishments and results of the project according to a documented procedure [ISO 9000-3 4.1.3] [Bellcore TR-NWT-000179 3.4.2-3 & 3.4.4-3] [Trillium].

Customer Interaction

4.3.2.4
The development function actively participate(s) with the customers and end users to establish their needs [SEI IC Activity 1] [Bellcore TR-NWT-000179 3.4.2-3].

Level 3

Joint Requirements Development

4.3.3.1
Product requirements are developed jointly by representatives from Customer's and Supplier's cross-functional areas (e.g., marketing, design, support, and operations) [Roadmap Trillium 4.3.2.4].

Joint Application Design

4.3.3.2
Product design is developed in consultation with representatives from Customer's and Supplier's cross-functional areas (e.g., marketing, design, support, and operations) [Roadmap Trillium 4.3.2.4].

Quality Assurance Functions Liaison

4.3.3.3
The QA function representative conducts regular reviews of its activities and findings with the customer's QA function representative [SEI SQA Activity 8] [Trillium].

Interface Performance

4.3.3.4
Feedback on human machine interface and product and service interfaces is gathered formally (e.g., from customer and/or user groups) [MB 7.2f] [Trillium].

Roadmap 4.4: Requirements Management

This Roadmap covers practices that are related to the development and the management of requirements.

Level 2

Funding

4.4.2.1
Adequate resources and funding are provided for managing the allocated customer and systems requirements [SEI RM Ability 3] [ISO 9001 4.1.2.2] [Trillium].

Procedure

4.4.2.2
User/customer requirements are developed and documented according to a documented procedure [SEI RM Ability 2] [Bellcore TR-NWT-000179 4.6-3] (Ref. IEEE Std. 830) [Trillium].

User Requirements

4.4.2.3
There is an organizational policy for the management of user/customer requirements. This policy covers purpose, scope, modification, and ownership [ISO 9000-3 5.3] [Bellcore TR-NWT-000179 3.3-1,2,3,4] [Trillium].

4.4.2.4
The requirements include all aspects necessary to satisfy the customer's need and are stated precisely enough to allow validation during product acceptance. These requirements may include, but are not limited to, the following: functionality, performance, safety, reliability, security and privacy [ISO 9001 4.4.4, 4.4.5] [ISO 9000-3 5.3] [Bellcore TR-NWT-000179 3.3-1,2,3,4 & 4.6-3].

System Requirements

4.4.2.5
System requirements are documented in a consistent format and are clearly stated, verifiable and testable (Ref. IEEE Std. 830) [Trillium].

4.4.2.6
System requirements are traceable to user/customer requirements [ISO 9001 4.4.4] [Trillium].

4.4.2.7
System requirements are reviewed by all affected groups [SEI RM Activity 1].

4.4.2.8
System requirements form the basis for the product development plans, requirement specifications and activities [SEI RM Activity 2].

System Requirements Allocation

4.4.2.9
There is a function responsible for analyzing and allocating system requirements to hardware, software and other system components [SEI RM Ability 1].

System Requirements Changes

4.4.2.10
Changes to the system requirements are reviewed and incorporated into all appropriate development plans & activities [SEI RM Activity 3] [ISO 9001 4.4.4] [Bellcore TR-NWT-000179 3.4.1-2].

4.4.2.11
Changes to system requirements are analyzed to identify project impact [Bellcore TR-NWT-000179 3.4.1-2] [Trillium].

Level 3

Market Analysis

4.4.3.1
Market analyses to determine the customer needs and formulate appropriate product requirements are formal and performed according to a documented procedure [MB 7.1].

Quality Goals

4.4.3.2
Quantitative quality goals for requirements are established, and achievement against these goals is measured and tracked [ISO 9001 4.4.5] [Trillium].

Level 4

Customer Requirements

4.4.4.1
A process/method (e.g., Quality Function Deployment) is used to systematically capture all customer requirements and translate them into clear design statements [Roadmap Trillium 4.4.2.4].

Roadmap 4.5: Estimation

This Roadmap covers practices that are related to the estimation process.

Level 2

Work Product Size

4.5.2.1
Estimates for the size of all work products (or changes to the size of the work products) are derived according to a documented procedure [SEI SPP Activity 9] [Bellcore TR-NWT-000179 3.4.3-1,2].

Development Effort

4.5.2.2
Estimates for product development effort, costs and resources are derived according to a documented procedure [SEI SPP Activity 10] [Bellcore TR-NWT-000179 3.4.3-1].

Target Computer Resources

4.5.2.3
Estimates for critical target computing resources are derived according to a documented procedure [SEI SPP Activity 11] [Bellcore TR-NWT-000179 3.4.3-3].

Level 3

Process Repository

4.5.3.1
The organizational process repository is used for planning and estimating according to a documented procedure [SEI ISM Activity 5].

Project Size Management

4.5.3.2
The project's size is quantitatively managed according to a documented procedure [Trillium].

Estimation Model

4.5.3.3
Past project data is used to update a formal estimation model according to a documented procedure [Trillium].

4.5.3.4
The estimation model is maintained according to a documented procedure [Roadmap Trillium 4.5.3.3].


[*] Back to the Trillium home page.
[TOC] To the detailed Trillium table of contents.
[TOC] Back to capability area 3.
[TOC] Forward to capability area 5.

[UHCL]