This video looks at the technique of the "Timebox"

This is a generic term for defining how long a team has to build a set of requirements. In a project the approach is to build a set of related products/features/requirements. In other words, a Timebox in a project has a specific objective to deliver something functional (not always an MVP - minimum viable product, often something more than that).

However, it should be more than just functional - this objective should be giving the business some idea as to whether this part of the solution will contribute to the Benefit, and also works the way they need it to work - hence more than an MVP

This objective has a set of requirements which it is depenedant on for it to work. This we can see if using the Product Based Planning approach and shown in the Product Breakdown Structure (esp the org chart view)

Remember this is about Projects in the main.

Of course Scrum calls a timebox a Sprint. DSDM's AgilePM calls it in full a "Solution Development Timebox". From a project perspective the next timeframe up, a Stage" (Prince2), "Increment" (AgilePM), is therfore also a Timebox and so up to project level, we have a Project Timebox.

More in the video