GAP Product Owners are in a crucial position on Agile SCRUM teams, and play a key role in the success of GAP projects. The Product Owner works closely with the Product Management team, and directly with customers, to understand the market needs. They are responsible for conveying the market needs to the SCRUM team in the form of user stories. The Product Owner is also responsible for prioritizing user stories to create a backlog based on business value and serving as the point person for the developers and QA members on the SCRUM team. The Product Owner participates in standard SCRUM ceremonies including stand-ups, backlog grooming, and sprint planning. The Product Owner is responsible for signing off on features to ensure they meet the agreed-upon acceptance criteria and overall market needs.**Desired skills and experience****Bachelor's degree, or equivalent experience**- 2+ years of relevant software product management, product owner, or business analysis experience in an agile environment- Experience in the Software industry and a good understanding of Software Development and Product Life Cycle, including customer requirements gathering, software design, and development, testing including unit, functional, systems, and integration implementation/delivery and maintenance- Skilled at meeting facilitation and presentation- Experience working with Scrum and Product Owner role or equivalent Agile Development Process-Knowledge of how different systems interact, including potential problems and difficulties that may occur- Flexibility to partner with and negotiate with various individuals across teams at different levels, both business people and technical people- Strong time management skills and project management skills- Must thrive in a fast-paced, time-compressed, and dynamic environment- Experience Story Mapping and Road Maps- Skilled at writing acceptance criteria- Excellent communications skills: written, verbal, and group presentations at the team level**Goals of the GAP Associate Product Owner Resource**:- Intermediary between the Dev team and the rest of R&D:- Work directly with the team/team lead/scrum master- Guide the team forward to meeting the PI Objectives outlined by the Product Owner- Monitor quality and relevance of development effort relative to TFS Feature Acceptance Criteria- Representation at all SAFe ceremonies (DSU, sprint planning/review, stakeholder review, refinement)- Communicate AC Hospitality relevance- Communicate AC relevance to the MB/S&C platform/domain- Empowered to make product decisions and communicate priorities with these other departments- Takes the initiative to bring the necessary resources together to work through team impediments- Working directly with the Primary Product Owner- Frequent, effective communication of item/status updates to me (I will be the primary point of communication with stakeholders)- Receive platform guidance Dev Manager- Working directly with Product Management: (Product Strategist)- Working directly with the Dev Architecture team to clarify feature AC: Platform Architect, Security Architect, API Architect)- Working with Operations - managing communication for Dev deliverables required for Production deployments- Working with Services - working with me to stick to prioritized commitments- Participation in Product Owner team (knowledge sharing/problem solving/SAFe methodology updates)- The primary Product Owner will maintain the communication with...- Product Strategist- Product Release Team- Stakeholders- Customer base**Preferred Skills**- Ability to use wireframes to prototype new functionality- Scrum Product Owner certification (CSPO)- Prior experience as a Product Owner- Knowledge and experience of SAFe**Business analyst background**:- Experience as BA, transforming business needs/outcomes into stories.- Understands analyses and is able to decompose the work and see what's important for the BV.- Technical understanding (APIs, REST, Swagger,):- Knows and understands technical terminology, not necessarily a high-tech level of experience, but it's important to understand and feel comfortable with tech terms.- If they have tech experience it is something nice to have.- Understands the operation.- Knowledgeable of UML (Sequence diagrams,):- Able to use diagrams/flowcharts as a way to visually explain a process.- Knows or is familiar with what is a class diagram, activity diagram, and sequence diagram.- The important thing here is to have the skill and experience representing processes visually to convey to the team and help them understand how a system behaves.- UML is a modeling language that they use, so the person could learn it. The more familiar they are with it the better, but it's not a must.
