There are currently 19 terms in this directory beginning with the letter I.
The channels used to provide stakeholders with timely information and updates regarding a project.
Initiation phase – The formal start of a new project. It involves receiving proper authorization and creating a clear definition for the project.
The process of reviewing and examining the final product to assess compliance to initial requirements and expectations.
The process of coordinating assurance activities across a number of assurance providers.
Integrated change control
The coordination of changes throughout all aspects of a project, including scope, budget, and schedule.
Integrated master plan (IMP)
A project management tool used to break down project work in large, complex projects. It lists project tasks and events in a hierarchical structure and shows relationships between them.
Integrated master schedule (IMS)
An integrated master schedule is produced from an integrated master plan. It is a list of all project tasks represented as a networked schedule.
Integration management plan
A document that explains integration planning and details how changes to project aspects will be managed.
The process of deciding how project elements will be integrated and coordinated and how changes will be addressed throughout the project management process.
Management processes that coordinate a number of project aspects including cost, schedule, and resources (among others).
Invitation for bid
An invitation for expressions of interest that a procuring organization extends. (See also request for proposal)
Ishikawa diagrams are used in project management to identify the possible causes of an effect. (See also fishbone diagram)
A set of quality-management guidelines for projects. It is a standard created by the International Organization for Standardization.
Anything that can cause problems for a project. The term typically refers to major problems that cannot be tackled by the project team on their own.
Project issues and the persons responsible for resolving them. It may also include issue status, plans for resolution, and resolution deadlines.
A concept from iterative software development that specifies a fixed time cycle for development work, typically a few weeks long. The development life cycle consists of a number of iterations, sometimes with a functional version of the software produced at the end of each one. Iterative development prioritizes time over scope, so there are rarely concrete requirements to be achieved in an iteration.
Iterative and incremental development
Iterative and incremental development is any combination of the iterative and incremental development approaches. It is an alternative to the waterfall development method: instead of focusing on sequential development with a single end product, it passes through a number of development cycles, with an improved version of the product, called an increment, produced at the end of each iteration.