Business, Projects and Management
Product management
Product management decides what a product should become next and why, and answers for whether the result was worth building. It sits where business analysis, agile delivery and strategy meet: discovering what users need, ordering a backlog against limited capacity, setting goals and reading the numbers afterwards. In Scrum the product owner carries this accountability for one product; in larger organisations a product manager often carries it across several.
Why this topic exists: Discovery, roadmaps, prioritisation, metrics and the product owner's accountability: where business analysis, agile and strategy meet (Scrum Guide's Product Owner; SFIA Product management; PSPO).
Product management decides what a product should do next and answers for whether it was worth doing. SFIA 9 frames the skill across a whole lifecycle, from the first idea through growth and maturity to eventual retirement, and applies it to internal products as well as those sold to customers. Its guidance covers research into users and markets, vision and roadmaps, pricing, and watching performance and competitors, delivered by plan-driven or adaptive means as the context demands. It is a role of influence more than authority: most product managers direct nobody and win agreement through evidence and clarity.
The product owner in Scrum
The 2020 Scrum Guide makes the product owner accountable for maximising the value the team's work produces, and insists that a single person holds the role rather than a group. That person develops and communicates the product goal, creates and orders the product backlog, and keeps it visible and understood. Others may help write items, but the ordering belongs to the owner, and the organisation is expected to respect those decisions.
Outside Scrum the usual title is product manager, and the scope is often wider: several teams, a portfolio of features, pricing and positioning worked out with marketing. Many organisations use both titles for different altitudes of the same job. SFIA's framing fits that wider role better than the Scrum Guide does, since the guide says nothing about pricing, market research or positioning.
The working cycle
- Discovery. Interviews, usage data and small experiments to find out which problems deserve solving before anything is built.
- Strategy and roadmap. A product goal tied to the company's direction, and a roadmap showing themes and outcomes rather than a promise of features by date.
- Prioritisation. Ordering the backlog against limited capacity, weighing value, cost, risk and what the team would learn. Scoring schemes structure the argument; they do not replace judgement.
- Delivery. Turning outcomes into user stories and other items with a shared definition of done, usually tracked in Jira or a similar backlog tool.
- Measurement. Metrics that show whether users behave differently, reviewed after release so the next cycle starts from evidence. Outputs such as features shipped are easy to count and say little; outcomes such as changed behaviour are harder to measure and say far more.
The beginner's mistake is acting as a feature broker: collecting requests from sales, support and executives and queueing them in order of who asked loudest. The backlog swells, everything is urgent, and the product turns into a pile of unrelated features. The job is to decline most requests with a reason the requester can accept. Scrum.org's PSPO I is the exam closest to the role; it checks understanding of the product owner's accountability as the guide describes it, not skill at discovery or pricing. Product work draws on business analysis for requirements, agile and Scrum for delivery and strategy for direction, and its research methods overlap with UX research in the design silo.
Next to this topic
- Project management fundamentalsCharter, scope, schedule, cost, risk and stakeholders: the predictive vocabulary of PMBOK 7's performance domains and the PMP ECO's Process domain, tested by CAPM, PMP, PRINCE2 and IPMA.
- Agile, Scrum and KanbanThree accountabilities, five events, three artefacts and the empirical pillars of the 2020 Scrum Guide; Kanban's flow; the PSM and PSPO exams and PMP's agile half.
- Business analysis and requirementsElicitation, requirements life cycle, strategy analysis, solution evaluation: BABOK v3's six knowledge areas, the discipline between the business and the build (SFIA Change analysis).
- Organisational change and transformationMaking a change stick in an organisation is its own discipline (SFIA Change planning: organisational change management and enablement; PMBOK's stakeholder and uncertainty domains).
- Leadership and people managementRunning a team: delegation, feedback, performance, hiring, motivation (SFIA People management; PMP's People domain; Udemy's largest business shelf).
- Business strategy and planningBusiness models, competitive position, planning and the numbers behind a decision (SFIA Strategic planning; Udemy Strategy; the business model canvas).
- Operations, Lean and Six SigmaProcesses, quality and waste: Lean, Six Sigma's DMAIC and the belts, supply chain and operations management (SFIA Business process improvement; Udemy Operations).
- Entrepreneurship and small businessStarting and running a small business: idea to model, funding, legal basics, first customers (Udemy Entrepreneurship; the site's own small-business and freelance readership).
- Sales and negotiationProspecting, discovery, closing, key accounts and negotiating: the revenue side of every business (Udemy Sales; SFIA Selling).
- Business communication and presentingWriting, presenting, meetings and public speaking: the skill every other business skill is delivered through (Udemy Communication; SFIA Relationships and engagement).
- Freelancing and independent workBriefs, statements of work, day rates, retainers and scope creep: how independent work is scoped, priced and agreed (the site's freelancing concepts and the /freelance/ silo).
Concepts to know
Glossary entries with the reason each one matters here.
- Product Backlog
The product owner's instrument.
- User Story
How outcomes become work items.
- Definition of Done
Quality as the product sees it.
Certifications that test it
Vendor exams and free certificates; facts, cost and the preparation path are on each page, and the certifications hub has them all.
Tools of the trade
- Jira
The product backlog's usual home.
Frequently asked
- Is a product owner the same as a product manager?
- Sometimes. The product owner is Scrum's accountability for one product backlog; product manager is a job title that often includes strategy, pricing and several teams. In small companies one person does both, while in large ones a product manager may work across several product owners.
- Do product managers need technical skills?
- Enough to understand what is hard, what is risky and what engineers are telling them. Writing code is rarely part of the job. Reading usage data and running simple analyses usually helps more than coding does.
- How do people move into product management?
- Mostly sideways from a neighbouring role: business analysis, UX, engineering, customer success or marketing. Take ownership of a small product area where you already work, show decisions grounded in evidence, and the title tends to follow.
Courses in the directory
83 courses are filed here; the top 4 by our ranking, details and the provider link on each course page.
Last reviewed 26 September 2026 · Getting Digital