CIS-SPM Certified Implementation Specialist - Strategic Portfolio Management Questions and Answers

Cost Plans and Monetary Benefit Plans are the related lists that should primarily be used to capture financial data in a project. Cost Plans allow you to define the expected costs of a project over time, based on the planned and actual work, resources, and expenses. Monetary Benefit Plans allow you to define the expected financial benefits of a project over time, based on the estimated and realized value, revenue, and savings. You can find more information about these related lists in the Product Documentation for ServiceNow.

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 field2.

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

According to the ServiceNow documentation1, a demand manager can view and edit the following artifacts from a demand:

Decision: A decision that affects the demand or its outcome2.

Risk: A risk that could impact the demand or its outcome3.

Requirement: A requirement that defines the scope or functionality of the demand4.

The other options are not artifacts of a demand, but rather related entities that can be created from a demand or linked to a demand.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/concept/c_DemandManagement.html 2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/task/t_CreateADecision.html 3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/task/t_CreateARisk.html 4: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/task/t_CreateARequirement.html

According to the ServiceNow documentation1, the timecard_admin role can approve time sheets or submit time cards on behalf of team members. This role also has the ability to create and modify time sheet policies, time sheet groups, and time sheet periods. The other options are incorrect because:

A. activity_admin: The activity_admin role can create and modify activities, activity sets, and activity plans2.

C. form_admin: The form_admin role can create and modify forms, form sections, and form layouts3.

D. approval_admin: The approval_admin role can create and modify approval rules, approval groups, and approval stages4.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/time-card-management/reference/r_TimeCardManagementRoles.html 2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_ActivityManagementRoles.html 3: https://docs.servicenow.com/bundle/vancouver-platform-administration/page/administer/form-administration/concept/c_FormAdministration.html 4: https://docs.servicenow.com/bundle/vancouver-platform-administration/page/administer/approvals/concept/c_Approvals.html

A resource event is a non-scheduled activity that affects the availability and capacity of a resource or a group of resources. Examples of resource events are vacations, holidays, training, or sick leave. Resource events can be created by resource managers or resources themselves, and they can be viewed in the resource calendar or the resource workbench. You can find more information about resource events in the Product Documentation for ServiceNow.

According to the ServiceNow documentation1, the cost_plan_breakdown table stores the cost information for a specific fiscal period. This table contains the fields such as cost plan, fiscal period, amount, and currency. The other options are incorrect because:

B. pm_project: The pm_project table stores the information about projects, such as name, description, state, and status2.

C. cost_plan: The cost_plan table stores the information about cost plans, such as name, type, and project3.

D. expense_line: The expense_line table stores the information about expense lines, such as expense type, amount, and date4.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_CostPlanBreakdownTable.html 2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_ProjectTable.html 3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_CostPlanTable.html 4: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_ExpenseLineTable.html

According to the Completing Demand Assessments document, demand assessments are triggered as soon as the demand enters the Submitted state. The other options are not correct, as demand assessments are not triggered when the demand is Approved, Screening, or Qualified.

According to the ServiceNow documentation1, the pm_home_page_config table is used to configure the parameters displayed on a project card on the My Projects Space page of the Project Workspace. The other tables are used for different purposes:

pm_project: Stores information about projects2.

pm_toplevel_project: Stores information about top-level projects3.

project_template_config: Stores information about project templates.

According to the Cost plan breakdown document, users are required to enter the cost type for each cost plan line item. Cost type is a mandatory field that specifies the type of cost, such as labor, software, hardware, etc. The other options are not required fields for a cost plan for a demand. Discount Rate % is an optional field that applies a discount rate to the cost plan. Total planned cost is a read-only field that displays the sum of the planned cost for all the cost plan breakdowns. Functional currency is a system property that defines the currency used for cost management.

According to the Using the Demand Workbench document, if a user creates a new demand from the demand workbench, the system saves the record in the qualified state and displays it on the bubble chart. The other options are not correct, as they are not the default state for a new demand created from the demand workbench. The approved state is the final state for a demand that has passed all the assessments. The open state is the initial state for a demand that is created from the Service Catalog. The draft state is the state for a demand that is created from the Demand form.

According to the ServiceNow documentation1, a program is a container for the following:

Program tasks: Tasks that define the scope and deliverables of the program2.

Issues: Problems that affect the program or its outcome3.

Cost plans: Plans that estimate the cost of the program and its components4.

A portfolio is not a part of a program, but rather a collection of programs and projects that are aligned with a strategic goal or objective.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-portfolio-management/concept/c_ProgramManagement.html 2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-portfolio-management/task/t_CreateAProgramTask.html 3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-portfolio-management/task/t_CreateAnIssue.html 4: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-portfolio-management/task/t_CreateACostPlan.html : https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-portfolio-management/concept/c_PortfolioManagement.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 Workspace2.

C. A central location transform the navigation of lists and forms into an interactive graphical experience: This describes the Lens, not the Project Workspace3.

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

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/concept/c_ProjectWorkspace.html 2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-portfolio-management/concept/c_PortfolioWorkbench.html 3: 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 Stakeholder Registry document, the combination of the user and the assigned portfolio must be unique when adding a user to the stakeholder registry. The stakeholder registry is a table that stores information about the stakeholders of a portfolio. The other options are not correct, as they are not registries that require a unique combination of user and portfolio. The application registry is a table that stores information about the applications in the system. The event registry is a table that stores information about the events that trigger notifications. The UX page registry is a table that stores information about the UX pages that are available for portfolios.

According to the Assigning Resource Roles document, to set up a group for selection in a resource plan, the group record needs to include the pps_resource role. This role grants access to the Resource Management application and allows the group members to view and update their resource allocations. The other options are not correct, as they are not required for a group to be selected in a resource plan. The it_project_user role grants access to the Project Portfolio Management application and allows the user to create and update projects. The itil role grants access to the ITIL application and allows the user to manage incidents, problems, and changes. The resource_manager role grants access to the Resource Management application and allows the user to manage resource plans and allocations.