The demand manager typically works with a business relationship manager to identify
stakeholders and elicit requirements, risks, and other important information.
The Demand Management application streamlines the stakeholder identification process by
auto-populating the list of stakeholders based on the portfolio the user selects when filling out
the demand form in the service catalog or in the Demand Management application. The Demand
Management application also allows you to use assessments to automate some of the information
When a demand is submitted, the demand stakeholder list is populated automatically from
associated portfolio. You can also add stakeholders. To add a person to the stakeholder list,
scroll to the Stakeholders related list on the Demand form, click
New to create a record, and fill in the form.
When adding a new stakeholder from the demand form, the Portfolio field
displays the portfolio that was selected on the Demand form.
A demand can have multiple stakeholders and a stakeholder can be associated with multiple
The newly added stakeholder is automatically associated with the current demand and any other
demands going forward that use the same portfolio.
Demand managers can create as many requirements as needed, but requirements are not mandatory.
Typically, the stakeholders associated with a demand request should have input into what the
requirements are for a demand request to be completed.
Demand managers can use the Requirement form to describe the requirement and assign an owner
who is responsible for making sure the requirement is met. If a requirement is especially
complex, demand managers can associate planned tasks, such as project tasks, with the
requirement, and assign and track those tasks until they are complete.
To add a requirement to a demand, open a Demand form and click New
related list (see table for field descriptions).
Table 1. Requirement form
||Unique identification number for the requirement. This number is automatically
generated when a new requirement record is created.
||User requesting the requirement. This field is automatically populated with the name
of the person filling out the form, but the source could be a different person who
identified the requirement.
||User or group who is responsible for managing the requirement or making sure the
requirement is met.
||Approximate amount of time to complete the requirement and any associated
||Importance of the requirement as it applies to the overall demand.
||Status of the requirement can be Pending,
Approved, or Rejected. Note that the request
state is independent of the demand request state and of the states of any planned tasks
associated with the requirement. The requirement state does not have to be closed to close
the request. Likewise, closing the request does not change the state of the
||Type of requirement can be: Business, Solution
(Functional), Solution (Non-Functional),
Quality, Stakeholder, or
||Brief description of the requirement.
||Detailed description of the requirement and any associated tasks. For example, you
can use this field to describe an expected outcome or result.
A risk is any uncertain event that can potentially impact the success or outcome of a project.
For example, schedule slippage is a risk, even if it's caused by incorrect estimating. Another
example of a risk is a change in project requirements. It is important to record risks so
decision makers have all relevant information when assessing a demand.
To add a risks to the demand, scroll to the Risks
related list on the Demand
form and click New
to create a record (see table for field
Table 2. Risk form
||The current state of the risk. Available options are: Pending,
Achieved, and Not Achieved.
||The likelihood that the event described by the risk will occur during the course of
||Brief description of the event and its potential impact on the success of the
activity specified in the demand.
||Cost the event will generate should it occur.
||Cost generated by the event. This information is added when and if the event
||Brief description of efforts taken to mitigate the risk.
To add a decision to the demand, scroll to the Decisions
related list on the
Demand form and click New
to create a record (see table for field
Table 3. Decision form
||Unique number for the decision. This number is automatically generated when a new
decision record is created.
||Person requesting the decision. This field is automatically populated with the name
of the person entering the decision.
||The date the decision needs to be finalized.
||Brief description of the decision such as, what the decision is about, who made it,
who it affects, and the decision outcome.
||The current state of the decision. Available options are:
Pending, Approved, and
||Check box that enables (selected) or disables (cleared) the approval requirement for
Adding Resource Plans
Resource plans are another source of information that decision makers can use when evaluating
demands. You can create resource plans for a demand from the Resource Plan related list, which
appears only if the Resource Management application is activated.
To add a resource plans to the demand, scroll to the Resource Plan
list on the Demand form and click New
to create a record.