Free CIS-SPM Exam Dumps Preview

According to the ServiceNow documentation1, the it_program_manager role is needed to group related projects and demands. This role can create and manage programs, which are containers for projects and demands that share a common goal or objective. The other options are incorrect because:

B. it_project_manager: The it_project_manager role can create and manage projects, but not group them
into programs.
C. it_demand_manager: The it_demand_manager role can create and manage demands, but not group
them into programs.
D. it_project_user: The it_project_user role can view and edit project tasks, but not create or manage
projects, demands, or programs.

https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-portfolio-management/concept/c_ProgramManagement.html
https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/concept/c_ProjectManagement.html
https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/concept/c_DemandManagement.html
https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_Roles.html

According to the ServiceNow documentation1, the Project Workspace is a central location for creating and managing projects. It provides a graphical interface that allows users to view and edit project information, such as tasks, resources, risks, issues, and dependencies. The Project Workspace also enables users to collaborate with team members and stakeholders, track project progress, and generate reports.

The other options are incorrect because:
A. A central location to view of all projects in a portfolio to prioritize work: This describes the Portfolio
Workbench, not the Project Workspace.
C. A central location transform the navigation of lists and forms into an interactive graphical experience:
This describes the Lens, not the Project Workspace.

D. A central location for viewing and assessing business demands: This describes the Demand
Workbench, not the Project Workspace.

https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/concept/c_ProjectWorkspace.html
https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-portfolio-management/concept/c_PortfolioWorkbench.html
https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/it-business-management/concept/c_Lens.html
https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/concept/c_DemandWorkbench.html

According to the ServiceNow documentation1, the Business Unit field on a Project or Demand form is a reference field that displays values from the cmn_department table. A reference field stores a link to a record on another table, rather than storing the data directly in the field.

https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_ProjectTable.html
https://docs.servicenow.com/bundle/vancouver-platform-administration/page/administer/form-administration/concept/c_ReferenceFields.html

The project status report allows project managers to do the following:

Show historical trend of project KPI's: The project status report displays the key performance indicators (KPIs) of the project, such as schedule variance, cost variance, and earned value. It also shows the historical trend of these KPIs over time, which helps project managers monitor the progress and performance of the project. You can find more information about the project status report KPIs in the Product Documentation for ServiceNow.

Print as a PDF attachment: The project status report can be printed as a PDF attachment and sent to the stakeholders or sponsors of the project. This helps project managers communicate the status and health of the project in a clear and concise format. You can find more information about the project status report PDF attachment in the Product Documentation for ServiceNow.

According to the Scenario Planning for PPM document, a portfolio manager can access the Portfolio Planning Workbench by navigating to either the Portfolio Planning related link on the portfolio form or the Portfolio Planning Workbench module under the Portfolio Planning application menu. The other options are not correct, as they do not lead to the Portfolio Planning Workbench. The Project module is under the Project Portfolio Management application menu and the Program Workbench is under the Program Management application menu.

According to the ServiceNow documentation1, the planning console can show as many WBS levels as desired, starting from the level 1 to the lowest system components. The WBS levels can be expanded or collapsed by clicking the plus or minus icons next to the task names. The planning console also allows users to create, edit, and delete tasks, as well as add dependencies, assign resources, and track progress.

https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/concept/c_PlanningConsole.html

A baseline is a data copy of the current project's task, schedule, or structure that can be used for comparison reporting later. A baseline captures the original plan of the project and allows you to track the changes and deviations from the plan over time. You can create multiple baselines for a project and compare them with the current state of the project. You can find more information about baselines in the Product Documentation for ServiceNow.

According to the ServiceNow documentation1, the Idea [im_idea_core] table is a base table that is not extended from any other table. It stores information about ideas and their categories. The other options are incorrect because:

Task: The Task table is a base table that is extended by many other tables, such as Project, Demand, Incident, etc.

Idea Modules: The Idea Modules table is a child table of the Idea [im_idea_core] table that defines the idea modules displayed on the Idea Portal.

Project: The Project table is a child table of the Task table that stores information about projects.

https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/reference/r_IdeaTable.html
https://docs.servicenow.com/bundle/vancouver-platform-administration/page/administer/table-administration/concept/c_TableHierarchy.html
https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/reference/r_IdeaModulesTable.html
https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_ProjectTable.html

According to the Category Configuration document, the default table that stores the idea categories that a user can select from when submitting an idea is im_category. This table contains the predefined categories for ideas, such as Business Process, Customer Service, or IT Service. The other options are not correct, as they are not the tables that store the idea categories. The dmn_demand table stores the demand records that are created from the approved ideas. The im_module table stores the idea modules that are used to group ideas by different criteria. The im_idea_core table stores the core fields of the idea records.