ServiceNow CIS-SPM - Certified Implementation Specialist - Strategic Portfolio Management

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 Project Summary - Waterfall Dashboard document, depending on the execution type selected for a particular project, the Project Summary - Waterfall Dashboard will also be available. This dashboard provides a comprehensive view of the project status, progress, and performance using various widgets. The other options are not correct, as they are not dashboards that are dependent on the execution type of the project. The Timecard Dashboard is a dashboard that displays the time worked by users on various tasks. The User Manager Dashboard is a dashboard that displays the user management activities and statistics. The PMO Dashboard is a dashboard that displays the portfolio and project performance and health.

According to the ServiceNow documentation1, this property controls whether the cost roll-ups are performed when a sub-project and parent project have different project currencies. If this property is set to true, then the system converts the sub-project currency to the parent project currency using the exchange rate table and performs the cost roll-ups. If this property is set to false, then the system does not perform the cost roll-ups for sub-projects with different currencies.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_Properties.html

According to the ServiceNow documentation1, this property controls whether the start dates of the resource plan, cost plan, and benefit plan are automatically updated when the start date of the demand or project is changed. If this property is set to true, then the plans will be shifted by the same number of days as the demand or project start date change. If this property is set to false, then the plans will not be affected by the demand or project start date change.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_Properties.html

According to the ServiceNow documentation1, a rate card is a table that defines the hourly cost of labor for different roles or resources. A project rate is a fixed rate that is applied to all resources assigned to a project, regardless of their roles or individual rates. Both of these can be used to calculate the planned cost of a resource plan by multiplying the hours allocated to each resource by the corresponding rate. The other options are incorrect because:

A. Demand rate: A demand rate is a rate that is applied to a demand, not a resource plan. It is used to estimate the cost of fulfilling a demand before it is converted into a project2.

C. Default rate: A default rate is a rate that is applied to a resource when no other rate is specified. It is not a valid option for calculating the planned cost of a resource plan, as it is only used as a fallback option3.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/resource-management/concept/c_RateCards.html 2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/concept/c_DemandRate.html 3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/resource-management/concept/c_DefaultRate.html

According to the RIDAC (Risk, Issue, Decision, Action, and Request Changes) record entries for a project document, the RIDAC workflow can be modified by using the Workflow Editor, which is a graphical tool that allows you to create and edit workflows. The other options are not correct, as they are not recommended features for modifying the RIDAC workflow. The Project Form is used to create and update project records. The Flow Designer is used to automate processes without coding. The Service Catalog is used to order items and services.

According to the web search results1, the timecard_admin role is the minimum role that is required to assign a time sheet policy to a user. A time sheet policy is a rule that controls the creation and operation of time sheets for resources who log time against work items. The timecard_admin role can create and modify time sheet policies, time sheet groups, and time sheet periods, as well as approve time sheets or submit time cards on behalf of team members. The other options are incorrect because:

A. ppm_admin: The ppm_admin role is a higher-level role that can access all Project and Portfolio Management modules and features, but it is not the minimum role required for assigning a time sheet policy to a user2.

C. it_project_manager: The it_project_manager role can create and manage projects, but not assign time sheet policies to users3.

D. It is not possible to assign a time sheet policy to a user: This is false, as it is possible to assign a time sheet policy to a user by using the Time Sheet Policy field on the User form4.

1: 3 2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_Roles.html 3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/concept/c_ProjectManagement.html 4: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/time-card-management/reference/r_TimeCardManagementRoles.html