Business Analyst / Scrum Master

We need to output HTML fragment with sections for headings where there is real content. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must not include Job ID etc. Remove boilerplate. We have content: Job Summary, Key Responsibilities, Required Qualifications, Preferred Qualifications, Key Skills, Work Arrangement, Ideal Candidate, Employment Type, Work Model, Location, Salary, Experience, Skills (some duplicates). We need to map to sections: About the role (maybe job summary). Responsibilities (key responsibilities). Requirements (maybe required qualifications). Qualifications (maybe preferred qualifications). Skills (key skills). Benefits, Pay, Schedule only if present. There's no explicit benefits, pay, schedule details (salary placeholder). So we should not include Pay/Benefits/Schedule sections because they are not substantive (they have placeholder "[Insert Salary Range]" etc). Work Arrangement is given: full-time hybrid. Could be under "Schedule"? Actually schedule is not given. Work Arrangement could be part of About the role or maybe a separate section? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role (job summary), Responsibilities, Requirements (required qualifications), Qualifications (preferred qualifications), Skills (key skills). Possibly also Work Arrangement could be under About the role or maybe a separate section like "Work Arrangement" but not in list; but we should only use those headings. Could incorporate work arrangement into About the role paragraph. Also "Ideal Candidate" could be part of About the role. We'll preserve all substantive info. We need to output only HTML fragment, no /. Use

headings,

• for lists,

  for prose. We must preserve all substantive info: job summary paragraph, responsibilities list, required qualifications list, preferred qualifications list, key skills list (maybe as list), work arrangement sentence, ideal candidate paragraph, employment type, work model, location, experience, skills (some duplicates). But we must not repeat info unnecessarily; but we must preserve all substantive info. Could combine duplicates. Let's extract substantive info: Job Summary: "We are seeking an experienced Business Analyst / Scrum Master to join our team in a full-time hybrid role. The ideal candidate will combine strong business analysis skills with Agile/Scrum leadership to bridge the gap between business stakeholders and technical teams. The candidate will be responsible for gathering and documenting business requirements, facilitating Agile ceremonies, managing the product backlog, supporting sprint planning and delivery, and ensuring successful communication between stakeholders, product owners, developers, and other cross-functional teams." Key Responsibilities list (many items). We'll output as

  • each. Required Qualifications list: bullet points. Preferred Qualifications list. Key Skills list: categories with sub-items. Could output as
    • each skill item (maybe flatten). But we can keep categories as part of list items. Work Arrangement: "This is a full-time hybrid position, requiring the candidate to work both remotely and onsite based on business and team requirements." Ideal Candidate: "The ideal candidate is someone who can understand business requirements, translate them into actionable user stories, and effectively facilitate Agile delivery. The candidate should be comfortable working with executives, business stakeholders, Product Owners, developers, QA teams, and other cross-functional groups." Employment Type: Full-Time (already mentioned). Work Model: Hybrid (already). Location: [Insert Location] (placeholder, not substantive? It's placeholder, so we should not include because it's not real specific content. The instruction: never emit a heading followed by filler/placeholder text. So we should drop location line. Salary: [Insert Salary Range] placeholder -> drop. Experience: ( Insert Expereince ) placeholder -> drop. Skills: teams,sprint planning,business requirements,scrum,agile (looks like a duplicate list but maybe placeholder; it's not substantive? It's a list but seems like a placeholder; but it's not clearly placeholder like "Insert". It's a list of skills but seems like a duplicate of key skills. However it's likely leftover metadata; but it's substantive? It says "Skills: teams,sprint planning,business requirements,scrum,agile". That's a list but not detailed. Might be considered filler. Safer to drop because it's not detailed and duplicates. Thus we will not include sections for Pay, Benefits, Schedule. We'll produce:

      About the role

      Job summary paragraph + ideal candidate + work arrangement maybe.

      But we need to avoid duplication: The job summary already mentions ideal candidate; we have separate ideal candidate paragraph. Could combine. Let's craft About the role paragraph: combine job summary and ideal candidate and work arrangement. Then Responsibilities. Then Requirements (required qualifications). Then Qualifications (preferred qualifications). Then Skills (key skills). Make sure to use
      • for lists. Let's write. Check for any repeated content: Ensure we preserve all substantive info from responsibilities, required qualifications, preferred qualifications, key skills. Let's extract responsibilities list items exactly as given: - Work closely with business stakeholders, Product Owners, and technical teams to understand business needs and objectives. - Gather, analyze, document, and validate business and functional requirements. - Create Business Requirements Documents (BRDs), Functional Requirements Documents (FRDs), user stories, acceptance criteria, process flows, and use cases. - Facilitate Agile/Scrum ceremonies, including: - Daily stand-ups - Sprint planning - Sprint reviews/demos - Sprint retrospectives - Backlog refinement - Manage and prioritize the product/project backlog in collaboration with Product Owners and stakeholders. - Ensure user stories are clearly defined, actionable, and ready for development. - Identify dependencies, risks, issues, and blockers and work with teams to resolve them. - Track sprint progress, velocity, deliverables, and project milestones. - Act as a facilitator between business stakeholders and development teams. - Support product owners with backlog prioritization and release planning. - Translate complex business requirements into clear technical requirements for development teams. - Coordinate with QA teams to ensure requirements and acceptance criteria are properly covered in test scenarios. - Monitor project scope, timelines, and deliverables. - Prepare project status reports and communicate progress to stakeholders and leadership. - Identify opportunities for process improvement and promote Agile best practices. - Help teams continuously improve their delivery processes through retrospectives and Agile metrics. We need to handle nested list for ceremonies. Could keep as sublist. Required Qualifications list: - Bachelor's degree in Business Administration, Information Technology, Computer Science, or a related field. - 5+ years of experience as a Business Analyst, Scrum Master, or in a combined BA/Scrum Master role. - Strong understanding of Agile and Scrum methodologies. - Experience working with cross-functional software development teams. - Strong requirements gathering and documentation skills. - Experience writing user stories and acceptance criteria. - Excellent communication, presentation, facilitation, and stakeholder-management skills. - Strong analytical and problem-solving abilities. - Experience with backlog management and sprint planning. - Ability to work effectively with both technical and non-technical stakeholders. Preferred Qualifications list: - Certified ScrumMaster (CSM), Professional Scrum Master (PSM), or equivalent certification. - IIBA/CBAP certification is a plus. - Experience with Jira, Confluence, Azure DevOps, or similar Agile tools. - Experience with process modeling tools such as Visio, Lucidchart, or equivalent. - Experience working in software development, IT, financial services, healthcare, retail, or other enterprise environments. - Knowledge of SDLC and software testing methodologies. - Experience working with distributed or hybrid teams. Key Skills list: It's grouped: Business Analysis: Requirements Gathering, BRD, FRD, Use Cases, Process Mapping, Gap Analysis, Stakeholder Management Agile/Scrum: Sprint Planning, Daily Stand-ups, Backlog Refinement, Sprint Reviews, Retrospectives, User Stories, Acceptance Criteria, Release Planning Tools: Jira, Confluence, Azure DevOps, MS Visio, Microsoft Office Soft Skills: Communication, Leadership, Facilitation, Negotiation, Problem Solving, Conflict Resolution, Team Collaboration We can output each as list items, maybe keep categories as part of item text. Now About the role paragraph: combine job summary, ideal candidate, work arrangement. Job summary: "We are seeking an experienced Business Analyst / Scrum Master to join our team in a full-time hybrid role. The ideal candidate will combine strong business analysis skills with Agile/Scrum leadership to bridge the gap between business stakeholders and technical teams. The candidate will be responsible for gathering and documenting business requirements, facilitating Agile ceremonies, managing the product backlog, supporting sprint planning and delivery, and ensuring successful communication between stakeholders, product owners, developers, and other cross-functional teams." Ideal candidate: "The ideal candidate is someone who can understand business requirements, translate them into actionable user stories, and effectively facilitate Agile delivery. The candidate should be comfortable working with executives, business stakeholders, Product Owners, developers, QA teams, and other cross-functional groups." Work arrangement: "This is a full-time hybrid position, requiring the candidate to work both remotely and onsite based on business and team requirements." We can merge: maybe two paragraphs. We'll output:

        About the role

        We are seeking an experienced Business Analyst / Scrum Master to join our team in a full-time hybrid role. The ideal candidate will combine strong business analysis skills with Agile/Scrum leadership to bridge the gap between business stakeholders and technical teams. The candidate will be responsible for gathering and documenting business requirements, facilitating Agile ceremonies, managing the product backlog, supporting sprint planning and delivery, and ensuring successful communication between stakeholders, product owners, developers, and other cross-functional teams.

        The ideal candidate is someone who can understand business requirements, translate them into actionable user stories, and effectively facilitate Agile delivery. The candidate should be comfortable working with executives, business stakeholders, Product Owners, developers, QA teams, and other cross-functional groups.

        This is a full-time hybrid position, requiring the candidate to work both remotely and onsite based on business and team requirements.

        But note we repeated "ideal candidate" twice; but it's okay. Now Responsibilities:

        Responsibilities

        • Work closely with business stakeholders, Product Owners, and technical teams to understand business needs and objectives.
        • Gather, analyze, document, and validate business and functional requirements.
        • Create Business Requirements Documents (BRDs), Functional Requirements Documents (FRDs), user stories, acceptance criteria, process flows, and use cases.
        • Facilitate Agile/Scrum ceremonies, including:
          • Daily stand-ups
          • Sprint planning
          • Sprint reviews/demos
          • Sprint retrospectives
          • Backlog refinement
        • Manage and prioritize the product/project backlog in collaboration with Product Owners and stakeholders.
        • Ensure user stories are clearly defined, actionable, and ready for development.
        • Identify dependencies, risks, issues, and blockers and work with teams to resolve them.
        • Track sprint progress, velocity, deliverables, and project milestones.
        • Act as a facilitator between business stakeholders and development teams.
        • Support product owners with backlog prioritization and release planning.
        • Translate complex business requirements into clear technical requirements for development teams.
        • Coordinate with QA teams to ensure requirements and acceptance criteria are properly covered in test scenarios.
        • Monitor project scope, timelines, and deliverables.
        • Prepare project status reports and communicate progress to stakeholders and leadership.
        • Identify opportunities for process improvement and promote Agile best practices