No.	ISPMA naming	Different naming used by various sources		Explanation	Changed name
1	Market analysis	- User research (Springer & Miler, 2018) - Product discovery (product ideation) (Tkalich et al., 2022) - Segment markets (Haines, 2014) - Define target customers (buyer/user personas) (Haines, 2014) - Assess customer needs (Haines, 2014) - Track industry trends & reassess after launch (Haines, 2014) - Evaluate competitors & reassess after launch (Haines, 2014) - Uncover opportunities (Haines, 2014)		ISPMA synthesis well on all these concepts and comprises under the Market Analysis category.	Market Analysis
2	-	- Proposing solutions (Springer & Miler, 2018) - Idea evaluation (mock-up, working prototype) (Tkalich et al., 2022) - Evaluate prototypes (Haines, 2014) - Requirements identification (Bekkers et al., 2010)		ISPMA consolidates solutioning with the Product Definition category. The Geracie & Eppinger (2013) describes well to identify solution candidate via prototype validation, then create product definition. Hence, identify solution is separated out as an important activity to highlight.	Identify Solution
3	Customer insight	- Interacts with the customer (Tkalich et al., 2022) - Gathering user feedback (Tkalich et al., 2022)		ISPMA naming fits well.	Customer Insight
4	Positioning & product definition	- Proposing solutions (Springer & Miler, 2018) - Strategic vision creation (Tkalich et al., 2022) - Requirements identification (Bekkers et al., 2010) - Product vision creation (Maglyas et al., 2017) - Product SWOT analysis (Haines, 2014) - Articulate future vision (Haines, 2014) - Prioritize opportunities and product opportunity statement (Haines, 2014) - Shape value proposition (Haines, 2014) - Assert competitive positioning (Haines, 2014) - Compare competitor products (Haines, 2014)		ISPMA naming fits well. However, Maglyas et al. (2017) proposed this category to change as vision creation. Here, both the terms are used for a better clarity and product vision is used instead of only vision to separate out from the company vision.	Positioning & product definition or product vision creation
5	Ecosystem management	- Stakeholder management (Springer & Miler, 2018) - Engaging internal stakeholders (Tkalich et al., 2022) - Leverage cross-functional team (Haines, 2014)		PMs collaborate with them cross-functional teams instead of managing them. Hence, rename the activity to Cross-functional collaboration.	Cross-functional collaboration
6	Sourcing	- Make or buy decision (Bekkers et al., 2010) - Conduct make vs. buy analysis (Haines, 2014) - Acquiring resources (Tkalich et al., 2022)		ISPMA naming and definition consolidates well on the resource planning and make vs. buy decision regards to software components.	No change
7	Financial management	- Responsible for the profitability of the product (Tkalich et al., 2022) - Develop business case & reassess throughout the life cycle (Haines, 2014) - Drive forecast (Haines, 2014) - Analyze profit and loss (Haines, 2014) - Partnering & contracting (pricing) (Bekkers et al., 2010) - Refine value-based pricing (Haines, 2014)		For a simplicity, pricing is consolidated into the financial management category, and it is named as financial analysis.	Financial analysis
8	Legal and IPR management	- Project compliance (Tkalich et al., 2022) - Partnering and contracting (service level agreements, intellectual property management) (Bekkers et al., 2010) - Secure regulatory approval (Haines, 2014)		The legal, IPR, and compliance related activities are consolidated into the single category as they are related.	Legal and compliance management
9	Performance & risk management	- Assessing risk (Tkalich et al., 2022) - Product monitoring and adjustments (Tkalich et al., 2022) - KPIs and reporting (Haines, 2014) - Establish future metrics & evaluate after launch (Haines, 2014) - Organize post-launch audit & retrospective reviews (Haines, 2014) - Assess past and current data (Haines, 2014) - Track customer satisfaction (Haines, 2014)		Performance might be confusing with system performance, so to be specific, product performance is used. Risk management applies to entire product life cycle, so it is removed from the naming.	Product performance management
10	Product life cycle management	- Process lead (Tkalich et al., 2022) - Product life cycle (Maglyas et al., 2017) (Bekkers et al., 2010) - Determine life cycle state (Haines, 2014)		Universally accepted name.	No change
11	Roadmapping	- Prioritizing projects or tasks (Springer & Miler, 2018) - Gathers and prioritizes features (Tkalich et al., 2022) - Presents a prioritized product backlog (Tkalich et al., 2022) - Prioritize inter-team requirements (Haines, 2014) - Requirements prioritization (Bekkers et al., 2010) - Product roadmapping (Bekkers et al., 2010) - Strategic planning (Maglyas et al., 2017) - Integrate product roadmap (Haines, 2014)		Universally Accepted Naming for a PM.	No change
12	Release planning	- Define goals (Springer & Miler, 2018) - Communicate business needs to development team (Tkalich et al., 2022) - Decides release dates and content (Tkalich et al., 2022) - Release definition (Bekkers et al., 2010) - Release definition validation (Bekkers et al., 2010) - Participating in sprint planning and reviews (Kittlaus, 2012) - Collaboration with product management on release planning (Kittlaus, 2012) - Develop release & sprint plans (Haines, 2014) - Fine-tune release plans (Haines, 2014)		Universally accepted naming for a PM.	No change
13	Product requirements engineering	- Analysis of requirements (Springer & Miler, 2018) - Communicates the customer’s business needs to the development team (Haines, 2014) - Requirements gathering (Bekkers et al., 2010) - Requirements organizing (Bekkers et al., 2010) - Managing the backlog (Kittlaus, 2012) - Compose product requirement/write user stories (Haines, 2014)		ISPMA naming is generally accepted but more traditional. Geracie & Eppinger (2013) defines well with respect to Agile method (i.e., prioritized product backlog).	Product requirements engineering or prioritized product backlog (in Agile)
14	Development execution	- Cooperation with the development team (Springer & Miler, 2018) - Individuals follow up (Tkalich et al., 2022) - Supporting team delivery (Tkalich et al., 2022) - Product development (Maglyas et al., 2017) - Scope change management (Haines, 2014) (Bekkers et al., 2010) - Guide development (Haines, 2014)		Many sources have confused the generic product development vs. what the PM is responsible for. The development execution is a stage of product life cycle and not the Product Manager responsibility.	Supporting the product engineering team
15	Detailed requirements engineering	- Tactical planning (Kittlaus, 2012) - JIT story elaboration & acceptance (Kittlaus, 2012) - Update product backlog (Haines, 2014)		ISPMA naming looks universal comprising of all these activities. However, missing Agile specific naming in or clause.	Detailed requirements engineering or define user stories, acceptance criteria, and prioritized backlog (in Agile)
16	Quality management	- Build validation (Bekkers et al., 2010)		Geracie & Eppinger (2013) naming looks more specific as PM’s responsibility. ISPMA naming is broader category.	Product verification
17	Product launch		- Launch pilot version of the product (Haines, 2014) - Launch preparation (Haines, 2014) (Bekkers et al., 2010) - Training (Bekkers et al., 2010) - Orchestrate product launch (Haines, 2014)	PMs are not responsible for product launch itself. However, they are responsible for orchestrating the launch.	Orchestrate product launch
18	Channel preparation value communication service planning and preparation		- Conduct sales training (Haines, 2014) - Coordinate product messaging (Haines, 2014) - Prepare service organization (Haines, 2014) - Product support (Jansen et al., 2011)	There were various activities related to the operations and support readiness which are consolidated into the single category instead of having many.	Operations readiness
19	-		- Product end-of-life (Jansen et al., 2011) - Discontinue products (Haines, 2014)	ISPMA framework did define any category for End-of-life, so the new category is created.	End-of-life plan