Product
The application, platform or project you manage. Products can be linked one way, like a car that depends on its wheels.
Features
Same shape, same thing: every building block looks the same in the map, the matrix, the timeline and the 3D cube.
The application, platform or project you manage. Products can be linked one way, like a car that depends on its wheels.
What the product does for its users. Groups requirements. Flat: no features inside features.
What must be true for a feature to be complete. Part of exactly one feature, built in one or more modules, with its own status.
How the product is built. A feature linked to a module directly, or through its requirements, shows both.
A goal with a desired date. Delivers features, requirements and modules, one requirement at a time if you like, and can depend on other releases.
The product version a release ships as, plus the version of every module. Unchanged modules keep their version.
Not a building block but a linked document: the detailed spec behind a feature or a requirement, kept where your team writes it, in Confluence, Notion, Google Docs or Figma. VPM keeps the link and, if you want, the release it applies to.
Views
No tasks, tickets or sprints. Those stay in the tools your teams already use.
Every screen starts as a picture you can filter, focus and edit in place.
Warnings about dates and dependencies, stated as facts. Your plan stays yours.
Deleting is reversible. The history of what was planned, cancelled or delivered stays.