Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

A planning period is an interval in which requests and approvals are targeted at. An example would be a month or a quarter. Requests and approvals are made prior in anticipation for the period prior to it’s commencement.

For most of our clients, Typically the planning period is anchored to their the organisations planning cadence, such as their quarterly business review cycle the Quarterly Business Review (QBR). In doing so this allows us to configure Planner in such a way that demand leads have a specified amount of time to put in their requests before it is locked from them and supply leads will have their specified amount of time to go into Planner to review and approve the requests so that any outstanding requests / competing priorities can be surfaced at the client’s QBR marketplace. However there are situations where clients do not prefer this locking mechanism and would prefer Planner to be turned on 24/7 and this is what we call ‘continuous planning’Planner can be configured to support this cadence for demand and supply leads to manage requests, including the ability to lock down requests and provide time for approvals.

Then any outstanding requests or competing priorities (for workforce) can be surfaces in the QBR market place.

There are situations where people choose not to lock Planner down and take a more continuous approach. Continuous planning is partially supported in TeamForm and is an area we are looking to improve further in the coming months.

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@9e4
showSpacefalse
sortmodified
typepage
reversetrue
labelsplanner forecast planning-period allocation-project
cqllabel in ( "allocation-project" , "forecast" , "planner" , "planning-period" ) and type = "page" and space = "OS"

...