Product Owner

At Boeing, we innovate and collaborate to make the world a better place. From the seabed to outer space, you can contribute to work that matters with a company where diversity, equity and inclusion are shared values. We’re committed to fostering an environment for every teammate that’s welcoming, respectful and inclusive, with great opportunity for professional growth. Find your future with us.

The **Product Owner** (PO) is a leader in the software development process and part of a self-sufficient Scrum Team. The PO acts as a servant leader, interacting with Product Management and Architecture to understand requirements, then working with the team to elaborate, prioritize and decompose into technical features and stories to be executed by the team. The PO acts as a liaison between the team to the customer and product stakeholders, and is the daily voice to the team facilitating planning, scoping and buy-off exercises allowing the Scrum Team to focus on writing code rather than the writing/clarification of requirements, or pursuing acceptance of features. A Product Owner enables the Scrum Team to avoid task switching, ultimately allowing more dedicated capacity for software to be developed and released to market.

The PO must have daily interactions with the Scrum Team including participation in daily stand-up, providing guidance on development and acceptance of features. The PO also ensures that features are outlined with Product Management and architecture in adequate detail, ready for elaboration to the Scrum Team, minimizing variances in the quality of requirements and lessening the risk of features which lack adequate details to be given to Scrum Teams to work.

**Position Responsibilities**:

- Works closely and frequently with Product Management, customers, and the Scrum Team. Champions exposing the Scrum Team to Product Management and customers for planning and acceptance of features. Acts as the daily voice of the customer and product manager to the Scrum Team on questions related to execution of a feature scope.
- Reviews the vision and roadmap for the product with the team prior to every program increment (PI), shows connectivity between upcoming features in the backlog with the greater vision/roadmap. Invites Management and Product Management to participate in these sessions to ensure stakeholders and team are bought in on the vision and plan. Articulates to the team how the particular product vision fits into a larger ecosystem and corresponding priorities.
- Develops and adheres to a definition of done that captures functional, non-functional requirements. Utilizes definition of done with Scrum Team/Product Management to define, estimate and buy-off features and stories.
- Works closely with Product Management continuously prioritizing the team backlog of features, aligning with the product manager’s product roadmap at the epic level. Works with the team on feature definition and estimation and provides feedback to Product Management on the feasibility of committing to a set of scope at a PI level. (Does not commit to PI scope officially until team conducts PI planning).
- Champions the delivery of the greatest business value with lowest effort required that enables the customer. Scrutinizes features and capabilities on their prioritization and their inclusion in a program increment and release. Is aware of backlog scope and priorities versus capacity and facilitates trade-off discussions with Product Management and the Scrum Team. Acts with a sense of urgency to meet the customer’s needs incrementally and efficiently. Advocates the elimination of non-value added work and unnecessary documentation.
- Continuously grooms and prioritizes the team backlog via backlog grooming sessions with the Scrum Team, ensuring the team’s estimates on work are accurately sized and ready in accordance to anticipated work (in alignment to product roadmap). Elaborates features just in time (abides by DoR guidelines of maintaining the next PI as DoR 4 or above).
- Leads decomposition features into stories and enters into appropriate scrum tool. Ensures stories capture business requirements and technical requirements (including testing and acceptance criteria).
- Facilitates demo sessions for Product Management every sprint, and with the customer (on an agreed upon interval with the customer/Product Management). Champions the team demoing directly to customers and Product Management.
- Facilitates user acceptance testing with Product Management and the customer, ensuring commitments and priorities are met as expected. Negotiates plan/timing for any items that need to be fixed.
- Defines decision making authority with Product Management/Management and is empowered to lead the Scrum Team as a self-sufficient team.
- Advocates for agility, team self-sufficiency, protects the team’s commitments once the sprint plan has been made. Open to negotiation for prioritization prior to next sprint as a result of Pro