Product Owner

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to decide which sections to include: - About the role: combine company overview and maybe "What We Do" and "Our People Matter Most". We'll put prose in

  maybe multiple paragraphs. - Responsibilities: list from Essential Responsibilities (maybe also include What You Will Do? but that's essentially responsibilities). We'll combine both? The "What You Will Do" is a paragraph summarizing responsibilities; we could include that as prose before the list. But we must not duplicate content. We'll include the paragraph as prose, then the list. - Requirements: Minimum Qualifications list. - Skills: Desired Skills list. - Benefits: list. We should not include Qualifications heading if we already have Requirements; but we could include Qualifications as same as Requirements? The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't require all; only include when posting has real content. We have content for Requirements (minimum qualifications) and Skills (desired skills). Qualifications could be considered same as Requirements; but to avoid duplication, we can omit Qualifications heading. Or we could put Minimum Qualifications under Qualifications and Desired Skills under Skills, and omit Requirements. But we need to decide which mapping is more logical. Usually Requirements = minimum qualifications, Qualifications = maybe also minimum? But we have both Minimum and Desired. I'd map Minimum Qualifications to Requirements, Desired Skills to Skills. Omit Qualifications. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits. Now ensure we don't include any boilerplate like EEO etc. Not present. Now produce HTML. We'll need to escape any HTML special characters? Not needed. Structure:

  About the role

  At HHS Tech Group (HTG), our work matters, and each of us makes a difference in the lives of people every day. HTG is a leader in the development and delivery of innovative, purpose-built modular software and technology solutions to clients in the commercial and government sectors. HHS Tech Group creates innovative, purpose-built technology products and solutions, resulting in value and positive, quantifiable impact for our clients and the people they serve. Our people bring our software to life through collaborative relationships with our clients, working as a team, helping to solve complex problems that create positive personal and community impact for the people our clients serve. Each day, our software products and our people are making a difference. Our People Matter Most Improving the lives of others and making an impact daily is no simple task. We are dedicated to our team’s professional and personal growth and well-being.

  Then Benefits? Actually order: About the role, Responsibilities, Requirements, Skills, Benefits. Responsibilities:

  Responsibilities

  Our Product Owner will be an expert in MMIS (Medicaid Management Information System) Health IT and is responsible for defining, prioritizing, and managing the product backlog for a specific MMIS system, acting as the voice of the customer and stakeholders to ensure the development team delivers features that align with business needs and regulatory requirements within the healthcare landscape, collaborating closely with developers, testers, and business analysts to guide the product roadmap and deliver valuable functionalities throughout the development lifecycle.

  • Requirements Gathering and Analysis: Conduct user research and gather requirements from stakeholders including Medicaid beneficiaries, providers, and internal business teams to understand their needs and pain points. Translate complex business requirements into clear, concise user stories and acceptance criteria for the development team. Collaborate with subject matter experts to ensure compliance with Medicaid regulations and industry standards.
  • Product Vision and Strategy: Develop and communicate a clear product vision and roadmap for the MMIS system, aligning with overall organizational goals. Prioritize features and functionalities based on business value, user impact, and regulatory considerations. Stay informed about industry trends, emerging technologies, and regulatory changes impacting the MMIS landscape.
  • Backlog Management: Own and manage the product backlog, ensuring items are well-defined, prioritized, and ready for development. Regularly refine and update the backlog based on feedback from stakeholders and changing business needs. Collaborate with the development team to estimate effort and complexity of backlog items.
  • Agile Collaboration: Facilitate sprint planning sessions, ensuring the team understands the priorities and goals for each sprint. Participate in daily stand-ups and sprint retrospectives to track progress and identify areas for improvement. Actively engage with the development team to address questions, clarify requirements, and remove roadblocks.
  • User Experience and Testing: Work closely with UX designers to create intuitive and user-friendly interfaces for the MMIS system. Collaborate with the QA team to define testing strategies and ensure quality throughout the development process.
  • Stakeholder Management: Communicate effectively with key stakeholders including business leaders, technical teams, and regulatory bodies to keep them informed about product progress and address concerns. Proactively identify and manage risks that could impact product delivery and compliance.
  Requirements (