SPM - Demand and Project functional definitions

[Tommaso2]

Hi all,

For demand and project, can you please share with me:

- When and why are they created? (e.g. why I should open a demand/project rather than a change request or service request?)

Can you please share examples?

- Who creates them? (I know demand manager / project manager, but can you please provide a functional explanation and share examples? E.g. demand is created by individuals that ...)

Many thanks,

Tommaso 

[Mark Manders · Accepted solution]

Who creates them is really depending on your organization. I have customers where every single user can create demands and those are evaluated by the demand manager. But you can also use idea management for that and create demands from (approved) ideas. 

Changes are more related to IT (ITSM module). They are used to control modifications to infrastructure or services to minimize risks. 

Service requests are predefined in the system and users can request those.

Demands capture new ideas or business needs or enhancements in a broader scope than just IT and are including assessments and scoring

Projects are to manage the execution of strategic or operational initiatives.

These different task types can be related to each other (eg projects can have multiple changes) but it all comes down to how you are managing everything within your organization. You can create changes as projects or vice versa, depending also on you licensing. But they do serve different processes and have different functionality (projects will give insight in budget/cost, which changes often lack).