Innovation Portfolios, Ecosystems and Intellectual Property

Introduction

Product innovation rarely succeeds through a single project managed in isolation. Organisations must decide which opportunities to pursue, how much to invest, which capabilities to build internally, and when to collaborate with customers, suppliers, start-ups, universities, platforms and competitors. These decisions are made under uncertainty: customer needs may change, technologies may fail, competitors may respond, and regulation may alter the attractiveness of an opportunity.

Innovation portfolio management provides a disciplined way to balance current business performance with future growth. Ecosystem management extends the analysis beyond the organisation to the network of participants that create, distribute and capture value. Intellectual property (IP) management protects, enables and sometimes limits the use of knowledge, designs, brands and technologies.

For product managers, these topics are strategically connected. A promising product may require a patent, depend on a platform partner, use open-source software, compete for scarce engineering resources and expose the firm to substantial regulatory or technological risk. Effective management therefore involves portfolio choices, relationship design, legal awareness and continuous learning.

Learning Objectives

By the end of this chapter, you should be able to:

1. Distinguish core, adjacent and transformational innovation initiatives.
2. Construct and evaluate an innovation portfolio under uncertainty.
3. Apply resource-allocation and portfolio-risk principles to product decisions.
4. Explain open innovation, ecosystems, platforms and partnership governance.
5. Distinguish patents, trademarks, copyrights, trade secrets and design rights.
6. Identify ethical, regulatory and operational risks associated with innovation and IP.
7. Recommend an integrated portfolio, ecosystem and IP strategy.

1. Innovation Portfolios: From Individual Projects to Strategic Balance

An innovation portfolio is the collection of innovation initiatives funded or sponsored by an organisation. It may include new products, product improvements, process innovations, business-model experiments, technology research, platform investments and capability-building projects.

Managing a portfolio differs from managing a project. A project manager asks whether a particular initiative is being executed effectively. A portfolio manager asks whether the organisation is pursuing the right combination of initiatives. A project can be well managed but strategically unsuitable; conversely, an important initiative may require experimentation because its path to success is uncertain.

Portfolio management seeks balance across several dimensions:

• time horizon: immediate, medium-term and long-term value;
• risk: technical, market, financial, operational, regulatory and reputational risk;
• strategic fit: alignment with organisational purpose and capabilities;
• resource demand: people, capital, data, equipment and managerial attention;
• dependency: reliance on shared platforms, suppliers or other projects; and
• learning value: the extent to which an initiative reduces important uncertainty.

Core, adjacent and transformational innovation

A useful strategic classification is the three-horizon or three-zone portfolio.

Core initiatives include reliability improvements, feature enhancements, cost reduction and compliance updates. They often have relatively clear customer demand and established capabilities. Their strategic risk is under-investment: a company that focuses only on core work may become efficient at serving a declining market.

Adjacent initiatives apply existing capabilities in new contexts. A business-to-business analytics firm, for example, might adapt its product for smaller firms or enter a related industry. Adjacent projects benefit from some existing knowledge but require new market learning, partnerships or capabilities.

Transformational initiatives seek significant changes in technology, customer behaviour or business model. Examples include a physical-device company developing a subscription platform or a traditional retailer building a digital marketplace. Transformational initiatives can generate substantial value but are difficult to evaluate using conventional forecasts because historical data may be limited.

The categories are not permanent labels. An experimental project may begin as transformational, become adjacent after a validated use case is found, and eventually enter the core portfolio. Portfolio reviews should therefore examine whether an initiative has changed category.

Balance is not a fixed percentage

Managers sometimes use simple allocation rules, such as investing most resources in core work and smaller amounts in adjacent and transformational work. Such ratios can encourage discussion, but they should not be treated as universal laws. The appropriate balance depends on industry turbulence, competitive intensity, cash position, organisational capabilities and the expected life of the current business.

A mature organisation in a stable market may rationally allocate more to core improvement. A technology firm facing rapid disruption may need greater transformational investment. The key principle is strategic coherence, not mechanical compliance with a predetermined ratio.

2. Evaluating Innovation Under Uncertainty

Traditional investment appraisal assumes that future cash flows can be estimated with reasonable confidence. Innovation decisions often violate this assumption. Early-stage initiatives may have uncertain customers, uncertain technical feasibility and uncertain cost. The objective at this stage is not false precision; it is structured learning and disciplined escalation.

Staged investment and the logic of real options

A staged approach treats investment as a sequence of decisions rather than a single irreversible commitment. The organisation invests a limited amount to test a critical assumption, observes evidence, and then decides whether to continue, change direction or stop.

This resembles a real option. An initial investment creates the opportunity, but not the obligation, to make a larger investment later. The option is valuable when uncertainty is high, downside losses can be limited and new information is expected to arrive before the next decision.

A practical innovation stage sequence may be:

1. Problem validation: confirm that a significant customer problem exists.
2. Concept validation: test whether the proposed solution is desirable.
3. Technical feasibility: demonstrate that the solution can work at an acceptable performance level.
4. Business-model validation: test acquisition, pricing, retention and unit economics.
5. Pilot or minimum viable product: observe behaviour in a realistic context.
6. Scale decision: commit larger resources only when evidence meets predefined criteria.

Each stage should have a decision rule. For example, a team might proceed only if a target customer segment demonstrates repeated use, a technical performance threshold is achieved and a feasible route to regulatory approval is identified.

Expected monetary value

When credible probabilities and financial outcomes are available, expected monetary value can support comparison between alternatives. The general expression is:

Here, EMV is expected monetary value, pᵢ is the probability of outcome i, Vᵢ is the value of outcome i, and C is the relevant investment cost. Probabilities should sum to 1, and values and costs must use the same monetary basis and time period. If cash flows occur over multiple periods, they should normally be discounted before being combined.

Expected value is useful for comparing risk-adjusted alternatives, but it does not capture all managerial considerations. Two initiatives can have the same EMV while differing greatly in downside exposure, learning value, strategic importance or reversibility. Probabilities can also be subjective and vulnerable to optimism bias.

Risk-adjusted portfolio thinking

Portfolio risk is not simply the sum of the risks of individual projects. Projects may be correlated. For example, several products may depend on the same semiconductor supplier or regulatory approval. A common external shock can therefore damage several initiatives at once.

A simplified portfolio variance expression for two initiatives is:

where σₚ² is portfolio variance, w₁ and w₂ are the resource or investment weights, σ₁ and σ₂ are the standard deviations of initiative outcomes, and ρ₁₂ is the correlation between outcomes. The expression assumes that outcomes can be represented quantitatively and that the weights are defined consistently. The correlation coefficient lies between −1 and +1. A positive correlation increases concentration risk; lower correlation can provide diversification.

In practice, product managers need not calculate portfolio variance for every decision. The managerial lesson is to identify shared dependencies and avoid concentrating all initiatives around one uncertain technology, customer segment or channel.

Evidence-based portfolio reviews

A useful portfolio review combines quantitative and qualitative evidence:

• customer discovery and willingness-to-pay evidence;
• adoption, retention and engagement data;
• technical performance and reliability;
• cost-to-serve and scalability;
• legal freedom to operate;
• regulatory feasibility;
• partner readiness;
• strategic fit; and
• learning achieved relative to resources consumed.

The review should distinguish between a project that is failing because its concept is weak and one that is producing valuable learning but requires a revised approach. Continuing a project merely because resources have already been spent is the sunk-cost fallacy. Past expenditure should not determine future investment except insofar as it creates usable assets or knowledge.

3. Resource Allocation and Portfolio Governance

Innovation resources are broader than financial budgets. They include product managers, designers, engineers, data scientists, sales specialists, legal counsel, test facilities, managerial attention and access to customers. A portfolio can be financially funded yet capacity-constrained because the organisation lacks specialist skills.

Capacity allocation

Resource allocation should identify bottlenecks rather than distribute money alone. Important questions include:

• Which scarce capabilities are required by multiple initiatives?
• Which projects have genuine critical-path dependencies?
• Can external partners provide capacity without creating unacceptable risk?
• What work should be stopped to release capacity?
• Is the organisation funding discovery, delivery and post-launch learning?

A practical governance system often includes a portfolio council with representatives from product, technology, finance, operations, marketing, legal and risk. The council should establish entry criteria, review cadence, escalation thresholds and stop criteria. Governance should be proportional: a small experiment should not require the same approval process as a safety-critical product.

Common portfolio biases

Portfolio decisions are affected by predictable biases:

• optimism bias: overestimating benefits and underestimating time or cost;
• confirmation bias: seeking evidence that supports an existing belief;
• status quo bias: protecting established products from disruptive investment;
• executive sponsorship bias: continuing a favoured project despite weak evidence;
• survivorship bias: studying successful innovations while ignoring failed attempts; and
• local optimisation: maximising one department’s performance at the expense of portfolio value.

Countermeasures include independent reviews, explicit assumptions, pre-agreed kill criteria, diverse decision teams, reference-class comparisons and separating the team that proposes an initiative from the group that evaluates it.

4. Innovation Ecosystems and Platforms

An innovation ecosystem is a network of organisations and individuals whose complementary activities contribute to a product, service or market. Participants may include customers, suppliers, complementors, distributors, regulators, infrastructure providers, developers, universities and communities.

An ecosystem differs from a conventional supply chain. A supply chain commonly emphasises sequential flows of materials or services. An ecosystem emphasises interdependence, co-creation, standards, roles and value capture. A software platform, for example, may create value only when independent developers provide applications and users adopt them.

Platforms and network effects

A platform provides a foundation, interface or set of rules that enables interactions or complementary products. Examples include operating systems, payment infrastructures, developer platforms and app marketplaces.

Network effects occur when the value of a product changes as participation changes. A direct network effect arises when users benefit from more users of the same service, as in some communication systems. An indirect network effect occurs when one group attracts complements that benefit another group, such as users and application developers.

Network effects can create rapid growth, but they do not guarantee success. Poor quality, privacy failures, congestion, incompatible standards and abusive platform governance can reduce participation. Product managers must design onboarding, incentives, APIs, quality controls, data rules and dispute processes.

Open innovation

Open innovation is the purposeful management of knowledge flows across organisational boundaries. It includes:

• inbound innovation: acquiring or using external knowledge;
• outbound innovation: licensing, selling or otherwise transferring internal knowledge; and
• coupled innovation: co-developing value through partnerships or alliances.

Open innovation does not mean sharing everything freely. It means deciding deliberately which knowledge should be internal, licensed, jointly developed, published or protected. The decision depends on strategic importance, absorptive capacity, transaction costs, IP rights, trust and the need for speed.

Partnership design and governance

Partnerships should begin with a clear statement of mutual value. A contract alone cannot resolve an unclear business model. Effective partnership design addresses:

1. objectives and measurable outcomes;
2. roles, responsibilities and decision rights;
3. contribution of data, technology, capital and personnel;
4. ownership of pre-existing and newly created IP;
5. confidentiality and permitted disclosures;
6. security, privacy and regulatory responsibilities;
7. service levels, quality and audit rights;
8. revenue sharing, pricing or licensing;
9. mechanisms for resolving disputes; and
10. termination, transition and treatment of customer data.

Trust is important, but trust should be supported by transparent processes, access controls, documentation and escalation routes. A partnership can fail through misaligned incentives even when the participants have good intentions.

5. Intellectual Property for Product Managers

Intellectual property law varies by jurisdiction, and legal advice should be obtained for specific decisions. Nevertheless, product managers need enough knowledge to recognise issues early and involve specialists.

Patents

A patent can provide an exclusionary right over a claimed invention for a limited period, subject to national law, examination, fees and enforcement. Patentability commonly involves novelty, inventive step or non-obviousness, and industrial applicability or utility, although terminology and standards differ.

The timing of disclosure is critical. Public disclosure before filing can destroy novelty in many jurisdictions, though some jurisdictions provide limited grace periods. Teams should therefore use invention-disclosure procedures and consult patent counsel before publishing technical details, demonstrating prototypes publicly or releasing documentation.

A patent does not automatically provide freedom to operate. A firm may own a patent and still infringe another party’s patent when commercialising the product. Freedom-to-operate analysis is a separate investigation of relevant third-party rights.

Trademarks and brand assets

A trademark strategy begins with selecting a distinctive name, conducting clearance searches and registering or otherwise protecting the mark where appropriate. Product managers should avoid assuming that a domain name or social-media handle creates trademark rights. Brand use should be consistent, and unauthorised use should be monitored.

Copyright and software

Copyright generally protects the expression of an idea, not the underlying idea, method or functionality. Software, user-interface graphics, documentation, photographs and marketing content may all involve copyright. Ownership can depend on employment status, contractor agreements, jurisdiction and contractual assignment.

Open-source software can accelerate development, but each licence imposes conditions. Teams must maintain an inventory of dependencies, comply with attribution and notice requirements, understand distribution obligations, and assess security vulnerabilities. “Open source” does not mean “without obligations.”

Trade secrets

Trade secrets can protect algorithms, manufacturing processes, customer lists, pricing models and other confidential information when the information has value because it is secret and the organisation takes reasonable steps to preserve secrecy. Protection may be lost through careless disclosure. Controls include classification, least-privilege access, confidentiality agreements, secure repositories, employee training and exit procedures.

Trade-secret protection may be preferable to patenting when secrecy is technically feasible and long-term, but it is weak against independent discovery or lawful reverse engineering where permitted. A product manager must weigh the benefits of public patent disclosure against the practical durability of secrecy.

6. Integrating Portfolio, Ecosystem and IP Decisions

These decisions should not be made in separate functional silos. Consider a medical-device product. Its portfolio case depends on market demand and clinical evidence. Its ecosystem may include hospitals, component suppliers, regulators and software providers. Its IP strategy may combine patents for technical inventions, trademarks for the product name, copyright for software and trade secrets for manufacturing parameters.

An integrated decision process can follow these steps:

1. Define the customer problem and strategic role of the initiative.
2. Classify it as core, adjacent or transformational, while recognising that classification may change.
3. Identify the critical uncertainties and design low-cost tests.
4. Map ecosystem participants, dependencies, incentives and power relationships.
5. Conduct an early IP landscape and freedom-to-operate assessment.
6. Decide what knowledge to build, buy, license, share or protect.
7. Establish stage gates, metrics, ownership and stop criteria.
8. Review evidence and rebalance resources as learning accumulates.

This process supports strategic flexibility. It also prevents a common failure: investing heavily in a technically impressive product before discovering that the brand is unavailable, a key patent is blocked, the required partner has incompatible incentives or customers will not adopt the solution.

7. Illustrative Case: The Connected Cold-Chain Sensor

Background

The fictional company PolarTrack manufactures temperature-monitoring equipment for pharmaceutical distributors. Its core business sells standalone sensors. Management is considering a connected sensor with cloud analytics and automated alerts.

Problem

The proposal contains three possible initiatives:

• improve the reliability and battery life of the existing sensor;
• add cloud connectivity for current pharmaceutical customers; and
• develop a broader logistics platform linking distributors, carriers and insurers.

Engineering capacity is limited, and the firm has little experience with cloud software, data governance and platform partnerships.

Analysis

The reliability project is core: it protects current revenue and uses existing capabilities. The connected sensor is adjacent: it serves existing customers but requires new software, connectivity and service capabilities. The logistics platform is transformational: it depends on multiple external participants and a new business model.

The team identifies several uncertainties. Customers may value alerts but resist subscription pricing. Connectivity may be unreliable in certain transport routes. The platform may produce little value until enough carriers participate. A competitor may hold patents covering aspects of sensor communication. The product will also process location and shipment data, creating privacy and cybersecurity responsibilities.

Approach and solution

Management adopts staged funding. First, it funds customer interviews, route testing and a prototype using a limited set of customers. The prototype is evaluated against predefined criteria: alert accuracy, battery performance, customer response, willingness to pay and security findings.

The company forms a partnership with a connectivity provider rather than building a nationwide network. The agreement specifies service levels, data ownership, security duties, termination support and responsibility for customer complaints. It retains control of the customer relationship and product roadmap.

Before public demonstrations, the company conducts an IP review. It files a patent application for a potentially novel sensor-calibration method after counsel confirms that disclosure should be controlled. It registers the PolarTrack brand, documents copyright ownership for software created by contractors, and protects certain calibration parameters as trade secrets. It also conducts an open-source licence audit and a freedom-to-operate review.

The platform initiative is not cancelled, but it remains an option rather than a full-scale programme. The company conducts a partner experiment with one distributor and one insurer to test whether shared data creates measurable value. This prevents the organisation from committing substantial resources before network participation and governance questions are answered.

Outcome

The connected sensor reaches pilot stage after demonstrating improved alert accuracy and strong interest from two customer segments. The platform experiment shows that insurers value selected data but that distributors will not share all operational information. Management therefore narrows the platform concept and establishes explicit data-sharing controls. The core reliability project continues because it improves both the existing product and the connected version.

Learning points

1. Portfolio categories clarify strategic intent but do not replace evidence.
2. Staged investment limits downside while preserving upside options.
3. Ecosystem value depends on participant incentives, not technical capability alone.
4. IP review should begin before public disclosure or major partnership commitments.
5. Data governance and cybersecurity are product responsibilities, not merely legal tasks.

8. Challenges, Ethics and Governance

Innovation portfolios can create social as well as commercial consequences. Products that use personal data, automated decisions, biometric information or connected devices require careful assessment of privacy, consent, security, accessibility and potential discrimination.

Important governance questions include:

• Is data collected necessary and proportionate to the product purpose?
• Can users understand and control important data uses?
• Has the system been tested across relevant demographic and operating conditions?
• Are automated recommendations explainable enough for the context?
• Can users appeal harmful or incorrect decisions?
• Are suppliers and partners held to equivalent security and ethical standards?
• Does the IP strategy unfairly restrict interoperability or access to essential knowledge?

AI intensifies these questions. Generative AI may accelerate discovery, coding and design, but teams must assess confidentiality, training-data provenance, hallucination, bias, copyright risk and human accountability. Product managers should not place confidential invention disclosures or personal data into public AI tools without an approved governance framework. AI-generated outputs should be reviewed for accuracy, security, licensing and ownership implications.

Regulatory obligations differ by product and jurisdiction. Relevant areas may include consumer protection, product safety, competition law, privacy and data protection, sector-specific regulation, export controls, accessibility and environmental requirements. Compliance should be treated as an ongoing design constraint rather than a final approval step.

9. Best Practices for Product Managers

A disciplined product manager should:

• maintain a visible portfolio map linked to strategy;
• distinguish evidence, assumptions and opinions;
• fund learning before scaling expenditure;
• use explicit stop, pivot and proceed criteria;
• monitor shared dependencies and concentration risk;
• map ecosystem incentives and power asymmetries;
• define partner responsibilities and exit conditions;
• involve IP and regulatory specialists early;
• preserve invention records and control confidential information;
• maintain open-source and third-party asset inventories;
• treat privacy, security, accessibility and safety as product qualities;
• review portfolio performance after launch, not only at approval; and
• reward useful learning, including well-designed failure, rather than only successful launches.

Chapter Summary

Innovation portfolio management balances current performance with future growth by combining core, adjacent and transformational initiatives. The appropriate balance depends on strategy, industry conditions, capabilities and risk tolerance rather than a universal allocation formula.

Because innovation is uncertain, staged investment, explicit assumptions, experimentation and real-option thinking are often more appropriate than a single precise forecast. Expected monetary value can support comparison when probabilities and outcomes are credible, while portfolio analysis should also consider correlation, dependencies, strategic fit and learning value.

Innovation ecosystems extend value creation beyond the firm. Platforms, complementors, network effects and partnerships can accelerate innovation, but they require clear incentives, governance, data rules and exit arrangements. Open innovation involves deliberate inbound, outbound and coupled knowledge flows, not unrestricted sharing.

Intellectual property includes patents, trademarks, copyright, trade secrets and design rights. Each protects a different asset and imposes different strategic choices. Patent ownership does not guarantee freedom to operate, open-source software carries licence obligations, and trade-secret protection depends on effective secrecy controls.

The product manager’s role is integrative: to connect portfolio choices, ecosystem relationships, IP protection, regulation, ethics and customer value. Strong practice combines strategic ambition with staged commitment, evidence-based governance and responsible innovation.

Key Terms

Innovation portfolio: The collection of innovation initiatives managed as an interrelated set.

Core innovation: Improvement or protection of the existing business, customers and capabilities.

Adjacent innovation: Expansion into related markets, technologies, channels or customer uses.

Transformational innovation: Innovation that creates substantially new markets, capabilities or business models.

Stage gate: A formal decision point at which evidence is reviewed before further investment.

Real option: An opportunity, but not an obligation, to make a future investment after learning more.

Expected monetary value: Probability-weighted value of possible outcomes minus relevant cost.

Portfolio risk: The possibility that the combined set of initiatives fails to achieve its objectives.

Ecosystem: A network of interdependent participants that contribute to value creation and capture.

Platform: A foundation, interface or rule system that enables interactions or complementary offerings.

Network effect: A change in product value caused by a change in participation.

Open innovation: Purposeful management of knowledge flows across organisational boundaries.

Inbound innovation: Use or acquisition of knowledge from external sources.

Outbound innovation: External exploitation, licensing or transfer of internal knowledge.

Patent: A time-limited legal right relating to a qualifying invention, subject to jurisdictional rules.

Trademark: A sign that distinguishes the goods or services of one source from another.

Copyright: Protection for original expression such as software, text, graphics or audiovisual work.

Trade secret: Valuable confidential information protected through secrecy measures.

Freedom to operate: Assessment of whether commercial activity risks infringing relevant third-party rights.

Open-source licence: Legal terms governing permitted use, modification and distribution of open-source material.

Review Questions

Short Answer Questions

1. What distinguishes core, adjacent and transformational innovation?
2. Why is staged investment useful for uncertain innovation initiatives?
3. What is the difference between an ecosystem and a conventional supply chain?
4. Why does a patent not automatically provide freedom to operate?
5. Identify two controls used to protect trade secrets.

Long Answer Questions

1. Explain how an organisation can balance core, adjacent and transformational initiatives. Discuss why fixed allocation ratios may be misleading.
2. Describe how stage gates and real-option thinking improve innovation resource allocation.
3. Compare patents, trademarks, copyright and trade secrets from a product-management perspective.
4. Analyse the governance requirements of a strategic technology partnership.
5. Explain how open innovation can accelerate product development while creating legal and strategic risks.

Analytical / Application Questions

1. A firm has strong revenue from an established product but faces a rapidly changing technology market. Design a portfolio approach and justify the balance of initiatives.
2. A start-up wants to publish its technical architecture, use open-source software and partner with a large platform. Identify the portfolio, ecosystem, IP and governance questions it should resolve before launch.
3. Using the PolarTrack case, recommend which initiative should receive the next major investment and specify the evidence and stage-gate criteria required before approval.

Multiple Choice Questions with Answers

Question 1

Which initiative is most clearly classified as transformational innovation?

A. Improving the battery life of an existing product

B. Adding a minor feature for current customers

C. Entering a new market through a fundamentally different business model

D. Reducing manufacturing defects in the current product

Correct Answer: C. Entering a new market through a fundamentally different business model

Question 2

What is the main purpose of staged investment in innovation?

A. To ensure every project receives equal funding

B. To delay all commercial decisions indefinitely

C. To learn progressively before making larger commitments

D. To eliminate the need for customer research

Correct Answer: C. To learn progressively before making larger commitments

Question 3

In the expression EMV = ∑(pᵢ × Vᵢ) − C, what does pᵢ represent?

A. The investment cost

B. The probability of outcome i

C. The total portfolio variance

D. The product price

Correct Answer: B. The probability of outcome i

Question 4

Which situation illustrates concentration risk in an innovation portfolio?

A. Projects serving unrelated customer segments

B. Projects using different technologies and suppliers

C. Several projects depending on the same uncertain supplier

D. A portfolio containing both core and transformational initiatives

Correct Answer: C. Several projects depending on the same uncertain supplier

Question 5

What is an indirect network effect?

A. Users benefit from improved internal accounting

B. One participant group attracts complements that benefit another group

C. A product becomes cheaper because its materials cost less

D. A project is completed earlier than planned

Correct Answer: B. One participant group attracts complements that benefit another group

Question 6

Which activity is an example of inbound open innovation?

A. Licensing an external technology for use in a product

B. Selling an internal patent to another organisation

C. Publishing all confidential product information

D. Stopping collaboration with suppliers

Correct Answer: A. Licensing an external technology for use in a product

Question 7

Which statement about patents is correct?

A. A patent always guarantees freedom to operate

B. A patent protects every business idea automatically

C. Patent requirements and rights are subject to jurisdictional rules

D. A patent never requires disclosure of technical information

Correct Answer: C. Patent requirements and rights are subject to jurisdictional rules

Question 8

Which IP form depends most directly on maintaining confidentiality?

A. Trademark

B. Trade secret

C. Registered design

D. Copyright

Correct Answer: B. Trade secret

Question 9

Why should open-source software dependencies be inventoried?

A. Open-source software has no legal conditions

B. The inventory helps identify licence and security obligations

C. It guarantees that the software is free of vulnerabilities

D. It replaces the need for software testing

Correct Answer: B. The inventory helps identify licence and security obligations

Question 10

Which is the best example of a portfolio governance control?

A. Continuing every project until its original budget is exhausted

B. Using predefined criteria to proceed, pivot or stop an initiative

C. Allocating all resources to the highest-visibility project

D. Evaluating projects only after commercial failure

Correct Answer: B. Using predefined criteria to proceed, pivot or stop an initiative