A Planner is a coordination concept that structures how teams define goals, prioritize work and allocate resources across product delivery. It provides mechanisms for short- and long-term planning, aligning stakeholders and making trade-offs explicit. Useful for roadmaps, sprint planning and capacity management in product organizations.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
A planner is a planning artifact or tool that organizes tasks, dates, dependencies, and progress for an initiative.
Planners connect traditional project planning with today’s digital work tools. In the PMBOK context, planning defines the approach, scope, schedule, resources, and risks for execution.
A planner is a shared map for the next stretch: it shows what is due, who is waiting on what, and which commitments move when a task shifts.
The initiative is decomposed into deliverable tasks or work packages.
Dates and dependencies show the order in which work can proceed.
Status and deviations are visible so the team can adjust.
A planner provides shared working memory and makes coordination inspectable. It stays useful when assumptions, status, and ownership are kept current.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.