Keywords for sutdy? https://gemini.google.com/app/fed8a5d69cdda0f0
☐ Alternativas de keyword para Product Management https://gemini.google.com/app/a49cdbfc156adf91
- Revisar a lista de busca, incluir PRD:
- https://elicit.com/review/e1e45fe6-cf63-4be1-95b5-aa99381749f1
Capturado perdido: Requirements Elicitation Requirements Gathering Questionnaire Design Stakeholder Needs (and addressing stakeholder needs) Problem-Driven Approach Functional Requirements (FRs) Non-Functional Requirements (NFRs) Product Definition User Needs System Requirements Problem/Solution (as a dimension of RE)
“product manager” OR “product owner” OR (“founder or co-founder”) “Generative AI” OR ”artificial intelligence” “Market Analysis”,“Product Analysis” ”revenue” OR ”sales” “startup”
”business*” OR ”industry” OR ”market” OR ”customer” OR ”user”
(“Market Analysis” OR Product Analysis) OR (“Product Positioning” OR “Product Definition”) OR (“Delivery Model” OR “Service Strategy”) OR (“Performnace Management” OR “Risk Management”) OR (“Customer Insight” OR “Product Requirements”) OR (“Life Cycle” OR “Life-cycle” OR “Lifecycle”)
(“Generative Artificial Intelligence” OR “Generative AI” OR “Gen AI” OR “GenAI”) AND (“product ideation” OR “product prototyping” OR “user feedback” OR “product discovey” ) AND “enterprise” AND “product manager”
(“product manager” OR “product owner” OR “product team”) AND (“Generative Artificial Intelligence” OR “Gen AI” OR “GenAI”)
Thoughts
- How to defined that is software related? Maybe in the context, Digitization, Software…
- Narrowing data - Internal ou external the function - Activities directly linked to product management - Ex. Increase collaboration in general in the organization.
- Product or Product Manager? Product, because it can go beyond the “Role”
Direct Searches
OR “AI in Product Management” OR “AI for Product Managers”
SIPOC Variations
Population
Population
In software engineering experiments, the populations might be any of the following:
• A specific software engineering role e.g. testers, managers.
• A category of software engineer, e.g. a novice or experienced engineer.
• An application area e.g. IT systems, command and control systems.
• An industry group such as Telecommunications companies, or Small IT
companies.
A question may refer to very specific population groups e.g. novice testers, or
experienced software architects working on IT systems. In medicine the populations are defined in order to reduce the number of prospective primary studies. In software engineering far fewer primary studies are undertaken, thus, we may need to avoid any restriction on the population until we come to consider the practical implications of the systematic review.
Ref: B. Kitchenham and S. Charters, “Guidelines for performing Systematic
Deveria ser “Role” ou “Product Management”
Role “product manager” OR “product owner” OR “product team” OR “Product organization”
OR (“founder or co-founder”) ← Think not
Intervention
The intervention is the software methodology/tool/technology/procedure that
addresses a specific issue, for example, technologies to perform specific tasks such as requirements specification, system testing, or software cost estimation.
Ref: B. Kitchenham and S. Charters, “Guidelines for performing Systematic
“Generative Artificial Intelligence” OR “Generative AI” OR “Gen AI” OR “GenAI”
Should use verbs?
AI-driven customer insight “AI-Driven” OR “AI Driven”
Should be generic?
“artificial intelligence”
Should include LLMs?
No.
“Large Language Models” OR “LLMs” OR
-
Generative AI is the broader category. It refers to any AI that can create new content, whether that’s text, images, music, code, etc.
-
LLMs are a specific type of Generative AI. They focus on generating text and are incredibly powerful for language-related tasks.
Comparison
This is the software engineering methodology/tool/technology/procedure with which
the intervention is being compared. When the comparison technology is the
conventional or commonly-used technology, it is often referred to as the “control”
treatment. The control situation must be adequately described. In particular “not using
the intervention” is inadequate as a description of the control treatment. Software
engineering techniques usually require training. If you compare people using a
technique with people not using a technique, the effect of the technique is confounded
with the effect of training. That is, any effect might be due to providing training not
the specific technique. This is a particular problem if the participants are students.
Ref: B. Kitchenham and S. Charters, “Guidelines for performing Systematic
In principle, the results are not two much… probably the limitation is the population. Could maybe make some tries
Defining the Product
“product ideation” OR “product prototyping” OR “user feedback” OR “product discovey”
“Design Process”
“Product Discovery” OR “Product Innovation” OR “User Research” OR “Design Thinking” OR “Synthetic Data” OR “AI-driven Insights” OR “Human-Computer Interaction” OR “Creativity Support Tools.”
ISPMA based query: “Market Analysis”,“Product Analysis” ”revenue” OR ”sales” “startup” (“Market Analysis” OR Product Analysis) OR (“Product Positioning” OR “Product Definition”) OR (“Delivery Model” OR “Service Strategy”) OR (“Performance Management” OR “Risk Management”) OR (“Customer Insight” OR “Product Requirements”) OR (“Life Cycle” OR “Life-cycle” OR “Lifecycle”)
Outcomes
Outcomes should relate to factors of importance to practitioners such as improved
reliability, reduced production costs, and reduced time to market. All relevant
11outcomes should be specified. For example, in some cases we require interventions
that improve some aspect of software production without affecting another e.g.
improved reliability with no increase in cost.
A particular problem for software engineering experiments is the widespread use of
surrogate measures for example, defects found during system testing as a surrogate
for quality, or coupling measures for design quality. Studies that use surrogate
measures may be misleading and conclusions based on such studies may be less
robust.
Ref: B. Kitchenham and S. Charters, “Guidelines for performing Systematic
(”revenue” OR ”sales” OR “margin”) OR (“productivity”) OR (“risk”) OR (“value”) OR (“quality”) OR (""effectiveness” OR “efficiency”)
Context
For Software Engineering, this is the context in which the comparison takes place
(e.g. academia or industry), the participants taking part in the study (e.g. practitioners,
academics, consultants, students), and the tasks being performed (e.g. small scale,
large scale). Many software experiments take place in academia using student
participants and small scale tasks. Such experiments are unlikely to be representative
of what might occur with practitioners working in industry. Some systematic reviews
might choose to exclude such experiments although in software engineering, these
may be the only type of studies available.
Ref: B. Kitchenham and S. Charters, “Guidelines for performing Systematic
“software” “Product Management”
SaaS?
“enterprise” ”business*” OR ”industry” OR ”market” OR ”customer” OR ”user”
New Product, Existing Product? Does it matters?
Perspective from Jan
Strategic digital product management: Nine approaches - ScienceDirect
P - Population/Problem:
- Project Managers
- Project Management Professionals
- PMs
- Project Teams
- Digital Project Managers
- IT Project Managers (if focusing on IT projects)
- Software Project Managers (if focusing on software projects)
I - Intervention/Interest:
- Digitalization
- Digital Transformation
- Digital Technologies
- Industry 4.0
- Automation
- Artificial Intelligence (AI)
- Machine Learning (ML)
- Big Data
- Cloud Computing
- Agile Methodologies (often associated with digital transformation)
- DevOps (often associated with digital transformation)
- Emerging Technologies
- Technological Change
- Digital Disruption
C - Comparison/Control (Often less relevant for this type of research question, but consider if applicable):
- Traditional Project Management (if comparing to pre-digital practices)
- Non-digital Project Management (if comparing to projects without significant digital influence)
- Specific project management methodologies (e.g., Waterfall vs. Agile in a digital context)
O - Outcome:
- Role of Project Manager
- Changing Roles
- Evolving Roles
- Responsibilities of PMs
- Skills of PMs
- Competencies of PMs
- Impact of Digitalization on PMs
- Challenges for PMs
- Opportunities for PMs
- Future of Project Management
- Project Success (as influenced by the PM’s role in digital contexts)
- Project Performance (as influenced by the PM’s role in digital contexts)
C - Context (Consider if you have specific industry focuses):
- Construction Industry
- Healthcare Industry
- Manufacturing Industry
- Finance Industry
- Software Development
- Information Technology
Keywords perdidas
Market and Product Analysis Product Strategy Development Product Planning and Roadmapping Release Management Life Cycle Management Customer Insights Requirements Management Marketing and Communications Orchestration and Team Communications Customer Support
Requirements Engineering (RE) User Stories New Product Development (NPD) Product Development Feature Elicitation UI (User Interface) Design Prototyping
Strategic Management “Market Analysis” “Product Analysis”
Product Strategy “Product Strategy” “User Experience” “Product Vision” “Product Positioning” “Delivery Model” “Service Strategy” “Ecosystem Management” “Sourcing” “Pricing” “Financial Management” “Performance Management” “Risk Management” “New product development” “Business Model” “Product performance” “Product usage”
Product Planning “Product Planning” “Customer Insight” “Life Cycle Management” OR “Life-cycle” OR “Lifecycle Management” “Roadmapping” “Release planning” “Requirements management” “Requirements elicitation”
andre”Product Definition”, “Product Scope”, “Customer insight”, “Customer Journey”, “Customer feedback”, “Voice of the Customer”, “Persona”, “User Behavior”, “Issue tracking”, ""Knowledge base” OR “knowledge-base” OR “knowledgebase"", “UX design”, “User Story”, “Requirements specification”, “Roadmap”, “Backlog”, “Release Plan”