Assistant Product Owner, CCA Mission Autonomy (Platform Integration) (R5849)

What you'd do

• Work with the Product Owner and Chief Engineer to understand customer product needs (across the CCA program office, platform providers, and operational end users) and to determine priority, separating must-have capability from deferrable scope
• Elicit and validate needs and priorities from the customer, including official guidance and scoping documents, and from operational subject matter experts or surrogate end users as available
• Translate customer intent into customer needs into user stories and epic descriptions — including value proposition, success criteria, acceptance criteria, expected effort and timeline, dependencies, risks, and preconditions for success — against which feature crews can execute their sprints
• Own day-to-day management of the Shoal 1 epic backlog across feature crews, including maintaining traceability with customer requirements, refining the backlog, and monitoring backlog updates to ensure changes in priority or scope are surfaced and their rationale documented appropriately
• Provide a product perspective to feature crews at Shoal 1-specific sprint planning and review ceremonies, by maintaining an informal integrated product map of epics, interfaces, dependencies, and program milestones
• In collaboration with the Shoal Lead, manage dependencies across shoals, and carry integration decisions and associated implementation implications through to the respective shoal or feature crew leads, or collaboration partner
• In collaboration with the Shoal Lead, support development and integration of the operator interface, primarily through the backlog — the HMI feature crew owns delivery, the Shoal Lead owns requirements and acceptance, and the APO owns description, communication, and prioritization of epics
• Keep protected weekly hands-on time in the operator interface, so that HMI-specific epics and instructions can be written from first-hand use rather than second-hand reports
• Support the platform integration crew in their interaction with vendors
• Act as translator across disciplines — normalize preferred terminology and make specialist discussion accessible to the whole team, ensuring general consistency