Rules of The Road 1999 A Guide For Leading Successful Integrated Product Teams Oct 99
Rules of The Road 1999 A Guide For Leading Successful Integrated Product Teams Oct 99
Rules of The Road 1999 A Guide For Leading Successful Integrated Product Teams Oct 99
Revision 1
October 1999
In May 1995 the Secretary of Defense directed the Department to apply the Integrated
Product and Process Development (IPPD) concept of using Integrated Product Teams (IPTs)
throughout the acquisition process. In July 1999 the Under Secretary of Defense for Acquisition
and Technology reaffirmed the Department’s commitment to the IPPD and IPT concepts by
requesting an update to the Rules of the Road: A Guide for Leading Successful Integrated
Product Teams. This update incorporates four years of experience the Department has gained in
the IPT process and provides guidelines for more effective IPT operations.
This Rules of the Road guide is a “living” document, and the guidelines herein are
designed to assist the Program Manager by engaging both OSD and Service staffs in the IPT
process. By engaging all levels of the acquisition community early and continuously throughout
the process, issues will be identified and resolved as early as possible.
These guidelines complement DoD 5000.2-R, and the extracts therefrom are mandatory.
Other guidelines herein are discretionary, but represent best business practices and will be
included in an upcoming update to the discretionary section of the Defense Acquisition
Deskbook. The guide describes the IPT process for ACAT ID and ACAT IAM acquisition
programs, but the concepts are applicable for all programs.
_________________________ _________________________
_________________________ _________________________
iii
TABLE OF CONTENTS
FOREWORD...................................................................................................................................ii
List of Figures.................................................................................................................................iv
List of Tables..................................................................................................................................iv
I. INTRODUCTION....................................................................................................................1
OVERVIEW..............................................................................................................................1
II. POLICY....................................................................................................................................2
POLICY GUIDANCE...............................................................................................................3
OVERARCHING IPT PROCEDURES AND ASSESSMENTS..............................................4
WORKING-LEVEL IPT PROCEDURES, ROLES, AND RESPONSIBILITIES...................5
REFERENCES..........................................................................................................................8
III. PRINCIPLES..........................................................................................................................10
CHARTERING, LAUNCH, INITIATION.............................................................................10
GOAL ALIGNMENT.............................................................................................................11
OPEN DISCUSSIONS WITH NO SECRETS........................................................................12
EMPOWERED, QUALIFIED TEAM MEMBERS................................................................12
DEDICATED/COMMITTED PROACTIVE PARTICIPATION..........................................13
ISSUES RAISED AND RESOLVED EARLY.......................................................................13
IV. PRACTICE.............................................................................................................................15
V. TOOLKITS.............................................................................................................................17
GUIDELINES FOR MEETING MANAGEMENT................................................................18
BEST PRACTICES CHECKLIST..........................................................................................19
MEETING MANAGEMENT CHECKLIST..........................................................................23
EFFECTIVE CHARACTERISTICS OF IPT PARTICIPANTS............................................25
DOD IPT SKILL AND KNOWLEDGE REQUIREMENTS.................................................26
VI. GLOSSARY............................................................................................................................27
iv
List of Figures
List of Tables
v
I. INTRODUCTION
OVERVIEW
This guide is designed to assist the Program Manager (PM) and supporting acquisition
community in developing and executing high-performance integrated product teams (IPTs).
The guide is divided into five chapters. Chapter II addresses the mandatory policy and
guidance for IPT structures supporting ACAT (Acquisition Category) ID and ACAT IAM
programs. Chapter III defines fundamental Operating Principles for Effective IPTs at any level
within the DoD, and Chapter IV defines the process of putting IPTs into practice. Chapter V
provides an operational toolkit to assess and improve the effectiveness of any IPT.
1
II. POLICY
In 1995, the Secretary of Defense directed that the Department adopt IPTs as the preferred
approach for development, review, and oversight of the acquisition process. The IPT process as
described herein facilitates decision-making by making decisions and recommendations based on
timely input for the entire team and replaces the lengthy longstanding sequential review and
approval process. Figure 1 depicts the overall IPT approach and mandatory guidance (see DoD
5000.2-R Part 4.2 and Part 5.4) supporting ACAT ID and IAM acquisition program managers.
The IPT concept for oversight and review was developed to streamline an antiquated,
inefficient process. Before the IPT process was implemented, program offices frequently
produced a product that, when reviewed at higher levels, was modified substantially or even
rejected. The purpose of IPTs is to facilitate decision-making by making recommendations based
on timely input from the entire team. The IPT approach simultaneously takes advantage of all
members’ expertise and produces an acceptable product the first time.
As programs proceed through the acquisition process toward major Milestone Decisions
or reviews, each program will establish and execute an Overarching IPT (OIPT), Integrating IPT
(IIPT), Working-level IPTs (WIPT) and Program-level IPTs (PIPT), as appropriate. Table 1
sum-marizes the focus and participant responsibilities for each of these IPTs. A more detailed
policy description of the operation of OIPTs and WIPTs as extracted from DoD 5000.2-R
follows.
2
Figure 1. DoD IPT Operational Structure
3
Table 1. DoD IPT Types, Focus and Responsibilities
Organization Teams Focus Participant
Responsibilities
OSD and OIPT* Strategic Guidance Program Success
Components Tailoring Functional Area Leadership
Program Assessment Independent Assessment
Resolve Issues Elevated by WIPTs Issue Resolution
POLICY GUIDANCE
IPTs are an integral part of the defense acquisition oversight and review process. The
Secretary of Defense has directed that the Department perform as many acquisition functions as
possible, including oversight and review, using IPTs.
For ACAT ID and IAM programs, mandatory guidance for OIPTs and WIPTs is provided
in Part 5.4 of DoD 5000.2-R as extracted below. (Mandatory guidance for PIPTs is provided in
Part 4.2 of DoD 5000.2-R.)
This guide is oriented toward those IPTs whose membership is made up of OSD and
Component staffs and is designed to facilitate oversight and review of ACAT ID and ACAT
IAM programs. Nonetheless, the principles and practices apply to PIPTs whose membership is
made up of program office and contractor personnel in the execution environment. Additional
PIPT guidance may be found in the DoD Guide to Integrated Product and Process Development
and the DoD Integrated Product and Process Development Handbook.
1
Extracted from DoD 5000.2-R, Part 5.4.1.
4
In support of all ACAT ID and IAM programs, an OIPT shall be formed for each
program to provide assistance, oversight, and review as the program proceeds through its
acquisition life cycle. The OIPT for ACAT ID programs shall be led by the appropriate Office
of the Secretary of Defense (OSD) official (typically the Director of Strategic and Tactical
Systems or the Director, Program Analysis & Integration, depending on the program in
question). The OIPT for ACAT IAM programs is called the Information Technology
Overarching Integrated Product Team (IT OIPT) and shall be led by the Director, Performance
Assessment2, in the Office of the Deputy CIO. OIPTs shall be composed of the PM, PEO,
Component Staff, Joint Staff, USD(A&T) staff, and the OSD staff principals or their
representatives, involved in oversight and review of a particular ACAT ID or IAM program.
The OIPT shall first form upon learning that a program is intended to be initiated, to
consider the recommendations proposed by the IIPT; the extent of WIPT support needed for the
potential program; who shall participate on the WIPTs; the appropriate milestone for program
initiation; and the minimum information needed for the program initiation review. OIPTs shall
meet as necessary over the life of a program. The OIPT Leader shall take action to resolve
issues when requested by any member of the OIPT, or when directed by the Milestone Decision
Authority (MDA). The goal is to resolve as many issues and concerns at the lowest level
possible, and to expeditiously escalate issues that need resolution at a higher level, bringing only
the highest level issues to the MDA for decision.
In support of a planned milestone review by the Defense Acquisition Board (DAB), the
OIPT shall normally convene two weeks in advance of the anticipated review to assess
information and recommendations being provided to the MDA. Additionally, at that meeting,
the PM shall propose the WIPT structure, documentation, and strategy for the next acquisition
phase, for approval by the MDA. The OIPT Leader, in coordination with appropriate CAE, shall
recommend to the MDA whether the anticipated review should go forward as planned.
The OIPT leader for ACAT ID programs shall provide an integrated assessment to the
DAB chair, principals, and advisors at major program reviews and milestone decision reviews
using information gathered through the IPT process. The leader’s assessment shall focus on core
acquisition management issues and shall take account of independent assessments that are
normally prepared by OIPT members. These assessments are typically accomplished in the
context of the OIPT review and shall be reflected in the OIPT Leader’s report. There should be
no surprises at this point, because all team members are already working the issues in real time,
and they should be knowledgeable of their OIPT leader’s assessment. Typical OIPT
membership is shown in Table 2.
2
After the issuance of DoD 5000.2-R, the title of the Director, Performance Assessment,
was changed to Director, Information Technology Acquisition and Investments.
5
OIPT LEADERS
Vice Chairman, Joint Chiefs of Staff Assistant Secretary of Defense (Reserve Affairs)
Under Secretary of Defense (Comptroller) Assistant Secretary of Defense (Health Affairs)
Assistant Secretary of Defense (Command, Control, Communica- Under Secretary of Defense (Personnel & Readiness)
tions & Intelligence)/DoD Chief Information Officer Under Secretary of Defense (Policy)
Director, Defense Procurement Assistant to the Secretary of Defense (Nuclear, Chemical &
Director, Operational Test and Evaluation Biological)
Director, Program Analysis and Evaluation Deputy Under Secretary of Defense (Acquisition Reform)
Director, Systems Acquisition Deputy Under Secretary of Defense
Deputy Director, Developmental Test & Evaluation (Advanced Systems Concepts)
Chairman, OSD Cost Analysis Improvement Group Deputy Under Secretary of Defense (Environmental Security)
(ACAT ID Only) Deputy Under Secretary of Defense (Logistics)
Director, Interoperability Deputy Under Secretary of Defense (Science & Technology)
Cognizant Service Acquisition Executive Deputy General Counsel (Acquisition & Logistics)
Cognizant Program Executive Officer Director, Defense Research & Engineering
Cognizant Program Manager Director, Ballistic Missile Defense Organization
Director, Defense Intelligence Agency
Director, Defense Information Systems Agency*
Director, National Reconnaissance Office
Director, Acquisition Resources & Analysis
Director, Special Programs
The PM, or designee, shall form and lead an Integrating IPT (IIPT) to support the
development of strategies for acquisition and contracts, cost estimates, evaluation of alternatives,
logistics management, cost-performance trade-offs, etc. The IIPT shall assist the PM in the
development of a WIPT structure to propose to the OIPT. The IIPT shall also coordinate the
activities of the remaining WIPTs and ensure that issues not formally addressed by other WIPTs
are reviewed. WIPTs shall meet as required to help the PM plan program structure and
documentation and resolve issues. While there is no one-size-fits-all WIPT approach, there are
three basic tenets to which any approach shall adhere:
2
Extracted from DoD 5000.2-R, Part 5.4.2.
6
3. Direct communication between the program office and all levels in the acquisition
oversight and review process is expected as a means of exchanging information and
building trust.
The Leader of each IPT is usually the PM or the PM’s representative. The OSD action
officer may co-chair the IPT meetings, at the invitation of the PM. The following roles and
responsibilities apply to all WIPTs:
Examples of WIPTs
The purpose of the IPT is to assist in outlining the Test and Evaluation Master Plan
(TEMP) for a major program. The objective of such an IPT is to reach agreement on the strategy
and plan by identifying and resolving issues early, understanding the issues and the rationale for
the approach, and, finally, documenting a quality TEMP that is acceptable to all organizational
levels the first time.
3
Extracted from SECDEF memo, May 10, 1995.
7
Cost/Performance IPT4
The best time to reduce life-cycle costs is early in the acquisition process. Cost
reductions shall be accomplished through cost/performance tradeoff analyses, which shall be
conducted before an acquisition approach is finalized. To facilitate that process, the Overarching
IPT (OIPT) for each ACAT I and ACAT IA (as required) program shall establish a
Cost/Performance IPT (CPIPT). The user community shall have representation on the CPIPT.
Industry representation, consistent with statute and at the appropriate time, shall also be
considered. Normally, the PM or the PM’s representative leads the CPIPT. Prior to each
milestone decision, the PM shall report the CPIPT findings to the OIPT leader.
Upon approval of a MNS (see 2.3), a CAIV strategy shall be formulated as part of the
acquisition strategy to set cost objectives. By program initiation (usually Milestone I), each
ACAT I and ACAT IA PM shall have established life-cycle cost objectives for the program
through consideration of projected out-year resources, recent unit costs, parametric estimates,
mission effectiveness analyses and trades, accident attrition trade studies, technology trends and
other relevant considerations such as commercial versus DoD specifications (see 3.3.5.2) and the
open systems strategy and design (see 3.3.1 and 4.3.4). A complete set of life-cycle cost
objectives shall include RDT&E, production, MILCON, operating and support, and disposal
costs. At each subsequent milestone review, cost objectives and progress towards achieving
them shall be reassessed.
4
Extracted from DoD 5000.2-R, Part 3.3.4.1.
8
REFERENCES
The following references establish, direct, and provide guidance on the use of IPTs
within the Department.
(a) “Reengineering the Acquisition Oversight and Review Process,” USD(A&T), April 28,
1995.
(b) “Use of Integrated Product and Process Development and Integrated Product Teams in
DoD Acquisition,” Secretary of Defense, May 10, 1995.
(c) DoD Guide to: Integrated Product and Process Development (Version 1.0); February 5,
1996.
(d) DoD Directive 5000.1, Defense Acquisition (Change 1), May 21, 1999.
(e) DoD Integrated Product and Process Development Handbook, August 1998.
(f) DoD Regulation 5000.2-R, Mandatory Procedures for MDAPs and MAIS Acquisition
Programs (Change 4), May 11, 1999.
The following website addresses provide access to guidance on the use of IPTs within the
Department.
(a) http://www.acq.osd.mil/sa/asm/product.html
DoD Directive 5000.1 Defense Acquisition (Change 1), May 21, 1999.
DoD Regulation 5000.2-R, Mandatory Procedures for MDAPs and MAIS Acquisition
Programs (Change 4), May 11, 1999.
Rules of the Road: A Guide for Leading Successful Integrated Product Teams.
(b) http://www.acq.osd.mil/sa/se/ippd_pubs.html
DoD Guide to Integrated Product and Process Development (Version 1.0), February 5,
1996.
9
Integrated Product and Process Development Handbook, August 1998.
(c) http://www.deskbook.osd.mil
(d) http://www.dsmc.dsm.mil/pubs/gdbks/risk_managementhtm.htm
10
III. PRINCIPLES
IPTs shall function in a spirit of teamwork with participants empowered and authorized,
to the maximum extent possible, to make commitments for the organization or the functional
area they represent. IPTs are composed of representatives from all appropriate functional
disciplines working together to build successful programs and enabling decision-makers to make
the right decisions at the right time. Adherence to the following six guiding principles will
improve the productivity of any IPT.
Getting teams off to a good start is critical. Key activities include charter preparation,
conducting IPT training, and preparing a POA&M. When combined, these activities contribute
to early and sustained success.
The IPT charter documents the mission and product of the IPT, and it establishes the
timeframe in which the effort is to be completed. It should be drafted by the team leader, ratified
by the membership at the outset of the IPT, and approved by the responsible executive leader. A
charter embodies the three basic tenets and roles and responsibilities of IPTs (see Working-level
IPT Procedures, Roles, and Responsibilities, pp. 5-6). It also embodies the six operating
principles for success oriented IPTs enumerated in this chapter. Table 3 provides some
considerations for a charter.
The POA&M provides a detailed understanding of key IPT activities, target dates, and
deliverables. It is a simple management tool that complements the IPT charter and clearly and
graphically communicates critical IPT objectives and the processes that will be used to achieve
them.
Together, chartering an IPT, training participants, and preparing a POA&M provide the
solid foundation from which IPTs are successfully launched.
11
Table 3. Considerations for a Charter
A charter should:
1. contain a clear mission statement, to include the specific purpose and objectives of the IPT;
2. provide recognition of the purpose of the IPT in a larger context;
3. identify the output product, process, or service to be provided;
4. identify the customer or recipient of the output product, process, or service;
5. identify the timeframe by which the product is to be produced, the process completed, or the
service provided;
6. identify IPT membership, to include all the cross-functional disciplines necessary to achieve
the objectives of the IPT and to produce the product, complete the process, or provide the
service;
7. consider any need for training of the IPT membership, particularly those new to the IPT
process;
8. address membership performance objectives that characterize high-performance IPTs;
9. address product ownership and membership accountability;
10. address the use of metrics as a means of creating and maintaining team focus;
11. provide for membership coordination and buy-in;
12. embody:
(a). the three basic tenets of IPTs;
(b). the roles and responsibilities applicable to all WIPTs; and
(c). the six operating principles for implementing success-oriented IPTs;
13. be approved by appropriate authority;
14. provide for its own periodic review for adequacy, currency, or rescission.
A charter may:
GOAL ALIGNMENT
The team leader should ensure the goals and objectives of team members are consistent
with project goals and objectives. An effective mechanism to provide performance feedback to
team members and their functional organization should be established. Where feasible, feedback
on performance should be provided to the individual’s supervisor, as well as team members.
Individual recognition contributes to the development and success of high-performance IPTs.
12
OPEN DISCUSSIONS WITH NO SECRETS
Each member brings to the team unique expertise that needs to be recognized by all.
Because of that expertise, each person’s views are important in developing a successful program,
and these views need to be heard. Teams must have full and open discussions with no secrets.
Full and open discussion does not mean that the team must act on each view, but all facts must
be on the table for each team member to understand and assess. Cooperation is essential.
A sense of ownership on the part of the IPT members is key to the success of the IPT
process. Ownership is a collective concept. All IPT members must feel that their contributions
are important to the process and are well considered. Decisions and documents should be a
product of the Team.
IPT members must make other team members aware of any limits to their ability to speak
for their principals. IPT agreements cannot be binding if they exceed the limits of a member’s
empowerment. Staff representatives must seek direction from their superiors on the limits of
5
Extracted from SECDEF May 10, 1995 memo.
13
their authority and make recommendations only within those limits. Staff superiors will enhance
staff effectiveness by granting the greatest possible authority.
WIPT members are expected to ensure that their leadership is in agreement with the
IPT’s goals. When issues arise that exceed the limits of empowerment, the PM or IPT leader
must allow members adequate time to coordinate issues and positions with their principals. This
continuous “up-the-line” communication should ensure no surprises later when the principals are
asked to coordinate or review a final draft document or decision.
It is important for the IPT leader to stress at the outset that agreements reached in the IPT
must be binding. An exception to this general rule would be the rare case where new
information comes to light after agreements have been reached, and where new information is
significant enough to warrant a review of prior agreements.
Consistent team participation by people with institutional knowledge of the functional areas is
necessary for success. Therefore, IPTs should be organized to allow all stakeholders to
participate and rightsized to the issue. Membership should be limited to the minimum essential
to enhance communication and trust. Participation should be by the principal member. The
practice of accompanying support staff is specifically discouraged and is undesirable. Other
organizations may be added as required based on the needs of the program. WIPTs will include
action officers from the program office (or agency staff if the program is pre-Milestone I) and
from the staff organizations represented on the OIPT. Contractor participation shall be in
accordance with guidance in DoD 5000.2-R, Part 1.6/4.2.
Team members should openly raise and discuss issues at the earliest possible opportunity.
The IPT should try to resolve issues within the team, seeking additional functional expertise
when necessary. In the spirit of teaming and cooperation, issues should not be worked “off-line”
beyond the purview of the IPT. In instances where outside discussion facilitates the education of
a member, such activity is encouraged. However, all issues should be raised, worked and
disposed of, within the team context. When an issue cannot be resolved within the WIPT, the
PM should raise the issue as quickly as possible to a decision-making level where resolution can
be achieved.
Figure 2 illustrates the issue resolution process from the PM up to the USD(AT&L) or
the ASD(C3I), as the Milestone Decision Authority for ACAT ID or ACAT IAM programs. The
objective is to achieve agreement and resolve issues rapidly at the lowest possible level, without
hindering program progress.
14
Figure 2. Issue Resolution Process
15
IV. PRACTICE
Establishing and executing high performing IPTs require skilled leaders and an
organizational culture that exhibits openness and trust among its employees. A typical IPT
process model is illustrated in Figure 3 and defined by a four step process:
Delivery: As issues are resolved and the POA&M executed, the IPT completes and
delivers its chartered outcome requirements.
Reevaluation: Upon delivery and review with senior leadership, the IPT provides
necessary feedback to IPT membership and evaluates the need for continuation of the
IPT. If requirements are fulfilled the IPT is disbanded.
16
Figure 3. IPT Process Map
IPTs are not intended to solve every problem and should be distinguished from meetings.
IPTs are focused on building successful acquisition programs, but not all issues for resolution or
assigned actions require convening an IPT. For example, IPTs may be used to: develop
affordable and executable strategies and plans; identify and resolve issues early; and provide
continuous early insights to the MDA. There is a need to make sure that the IPT philosophy
does not become a fad, in order to productively use personnel resources, especially in today’s
downsizing environment. IPTs should be considered when there are requirements:
Once an IPT is launched and senior leadership is engaged, the IPT begins the operation.
For success, it is essential that adequate time be established to develop and implement the toolkit
material found in Chapter V.
As products are delivered, it is imperative that the IPT reevaluate its charter for
continuing need and currency.
V. TOOLKITS
This chapter provides the following aids to assist leaders in operating effective IPTs:
17
GUIDELINES FOR MEETING MANAGEMENT
Focus. The IPT Leader must clearly articulate the IPT's focus at the outset of the
process. Examples of a specific focus may be to prepare for a decision milestone, to develop and
reach agreement on a proposed acquisition strategy, or to resolve a specific issue or set of issues.
Orienting the Team Members. To ensure that all IPT members have a common
understanding of the program, the IPT Leader should provide a program or issue overview
briefing at the first meeting. Before the first IPT meeting, the IPT Leader will develop a
proposed IPT strategy, documentation requirements and IPT structure. These proposals will be
refined by the IPT and proposed to the sponsor. The IPT Leader will proceed based on the
sponsor’s agreement. Any disagreements will follow the issue resolution process in Figure 2.
The IPT members will discuss and agree to a meeting management approach, to include the
items listed below.
Agendas. To ensure productive meetings, detailed agendas with timelines for topics and
supporting material must be distributed at least three business days before the IPT meeting
NOT during the meeting. Every effort should be made to use electronic media for
distribution. It may prove useful for the leader and members to jointly prepare the agenda to
ensure all concerns are addressed.
Meeting Summaries. Good meeting summaries will be brief and will preclude revisiting
previous agreements and wasting the time and resources of the team members. Meeting
summaries should:
Record attendance
Draft meeting summaries should be provided to IPT members within one working day of
a meeting. The final summary should be provided to all members within two working days after
the deadline for the receipt of comments.
18
BEST PRACTICES CHECKLIST
Do: Don’t:
Engage all members in the IPT process Personalize organizational position
by soliciting inputs and applying active
listening skills Isolate people. IPTs are only effective
when all team members are participating
Know your team members’ preferred
methods of communication, and Leave issues unaddressed. Unaddressed
thoroughly understand their issues tend to resurface at higher levels
organizational roles and operating and often drive major rework
environments
Forget to document actions/decisions.
Trust and accept each person’s expertise Documentation provides all team
and advice members an opportunity clarify issues
and a historical record of decisions
State the extent of your authority/
empowerment and immediately identify
issues which are beyond established
limits
19
BEST PRACTICES CHECKLIST
Do: Don’t:
Principals must: Conduct a briefing cycle separate from
the overall IPT process
Ensure the IPT member is well-versed in
the mission and organization of the Principals should not overturn decisions
functional areas they are representing made by empowered team members
when those team members acted within
Provide guidance, direction and extent of
their delegated authority
authority to the members
20
BEST PRACTICES CHECKLIST
Do: Don’t:
Commit yourself to the objectives of the Bring a personal agenda/negative
IPT attitude to the IPT
Represent your functional area without Bring additional support staff
bias
Skip meetings
Actively seek and receive input of others
Come prepared
Do: Don’t:
Ensure structure is in place to identify Raise issues outside the IPT process
issues (e.g., dedicate a portion of each (i.e., no end runs)
meeting to raising / discussing issues)
21
BEST PRACTICES CHECKLIST
Do: Don’t:
Charter: Charter
Obtain Senior Management agreement Proceed without a written charter and
on charter objectives resources established
Ensure adequate resources are available Make the charter too complicated
(money, time and people)
Launch: Launch:
Launch IPT as soon as possible Allow the launch to be cumbersome and
following charter sign-off unfocused
Ensure IPT agreement and Discourage open member participation
understanding of charter
Goal Alignment
Do: Don’t:
Develop approach(s) to provide Ignore subpar performance
feedback to team members and their
home organizations
22
MEETING MANAGEMENT CHECKLIST
23
Evaluating the Meeting
To what extent do Team members:
Fully and freely participate in IPTs
Engage in open frank, and forthright discussions
Come prepared
Leave the pit ready to discuss/address the results with their organizations
Ask to what extent:
Is there consistent IPT participation by primary functional area members
Are member positions on issues known
Are positions revised by your functional area superior at the next level of review
Ask to what extent are:
Team and team member performance assessed
Potential Metric: Trend analysis of functional area issue resolution and team
member performance through action item records/meeting minutes
Consistent representation from functional areas available
Potential Metric: Record attendance
To what extent do:
Surprises arise at higher IPTs (IIPT, OIPT, DAB)
Issues get resolved at IPT level
Issues get elevated beyond IPT
Unresolved issues affect the POA&M
24
EFFECTIVE CHARACTERISTICS OF IPT PARTICIPANTS
25
DOD IPT SKILL AND KNOWLEDGE REQUIREMENTS
26
27
VI. GLOSSARY
28