ISPMA (International Software Produkt Manager)

Diese Lernkartei dient zum Aufbau und der Überprüfung des Wissens zur Erreichung des Foundation Zertifikat ISPMA.

0.0 (0)

Kartei Details

Karten	50
Lernende	13
Sprache	English
Kategorie	Informatik
Stufe	Universität
Erstellt / Aktualisiert	18.04.2018 / 21.03.2023
Weblink	https://card2brain.ch/box/20180418_ispma_international_software_produkt_manager
Einbinden	<iframe src="https://card2brain.ch/box/20180418_ispma_international_software_produkt_manager/embed" width="780" height="150" scrolling="no" frameborder="0"></iframe>

Kartenliste

Lernen

Which of the following elements are part of a product roadmap?

Timescale

Releases and versions

Release themes and main features

Target place

Product dependencies

The syllabus is the basis for consistent training, learning, and examination of software product management and provides ...

informal explanations to detail the educational objectives.

guidance for such specialization as domain-specific details.

explicitly phrased educational objectives for each chapter.

informal references to literature (without limiting the interpretation of the syllabus to this literature only).

informal explanations about excellent leadership.

The syllabus ...

prescribe the specific form and approach of learning.

corresponds to a three-day industry course.

can also be administered with other forms of teaching or learning, such as self-learning supplemented by coaching or courses at universities or universities of applied sciences.

A list of training providers can be found on the ISPMA web site ...

www.ispma.com

www.ispma.info

www.ispma.org

www.ispma.tv

A software product manager is responsible ...

only to develop the software product, but not with pricing.

to managing software with the objective to achieve sustainable success over the life cycle of the software product.

to manage a broad set of product-related activities as shown in the ISPMA SPM Framework (Figure 1).

for the business responsibility across different versions, variants and associated services of a product.

Software Product Management Framework includes ...

Business Case and Costing

Sales acquisition

Product Life-Cycle Management

Sourcing

To handle the product strategy, you have to ...

know the Strategic Pricing Pyramid

know intellectual property protection mechanisms

understand the business aspects and their interdependences.

understand the need for tissue viability risk assessment.

dynamically leverage existing user-centric process improvements.

The product strategy describes how the product is supposed to evolve over this strategic timeframe and should include the following items:

Delivery model and Service Strategy

Sourcing

Frictionless systems

Product definition

E-Services

The business aspects of the Business Model Canvas refer to the following subjects

Risk management

Infrastructurs

Definition and selection of relevant business measures

Business case

Benefits

The strategic Pricing Pyramid includes following levels:

Value recources

Value Creation

Price & Value Communication

Price Policy

Price Level

The structural constituents of software ecosystems are

boundaries

stakeholders

requirement

relationships

artifacts

A contract, so-called “terms and conditions” which describe the generally applicable legal terms, including:

Type of charges

Opportunities

Guarantee and Warranty

Scope of the license or service

Maintenance provisions

There are four fundamental legal constructs for the protection of intellectual property:

Trademark

Intellectual property

Trade Secret

Patent

For a propre product plannig, you need to

know the inquiry cycle with elicitation, triage, analysis, selection and validation.

understand the differences between product, project, and customer RE.

know the basic elements of a roadmap.

understand the changes in product management’s focus from phase to phase.

know the inquiry cycle with elicitation, triage, analysis, selection and validation.

Three requirement types of Requirements engineering (RE) can be distinguished:

Customer requirements which express individual customer needs.

Requirements engineering involves no communication between the project team members and stakeholders.

Project requirements which further refine product requirements that are selected for a particular release or project and require implementation in software code.

Product requirements which address no individual customer, but rather one or more markets consisting of any number of customers that may have similar needs, but with high variability.

Requirements elicitation is the systematic application of methods such as

artifact analysis

interviews

surveys

prototyping

observation

Requirements analysis aims at matching the elicited information with appropriate solution concepts bymodeling,

applying specification

modeling

implementation

prototyping methods

validation

A product organization needs a dedicated process to deal with requirements in a systematic way, the „requirements inquiry cycle”, which combines

analysis

requirements elicitation

promotion

triage

validation

Examples of life cycle phase models that might be used are:

Selected: the requirement has been selected for implementation with a given priority.

Tested: the necessary tests have been carried out in order to ensure an adequate level of quality.

Used: the requirement is already implemented and tested.

Approved: the requirement is approved and ready to be analyzed.

New: the initial state of a requirement.

Non-functional requirements can be specified

operationally

quantitatively

competitivly

qualitatively

independetly

Dependent on the type and amount of change, releases are called

minor release

update release

serivce release

upsell release

major release

A product roadmap usually has the following basic elements:

Product dependencies

Lifetime impacts

Release themes and main features

Target markets

Timescale

Product Life Cycle Management has usualy ... phases.

Conception and creation, the first phase of the product life cycle management has following focus areas

functionality

positioning

innovation

investment

Market Introduction, the second phase of the product life cycle management has following focus areas

market share

revitalization

launch

cost reduction

Growth, the third phase of the product life cycle management has following focus areas

functionality

revitalization

positioning

market share

The first phase of the Product Life Cicle Management is Conception and creation. Which following phases does not belong to the PLCM?

Growth

Maturity

Analysis

Withdrawal

Scrums

One of the central tasks of SPM is

to optimize the cooperation of all other units with respect to product-related goals.

successful negotiations in case of conflicts of interest.

efficiently utilize excellent catalysts for change.

orchestrate timely execution of localization.

The product manager’s orchestration responsibility includes

appropriately drive open-source portals.

the alignment of product strategies and plans.

availability of correct and timely measurements.

research and innovation initiatives for both functional and technical innovations.

the management of product-related services as part of the product offering,

Typical orchestration challenges are

between product manager and sales and distribution unit.

between product manager and marketing unit.

between sales manager and clients.

between product managers of a product family.

Strategies for avoiding/resolving conflicts:

Separate contract giver (product manager) and contract taker (development unit).

Ensure a clear definition and separations of concerns, responsibilities and competencies, as well as clear definition of accountability.

Define rapidiously target client-centered strategic theme areas.

Define contracting offers and agreements for system integration and outsourcing.

Separate contract giver (product manager) and contract taker (development unit).

The typical technical support structure is

Technical Maintenance

Help Desk

Level design support

Change Team (typically in or with Development)

Marketing support means providing help to Marketing. It may include

continually streamline agile best practices.

documentation and tracking of marketing activities and their results.

orchestrate integrated applications.

the production and distribution of marketing material.

Sales support means providing help to sales representatives and channels. It may include

and execution of sales events.

intrinsically exploit compelling solutions.

sales-related customer inbound and outbound communication.

and tracking of sales activities and their results.

provision of marketing material on request.

The orchestration responsibility does apply to

Controlling

Research

Human Resources

Finance

Channels

Service provisioning means

taking corrective actions when measurements deviate from plan.

the execution of the service plan.

interactively extend impactful outsourcing.

tracking of the relevant measurements.

Preparation of service planning includes

forecast of demand.

skills development.

development of a technical basis.

resource management.

empowered benefits.

Product-related services can include

innovation

education

operations

installation

The product manager’s orchestration responsibility may include

positioning of a product in the sales plan

conveniently drive enterprise resources

in particular the incentives plan

tracking of plan execution

in product-specific commitments to customers

Operational distribution means ensuring

smooth order and distribution processes.

supply (in case of physical distribution).

smooth and correct billing/payment.

stable and easy online order and distribution.

smooth handling of customers prospects.

Kartenliste

Lernen

ISPMA (International Software Produkt Manager)

Lernkarteien erstellen oder kopieren

Lernkarteien erstellen oder kopieren

Melde dich an, um alle Karten zu sehen.

SWITCHaai

Office 365

Edulog

Apple ID

Google