Subscribe
for Updates
Sign up for our newsletter to get more information about ISPMA, our people, events, and initiatives.
Glossary
A measure of whether a brand is correctly identified by potential customers. Typically expressed as a percentage of a target market. There are many different approaches to measuring this statistic, but it typically means that a customer can respond to a brand after viewing its logo or packaging.
A decision support and planning approach for comparing the costs and benefits associated with a proposed initiative.
Description of the rationale of how an organization creates, delivers and captures value by interacting with suppliers, employees, customers and partners.
A basic pattern of doing business. Available archetypes are creator, distributor, lessor and broker.
A model that describes the rise, duration, and decline of a category of product or service in terms of total revenue or number of users.
A sequence of intermediaries through which goods and services as well as the compensation are transferred between a company and its customers.
Service and delivery model for the provisioning of IT components through the internet based on an architecture that enables a high level of scalability and reliability.
The entity of a company which is responsible for the definition and communication of strategy, vision and mission to the rest of the company. Also, it has the managerial supervision of the different departments, including product management.
A competitor of company A is another company that sells products and/or services to A's target market (or a subset thereof) which are similar to A's products and/or services.
Business, project or design decisions taken in advance to ensure the solution fits business, managerial and contextual concerns. These decisions limit the solution space.
Automated push of software into the production environment or delivery to customers.
Combination of continuous integration and continuous delivery to automatically deliver code changes to customers.
Automated integration, build, and test of software in the development environment.
Metric for the number of customers who have completed a transaction on a web site divided by the total number of website visitors.
A form of intellectual property right that gives the author of an original work exclusive rights for publishing, distributing and adapting the work.
The basic long-term goals of an enterprise and the courses of action for carrying out these goals.
Metric for the average amount of money invested to acquire a new lead.
The types and relative proportions of fixed and variable costs connected to a business model.
A subset of existing and/or potential customers targeted by a common value proposition.
A party that receives or consumes products and/or services from a second party.
A description of the mechanisms in which a product is made available to customers. Examples: Licensed product vs. Software-as-a-Service (SaaS).
Tight cooperation of Development and Operations with the objective to significantly increase the speed and quality of software deployment.
Software parts of software-intensive systems that are not marketed and priced as separate entities.
A statement that identifies what a product or process must accomplish to produce required behavior and/or results.
Describes the activities, deliverables, budgets, dependencies, and schedules for a business function to members of a cross-functional product team, on behalf of a product.
The discipline of managing processes related to innovation. Innovation management allows the organization to respond to external or internal opportunities, and use its creative efforts to introduce new ideas, processes or products.
Exclusive rights that are granted by law to the owner(s) of intangible assets that result from creations of the mind, such as inventions, literary and artistic works, and symbols, names, and images used in commerce.
A specific numerical measure that represents the progress towards a strategic goal, objective, output, activity, or further input.
A technique for understanding which product features will help drive customer satisfaction.
A set of rights concerning a licensor's intellectual property which a licensor grants to a licensee.
A legal document that describes a license and the related financial conditions.
(a) The area of economic activity in which buyers and sellers of goods and services come together, and the forces of supply and demand affect prices.
(b) A geographic area of demand for commodities or services.
(c) A specified category of potential buyers.
Analysis of all aspects relevant for a particular market in its current state and over the strategic time frame including market structure, competitors, market shares, customer preferences and behavior.
Division of a market into sub-sets called market segments that are distinct from each other, and homogeneous with regard to certain criteria.
Percentage of revenue or volume that a particular player makes in a particular market or market segment in relation to the market's total revenue or volume.
(a) The activities that are involved in making people aware of a company's products and making sure that the products are available to be bought.
(b) The organizational and/or functional unit in an organization that is responsible for (a).
Set of marketing activities that concerns executing the marketing strategy to create communication deliverables including advertising, branding, graphic design, promotion, publicity, public relations and more.
Organizational structure in which individuals report to more than one person
The minimum feature set of a new product that is derived through a learning phase and that some customers are willing to pay for in the first release.
Definition of the present activities or purpose of an organization by saying what it does for whom and how.
Method to measure customer loyalty by asking a single 0-10 scale question: How likely is it that you would recommend $BRAND$ to a friend or colleague?. Your promoter score is the percentage of customers who answer 9 or 10 subtracted by those who answer 0-6.
A requirement that pertains to a quality concern that is not covered by functional requirements. Also referred to as -> Quality requirement
Software that can be freely accessed, used, changed, and shared (in modified or unmodified form) by anyone. Open source software is made by one or more people, and distributed under licenses that comply with the Open Source Definition.
A party who joins one or more other parties based on an agreement that defines the terms and conditions of the relationship (partnership).
A patent is an exclusive intellectual property right for an invention granted to the inventor for a defined timeframe by an authorized body of a sovereign state. The right is granted for the territory of that sovereign state. It is the right to exclude others from making, using, offering for sale, or selling the invention. The types of inventions covered by patent law can be different from state to state.
Continuous tracking and analysis of selected KPIs relevant for business success, plus timely action taking if needed
All activities required to set, communicate, and negotiate prices in a convincing way.
All activities to analyze, plan and execute changes in processes with the goal to optimize the defined process KPIs.
An abstract description of one or more processes. A process model typically describes a process as a sequence of activities and the involved roles and responsibilities.
A combination of goods and services, which a supplier/development organization combines in support of its commercial interests to transfer defined rights to a customer.
Analysis of all business aspects relevant for a particular product in its current state and over the strategic time frame including KPIs like revenue, revenue distribution, footprints, and market shares.
Describes the evolution of a product from its conception to its discontinuance and market withdrawal.
The management of the business and technical aspects of a software product with regard to its position in its life cycle.
A set of products based on a common platform with defined (static or dynamic) variability tailored to different markets and users.
(a) The discipline which governs a product along the product life cycle with the objective to generate the biggest possible value to the business.
(b) The organizational and/or functional unit in an organization that is responsible for (a).
A person responsible for -> Product Management in an organization. An organization can have multiple product managers.
Applying -> Marketing to a -> Product. Translates strategic marketing decisions to the product level.
Set of products or services offered by a company.
The activity of making decisions about investments in the products included in the product portfolio over the strategic timeframe.
A document that provides features or themes of the product releases to come over the strategic timeframe. The creation of a roadmap is influenced by the product strategy designed for this product.
Abstract description of the functional and quality characteristics of the product.
(a) Combination of the strategic goals and measures for the product, i.e. aspects that need to be defined and managed for the strategic timeframe of the product. See corresponding column in ISPMA's SPM Framework.
(b) Consistent documentation containing the following items and their evolution during the strategic timeframe: Product vision, Product definition, Target market, Potential segments, Delivery model, Product positioning, Sourcing, Business plan, Roadmap
Conceptual description of what the future product will be at the end of the strategic timeframe, i.e. high-level descriptions of a product concept and a corresponding business model.
Overview of the relationship between product releases (product evolvement) and successive technology generations.
A requirement that pertains to a quality concern that is not covered by functional requirements. Also referred to as -> Non-functional requirement.
(a) Product release: an instance of the product that is delivered to customers, and maintained as part of product maintenance.
(b) Pre-release: a result of development activity that is testable, e.g. the result of a sprint in Scrum.
The result of selecting the requirements to be implemented in the next release. Usually this result is documented including statements about the relationship between the selected requirements and strategic objectives.
The process of selecting the requirements for the next release.
(a) A condition or capability needed to solve a problem or achieve an objective.
(b) A condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed document.
(c) A documented representation of a condition or capability as in definition (a) or (b). Three different types of requirements are distinguished: functional requirements, quality requirements and constraints.
(a) The disciplined and systematic approach (i.e., "engineering") for elicitation, documentation, analysis, agreement, verification, and management of requirements while considering market, technical, and economic goals.
(b) Activity within systems engineering and software engineering.
Planning, executing, monitoring, and controlling any or all of the work associated with requirements elicitation and collaboration, requirements analysis and design, and requirements life cycle management.
The activity during which the most important requirements for the product are determined. As priorities change over time this activity is often targeted at the next release of the product.
An activity for early and fast acceptance/rejection of requirements.
The efficient and effective development of an organization's resources. In the software business resources are primarily people, existing software and systems that the software runs on or is developed on.
Metric for the average amount of revenue divided by the related cost.
Money collected by an organization in return for products and/or services.
Set of all -> revenue streams of a company.
Describes generation of compensation over time for a product, service or company as revenue or in non-monetary ways. Non-monetary aspects may be data or services in return.
The identification, assessment, and prioritization of risks followed by coordinated and economical application of resources to minimize, monitor, and control the probability and/or impact of unfortunate and/or undesired events.
Description of a real or imagined situation under a defined set of assumptions.
(a) Useful labor that does not produce a tangible commodity (as in "professional services").
(b) A provision for maintenance and repair (as in "software maintenance service").
(c) The technical provision of a function through a software component that can be accessed by another software component, often over a network and executed on a remote server (as in "web services" or "Software-as-a-Service").
Agreement between two or more parties about the target values a service-giving party has to achieve for the defined measures that are relevant for quality and cost of the service.
A network of people and/or companies that forms around a software vendor or a product or product platform. The relationships in this network have the goal to achieve benefits for all participants and can be formalized or not. Formalized relationships are called partnerships.
A system where a significant part of the value originates from software.
A product whose primary component is software.
A group of software products which for marketing reasons are marketed as belonging together under a common family name.
A set of software-intensive systems that share a common, managed set of features satisfying the specific needs of a particular market segment or mission, and that are developed from a common set of core assets in a prescribed way.
The management of a software product or the software components of a software-intensive product over its life cycle with the objective of generating the biggest possible value to the business.
Competence model that guides product management in process improvement.
Product manager of a software product or the software components of a software-intensive product.
A decomposition of the value concept that details value of a software intensive product from the main areas of financial, customer, internal business process, and innovation and learning perspectives.
A delivery model for software that is used in cloud computing.
The process of ensuring that all required resources are available when they are needed.
A person, group, or organization that has direct or indirect stake in an organization because it can affect or be affected by the organization's actions, objectives, and policies.
The way a firm effectively differentiates itself from its competitors by effectively segmenting the market, selecting the appropriate targets and consistently developing a better value positioning to customers than its competitors.
A set of market segments to which a particular product is marketed to.
Something which has economic value to a business because it is not generally known or easily discoverable by observation such as an algorithm and for which efforts have been made to maintain secrecy.
A distinctive identifier, such as a phrase, word or sign, for certain products or services as those produced or provided by a specific person or enterprise. Protection of trademarks depends on local law.
A person or thing that uses something i.e. products or services.
Every aspect of the usersÕ interactions with a software product or component with the purpose of shaping the user's behaviors, attitudes, and emotions about that product or component.
Description of the benefits customers can expect from one product, or from the products and services of a company.
A group of individuals who work together across time, space and organizational boundaries with links strengthened by webs of communication technology.