IPD Study Notes: How to Refine Project Plans in R&D

IPD (Integrated Product Development) stems from the PACE theory created by the U.S. PRTM company; after IBM’s adoption, it evolved into a comprehensive system of ideas, models, and tools for enterprise product development.

The IPD workflow is explicitly divided into six stages—concept, planning, development, verification, release, and lifecycle—and incorporates clearly defined decision‑review points. These reviews prioritize business considerations such as market positioning and profitability rather than purely technical criteria.

Each decision‑review point follows a consistent measurement standard, and only work that satisfies the required criteria may advance to the next review stage.

A project plan must address three core elements: tasks, schedule, and resources. The required level of detail correlates with project tightness; a more detailed plan reduces uncertainty and facilitates smoother execution, embodying the principle that “sharpening the axe does not delay the work.”

Three plan granularity levels are recommended:

Big plan : defines the tasks of the medium‑level plan, orders their execution, estimates duration, and outlines organizational involvement.

Medium plan : specifies sub‑tasks within a phase (e.g., a coding module), includes start and end dates, and assigns a task owner.

Small plan : details individual daily progress (day‑by‑day schedule).