CIS-SPM practice question 25 of 25

Which artifacts can be linked to either a program, a portfolio, both, or neither? Choose 2 answers

Full set: 112 questions

Domain Portfolio Management

Answer options
A: Operational plans
B: Demands Correct answer
C: Test cases
D: Stories
E: Projects Correct answer
Correct Answer:
B. Demands; E. Projects
Explanation

In ServiceNow Strategic Portfolio Management (SPM), both Demands and Projects are fundamental artifacts that offer flexible associations. A Project can exist as a standalone entity (neither), be part of a Program, be included in a Portfolio, or be part of a Program that itself belongs to a Portfolio (both). Similarly, a Demand can be created as a standalone idea or request (neither) or be associated with a Portfolio for evaluation and alignment against strategic objectives. Once qualified, a demand can be converted into a project, which can then be associated with a program, creating an indirect link. This flexibility is central to managing work from initial idea to execution within the SPM framework.

Why Incorrect

A. Operational plans: This is not a standard, discrete artifact type in ServiceNow SPM that can be directly linked to programs or portfolios in the same manner as projects or demands.
C. Test cases: Test cases are highly granular artifacts related to quality assurance. They are linked to specific development tasks like stories or defects, not directly to high-level strategic structures like programs or portfolios.
D. Stories: Stories are granular units of work in agile development. They are typically children of epics or features within a project's hierarchy, making their link to a program or portfolio indirect and not a primary association.

References

1. ServiceNow Product Documentation - Project Workspace: The documentation on creating and managing projects explicitly shows that the 'Portfolio' and 'Program' fields on a project record are optional reference fields. This confirms a project can be linked to a portfolio, a program, both, or neither if the fields are left blank.

Reference: ServiceNow Product Documentation, "Create a project in Project Workspace," section on Project form fields.

2. ServiceNow Product Documentation - Demand Management: The documentation for Demand Management illustrates that a demand can be created and exist independently. It also details how a demand can be associated with a 'Portfolio' for assessment using the demand workbench. The 'Portfolio' field on the demand form is optional.

Reference: ServiceNow Product Documentation, "Create a demand," section on Demand form fields.

3. ServiceNow Product Documentation - Portfolio Workbench: The Portfolio Workbench is a central tool for managing portfolios and shows that a portfolio's contents can include both Demands and Projects, demonstrating the direct link between these artifacts and a portfolio.

Reference: ServiceNow Product Documentation, "Use the Portfolio Workbench," section on workbench components.

Scroll to Top