Legislative and dependency prioritization criteria
In portfolio management, as described in PMI's Standard for Portfolio Management and the PfMP framework, components (programs, projects, and other work) are evaluated and ranked against a set of prioritization criteria. Legislative and dependency criteria are two key criteria that sit alongside strategic alignment, financial return, and risk. Legislative (regulatory or mandatory) criteria apply to components required by laws, regulations, industry standards, government mandates, or contractual obligations. Examples include data privacy compliance, safety regulations, tax reporting changes, and environmental rules. These components are often classed as non-discretionary. Because noncompliance can bring fines, legal action, license revocation, reputational damage, or forced shutdown of operations, they usually receive top priority or are placed in a protected mandatory category before discretionary work is scored. Portfolio managers still assess them for the most efficient way to comply, the deadlines involved, and their effect on resource capacity. Even when a mandatory component offers little financial return, its value lies in preserving the organization's license to operate. Dependency criteria consider how components rely on one another. A component may be an enabler that delivers infrastructure, capabilities, data, or outcomes that other components need before they can start or realize benefits. Dependencies can be technical, resource-based, schedule-based, or benefit-related, and they may be internal to the portfolio or external, such as with vendors or other portfolios. A component with a modest standalone score may receive higher priority because many high-value initiatives depend on it. Conversely, a component that depends on unfinished work may be deferred. Portfolio managers map these relationships, often using dependency matrices or roadmaps, so that sequencing, funding, and resource allocation follow a logical order. Together, these criteria ensure the portfolio is not ranked solely by attractiveness. Legislative criteria protect the organization from compliance risk, while dependency criteria keep execution feasible and support the realization of overall portfolio benefits, strategic balance, and an achievable roadmap.
Legislative and Dependency Prioritization Criteria in Portfolio Strategic Management (PfMP)
In the PfMP framework, prioritization decides which portfolio components (programs, projects, subsidiary portfolios and operations) receive funding, resources and attention first. Most components are ranked on their strategic value, financial return and risk. Two kinds of criteria behave differently from the rest: legislative (regulatory or mandatory) criteria and dependency criteria. They often override or adjust a pure value-based ranking. This guide covers what they are, why they matter, how they work in practice, and how to handle them on the PfMP exam.
1. What Are Legislative and Dependency Prioritization Criteria?
Legislative (Regulatory / Mandatory) Criteria
These criteria apply to components that the organization must carry out because of laws, regulations, government mandates, industry standards, contractual obligations or audit findings. Examples include:
- Data privacy compliance, such as GDPR or HIPAA updates
- Environmental, health and safety regulations
- Financial reporting rules, such as Sarbanes-Oxley or IFRS changes
- Tax law changes that require system updates
- Accessibility or consumer protection mandates
Components in this group are often called mandatory, non-discretionary or must-do components. Their key traits are:
- They may show little or no financial return, yet they are still required.
- Failing to deliver them can bring fines, legal action, loss of license, reputational damage or shutdown.
- They usually have fixed external deadlines that the organization cannot negotiate.
Dependency Criteria
These criteria reflect the relationships between components. A component may need to be prioritized because:
- Other high-value components depend on its outputs. For example, a data platform project may enable several analytics and AI initiatives.
- It provides a shared resource, capability or infrastructure that others need.
- It sits on the critical path of a strategic program.
- It depends on another component, so it cannot start until that predecessor finishes.
Dependencies can be:
- Technical: system, architecture or infrastructure prerequisites
- Resource: shared scarce people, skills or equipment
- Benefit: one component's benefits are realized only when another delivers
- Schedule or logical: sequencing constraints
- External: vendors, partners, regulators or other portfolios
2. Why Are These Criteria Important?
a) Protecting the organization
Legislative components shield the organization from legal and compliance risk. A portfolio that funds only high-ROI initiatives while missing a regulatory deadline exposes the organization to penalties that can wipe out the gains from every other component.
b) Realistic, executable portfolios
Dependency criteria make sure the portfolio can actually be delivered. Funding a high-value component while starving its enabling component produces delays, rework and lost benefits.
c) Optimizing total portfolio value
Portfolio management aims to maximize the value of the whole portfolio, not of single components. An enabling component with a low standalone score may unlock large value across many others.
d) Governance and transparency
Clear criteria for mandatory and dependent components make prioritization decisions defensible to the portfolio governance body, auditors and stakeholders.
e) Capacity planning
Mandatory components consume capacity first. Knowing this early lets the portfolio manager see how much discretionary capacity is left for strategic investments.
3. How Do They Work in Practice?
Step 1: Identify and categorize components
During the evaluation and categorization activities of portfolio strategic management, components are tagged. Typical categories include mandatory/regulatory, strategic growth, operational efficiency, maintenance and innovation. Regulatory items are flagged and checked with legal, compliance or risk functions.
Step 2: Validate the mandate
The portfolio manager confirms that the requirement is real, how far it extends, what the deadline is and what minimum scope is needed for compliance. Not everything labelled mandatory truly is. Only the compliant scope is non-negotiable, while extra enhancements bundled with it should be scored like any other discretionary work.
Step 3: Apply legislative criteria as a filter or high weight
Organizations commonly handle mandatory items in one of two ways:
- Pre-allocation or screening filter: mandatory components are funded first, outside the competitive scoring, and the remaining capacity goes to discretionary components.
- Very high weighting: a compliance criterion in the weighted scoring model carries enough weight that mandatory items rise to the top.
Either way, the governance body approves the approach and records it in the portfolio management plan.
Step 4: Map dependencies
Tools include dependency matrices, network diagrams, portfolio roadmaps and interdependency registers. The portfolio manager identifies predecessor and successor relationships, shared resources and benefit links between components.
Step 5: Adjust ranking and sequencing
- Enablers on which high-priority components rely are moved up or scheduled earlier.
- Dependent components are sequenced after their prerequisites, even when their individual scores are high.
- When a high-scoring component depends on a low-scoring one, both are assessed together as a package.
Step 6: Balance the portfolio
After mandatory and dependency constraints are applied, the portfolio is balanced against strategic goals, risk appetite and capacity. If mandatory work consumes too much capacity, the portfolio manager escalates to governance with options, such as extra funding, deferring discretionary work or phasing.
Step 7: Monitor and re-prioritize
New laws, changed deadlines, cancelled components or shifting dependencies trigger re-evaluation. Portfolio reviews should check regulatory changes and the dependency map on a regular cycle.
Illustrative Example
A bank has a budget for ten initiatives. One is a new anti-money-laundering reporting system required by the regulator within 12 months (legislative). Another is a core data platform that scores modestly but three top-ranked digital banking initiatives rely on it (dependency). A sound process funds the AML system first, places the data platform early on the roadmap, sequences the digital initiatives after it, and then fills the remaining capacity using the weighted scoring results.
4. Common Misconceptions
- Mandatory means unlimited scope. Only the scope needed for compliance is mandatory.
- Low-scoring components should always be cut. A low-scoring enabler may be essential to the portfolio's value.
- Dependencies are only a project scheduling issue. At portfolio level they affect selection, funding, resource allocation and benefit realization.
- Regulatory items need no governance. They still require authorization, tracking and reporting through portfolio governance.
5. Exam Tips: Answering Questions on Legislative and Dependency Prioritization Criteria
Tip 1: Compliance comes first. When a scenario mentions a legal, regulatory or government requirement with a deadline, the correct answer nearly always prioritizes that component, even over components with higher ROI or stronger sponsors.
Tip 2: Validate before acting. If a stakeholder claims a component is mandatory, a strong answer is to confirm the requirement with legal or compliance and define the minimum compliant scope, rather than accepting the claim at face value or rejecting it.
Tip 3: Think at portfolio level. Prefer answers that consider total portfolio value, strategic alignment and interdependencies over answers that optimize a single component.
Tip 4: Watch for hidden enablers. If a question describes a low-scoring component that other strategic components rely on, the best answer usually keeps or elevates it. Cancelling it would damage benefits elsewhere.
Tip 5: Analyze impact before cancelling or deferring. When asked to terminate, suspend or deprioritize a component, look for the option that first assesses dependencies and the effect on other components and benefits.
Tip 6: Use governance. Changes in priority, especially those triggered by new legislation or broken dependencies, should go through the portfolio governance body. Answers where the portfolio manager acts alone on major reprioritization are usually wrong.
Tip 7: Know the tools. Expect references to weighted scoring models, screening or filtering criteria, dependency matrices, portfolio roadmaps, capacity and capability analysis, and the portfolio management plan. Mandatory items are often treated as a screening filter or pre-allocation.
Tip 8: Recognize capacity trade-offs. If mandatory work uses most capacity, the best answer often involves informing governance, presenting options and rebalancing discretionary components, not quietly cutting compliance scope.
Tip 9: Respond to change. A new regulation in the middle of a cycle is a trigger to re-evaluate and rebalance the portfolio, update the roadmap and communicate with stakeholders.
Tip 10: Eliminate extreme options. Discard answers that pursue the highest ROI regardless of compliance, cancel components with no impact analysis, or let the loudest sponsor set priorities.
Sample Question
A portfolio manager learns that a new data protection law takes effect in nine months. The required system changes are not in the current portfolio, and capacity is fully allocated to high-ROI strategic initiatives. What should the portfolio manager do first?
A. Continue with the current plan, because the strategic initiatives offer higher returns
B. Assess the regulatory requirement and its impact on the portfolio, then present rebalancing options to the governance body
C. Cancel the lowest-ranked strategic initiative and start the compliance work
D. Ask the compliance department to handle the change outside the portfolio
Answer: B. It recognizes the mandatory nature of the requirement, includes impact analysis covering dependencies and capacity, and uses governance for the decision. A risks non-compliance, C skips analysis and governance, and D undermines portfolio visibility and resource control.
Key Takeaways
- Legislative criteria identify must-do components that protect the organization from legal and compliance risk.
- Dependency criteria make sure enabling components are funded and sequenced so the portfolio can deliver its intended value.
- Both criteria shape ranking, sequencing, capacity allocation and balancing.
- On the exam, favor answers that combine compliance, impact analysis, a portfolio-wide view and governance involvement.