Trova · 22 hours ago
Salesforce Product Owner
Trova is seeking a Salesforce Product Owner for a 12-18 month project focused on implementing Salesforce Health Cloud. The Product Owner will be responsible for owning the product vision and roadmap, translating business needs into features, and prioritizing work for the scrum team while acting as the primary interface between business stakeholders and IT delivery.
Staffing & Recruiting
Responsibilities
Owns the product vision and roadmap for a value stream or solution area
Translates business needs into features and user stories
Prioritizes work so the scrum team delivers the highest-value increments first
Acts as the primary interface between business stakeholders and IT delivery
Ensures what is built aligns with organizational goals, architectural standards, and member needs
Defining & grooming features (feature specifications) in collaboration with stakeholders
Breaking epics into user stories as vertical slices of value ("skateboard to Tesla")
Defining user story acceptance criteria
Owning and managing the backlog for the scrum team (multi‑project)
Project charter, scope definition, and phasing
Project feature list and technical deliverable list
Implementation estimates (sprints per feature, refined story-point estimates)
Business case analysis inputs (IT cost/duration estimates, benchmark vs. other projects)
Final decisions on scope boundaries, major roadmap moves, and technology selection
Stakeholder requirements elicitation (partnering with UX, Delivery, etc.)
Translating business requirements into functional design (user flows, system behaviors)
Creating and communicating the design intent: “What is supposed to happen?”
Vendor technical requirements and vetting for your product area
User testing and research (partnering with UX)
User workflow and interface design for specific features
Vendor SoWs and contracts, vendor integration design
Maintaining a prioritized, refined backlog across projects in the scrum team
Ensuring each story is ready (clear AC, dependencies understood) before sprint planning
Refined implementation estimates (story points per epic)
Technical tasking of user stories (with Principal Dev / Delivery Manager)
Sprint ceremonies (planning, review, retrospectives) as a key decision‑maker on scope and acceptance
Whether a feature/user story meets business expectations and acceptance criteria
Trade‑off decisions (must‑have vs. can‑defer) within your product scope
Release scoping decisions impacting your product
UAT planning and execution (coordinating with SRE/Prod Ops)
Training and rollout readiness (content, timelines, who needs what)
Providing product content for project communications / status updates
Ongoing scope management as new needs and constraints arise
Project change requests (providing product impact and recommendation)
Cross‑team dependency coordination (Scrum of Scrums)
Qualification
Required
Must be US citizen and based in the United States
Owns the product vision and roadmap for a value stream or solution area
Translates business needs into features and user stories
Prioritizes work so the scrum team delivers the highest-value increments first
Acts as the primary interface between business stakeholders and IT delivery
Ensures what is built aligns with organizational goals, architectural standards, and member needs
Defines & grooms features (feature specifications) in collaboration with stakeholders
Breaks epics into user stories as vertical slices of value
Defines user story acceptance criteria
Owns and manages the backlog for the scrum team (multi-project)
Stakeholder requirements elicitation (partnering with UX, Delivery, etc.)
Translates business requirements into functional design (user flows, system behaviors)
Creates and communicates the design intent
Vendor technical requirements and vetting for your product area
Maintains a prioritized, refined backlog across projects in the scrum team
Ensures each story is ready (clear AC, dependencies understood) before sprint planning
Acts as functional Approver for whether a feature/user story meets business expectations and acceptance criteria
Ongoing scope management as new needs and constraints arise