Associate Scrum Master / Agile Project Coordinator
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real content. The posting includes: Position Summary (could be About the role). Responsibilities. Required Qualifications (maybe Requirements). Preferred Qualifications (maybe Qualifications or Skills). Measures of Success (maybe not a standard heading; could be part of About the role? But we need to decide. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map: About the role -> Position Summary. Responsibilities -> Responsibilities. Requirements -> Required Qualifications. Qualifications -> Preferred Qualifications? Or maybe Skills -> Preferred Qualifications? But we have both Required and Preferred. Could combine? The instruction: Prefer a few substantive sections over many thin ones. Could have sections: About the role, Responsibilities, Requirements, Qualifications. Skills maybe not needed if covered. Benefits, Pay, Schedule: we have Salary Range (Pay) and maybe no Benefits or Schedule. Salary Range is given: $72,000 to $78,000. So we should include Pay section. Benefits not mentioned, so omit. Schedule not mentioned, omit. Also we have Location Remote, Clearance U.S. Citizen with ability to obtain a Security Clearance, Application Deadline September 30, 2026. Those are metadata; we should fold minor metadata into a short
or drop it. Probably include a short paragraph at top with location, clearance, deadline. Not as heading. We must not repeat job title as heading. So no heading for Associate Scrum Master / Agile Project Coordinator. We must preserve all substantive information. So include details from Position Summary, Responsibilities, Required Qualifications, Preferred Qualifications, Measures of Success, About S2i2 (company description). Also include Salary Range. We need to remove boilerplate: EEO etc. At end there is EEO statement; remove. Also remove duplicated lines, cookie/navigation/legal etc. Not present. Now produce HTML fragment. Structure:
Location: Remote. Clearance: U.S. Citizen with ability to obtain a Security Clearance. Application Deadline: September 30, 2026.
About the role
Position Summary ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
Preferred Qualifications ...
maybe list. But we could also put Preferred Qualifications as- ...
Pay
Salary Range: $72,000 to $78,000.
Measures of Success
maybe not standard but we could include as a section? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we could still use other headings if needed. But better to incorporate Measures of Success into About the role or Responsibilities? It's substantive; maybe we can add a section "Measures of Success" as as it's not in the list but still a heading. The instruction didn't forbid other headings, just gave examples. I'd include it.
Also About S2i2 could be "About the company" but not in list; maybe we can incorporate into About the role or drop? It's substantive; we could add a section "About the company". But instruction says prefer few substantive sections over many thin ones. Could combine About S2i2 with About the role? Might be okay to add a separate section "About the company". However the examples didn't include About the company; but we can still use for any section heading. I'd include About the company.
But to keep sections few, we could merge About S2i2 into About the role paragraph.
Let's decide: We'll have sections: About the role (includes Position Summary and About S2i2), Responsibilities, Requirements, Qualifications (Preferred), Pay, Measures of Success.
That's 6 sections.
Now ensure we preserve all substantive info.
Let's extract details.
Position Summary: "We are seeking an early-career Agilist to coordinate delivery across 3 software integration teams: Front End Integration, Backend Integration, and Data. The successful individual will maintain the teams' shared Jira operating rhythm, facilitate agile ceremonies, improve backlog quality, track cross-team dependencies, and give project leadership reliable visibility into delivery progress. The position reports to the Project Manager and works closely with the technical lead, solutions architect, project coordinator, and 3 team leads. It facilitates delivery but does not own product priorities, make technical decisions, or replace the team leads' responsibility for execution."
About S2i2: "S2i2 is a growing company with a supportive and inclusive culture and many opportunities for professional development and growth. We have created a supportive, family-like work environment where contributions are recognized. Regular company updates and open lines of communication with leadership fosters collaboration within the company. We Are Proud To Include Support to achieve professional certifications and degrees Leadership that is accessible to all employees Regular company updates Client networking social engagements Monthly team-building activities (past examples: Top Golf) Supporting our community - including veterans"
We need to preserve that exactly? Probably keep as is but maybe lower case? Keep original.
Responsibilities list:
- Facilitate sprint planning, backlog refinement, daily standups, sprint reviews, retrospectives, and cross-team dependency meetings.
- Administer the shared Jira backlog and sprint structure for all three teams.
- Ensure stories and tasks have clear descriptions, acceptance criteria, estimates, ownership, team assignments, and dependency links.
- Help team leads translate milestones and deliverables into appropriately sized sprint work.
- Monitor sprint commitments, blockers, aging work, scope changes, and delivery risks.
- Escalate unresolved blockers and cross-team dependencies to the appropriate project or technical leader.
- Maintain Jira dashboards and provide concise reporting on velocity, throughput, burndown, blocked work, and milestone progress.
- Keep Jira execution data aligned with the program's higher-level planning and reporting tools.
- Maintain action, decision, risk, and dependency records as assigned.
- Coach team members on practical Scrum and Kanban practices and encourage continuous improvement.
- Support release, demonstration, authorization, and stakeholder-readiness activities.
- Follow applicable government security, access, and information-handling requirements.
Required Qualifications list:
- 1-3 years of experience as an Agile Coordinator, Scrum Master, Project Coordinator, Business Analyst, or similar delivery support professional.
- Practical experience using Jira to manage backlogs, sprints, workflows, dashboards, and reports.
- Working knowledge of Scrum, Kanban, user stories, acceptance criteria, estimation, and dependency management.
- Strong meeting-facilitation, organization, written communication, and follow-up skills.
- Ability to coordinate several teams without relying on formal authority.
- Ability to identify delivery problems, communicate them clearly, and drive issues toward resolution.
- Bachelor's degree or equivalent relevant experience.
Preferred Qualifications list:
- PSM I, Certified ScrumMaster, or comparable entry-level agile certification.
- Experience supporting software development, systems integration, data, or DevSecOps teams.
- Experience with government or Department of Defense programs.
- Familiarity with Confluence, Airtable, release planning, and risk tracking.
- U.S. citizenship and ability to satisfy any required customer-access or clearance requirements.
Measures of Success:
- Within The First 30 Days, The Successful Candidate Will Establish a consistent ceremony schedule across all three teams.
- Keep sprint and backlog information accurate and current.
- Ensure planned work meets an agreed definition of ready.
- Make cross-team dependencies and blockers visible before they affect milestones.
- Provide dependable sprint and milestone reporting to project leadership.
- Help the teams complete at least two retrospectives with documented improvement actions.
Pay: Salary Range $72,000 to $78,000.
Now produce HTML.
We need to wrap each list in - ...
. For prose use
for any section heading. I'd include About the company.
But to keep sections few, we could merge About S2i2 into About the role paragraph.
Let's decide: We'll have sections: About the role (includes Position Summary and About S2i2), Responsibilities, Requirements, Qualifications (Preferred), Pay, Measures of Success.
That's 6 sections.
Now ensure we preserve all substantive info.
Let's extract details.
Position Summary: "We are seeking an early-career Agilist to coordinate delivery across 3 software integration teams: Front End Integration, Backend Integration, and Data. The successful individual will maintain the teams' shared Jira operating rhythm, facilitate agile ceremonies, improve backlog quality, track cross-team dependencies, and give project leadership reliable visibility into delivery progress. The position reports to the Project Manager and works closely with the technical lead, solutions architect, project coordinator, and 3 team leads. It facilitates delivery but does not own product priorities, make technical decisions, or replace the team leads' responsibility for execution."
About S2i2: "S2i2 is a growing company with a supportive and inclusive culture and many opportunities for professional development and growth. We have created a supportive, family-like work environment where contributions are recognized. Regular company updates and open lines of communication with leadership fosters collaboration within the company. We Are Proud To Include Support to achieve professional certifications and degrees Leadership that is accessible to all employees Regular company updates Client networking social engagements Monthly team-building activities (past examples: Top Golf) Supporting our community - including veterans"
We need to preserve that exactly? Probably keep as is but maybe lower case? Keep original.
Responsibilities list:
- Facilitate sprint planning, backlog refinement, daily standups, sprint reviews, retrospectives, and cross-team dependency meetings.
- Administer the shared Jira backlog and sprint structure for all three teams.
- Ensure stories and tasks have clear descriptions, acceptance criteria, estimates, ownership, team assignments, and dependency links.
- Help team leads translate milestones and deliverables into appropriately sized sprint work.
- Monitor sprint commitments, blockers, aging work, scope changes, and delivery risks.
- Escalate unresolved blockers and cross-team dependencies to the appropriate project or technical leader.
- Maintain Jira dashboards and provide concise reporting on velocity, throughput, burndown, blocked work, and milestone progress.
- Keep Jira execution data aligned with the program's higher-level planning and reporting tools.
- Maintain action, decision, risk, and dependency records as assigned.
- Coach team members on practical Scrum and Kanban practices and encourage continuous improvement.
- Support release, demonstration, authorization, and stakeholder-readiness activities.
- Follow applicable government security, access, and information-handling requirements.
Required Qualifications list:
- 1-3 years of experience as an Agile Coordinator, Scrum Master, Project Coordinator, Business Analyst, or similar delivery support professional.
- Practical experience using Jira to manage backlogs, sprints, workflows, dashboards, and reports.
- Working knowledge of Scrum, Kanban, user stories, acceptance criteria, estimation, and dependency management.
- Strong meeting-facilitation, organization, written communication, and follow-up skills.
- Ability to coordinate several teams without relying on formal authority.
- Ability to identify delivery problems, communicate them clearly, and drive issues toward resolution.
- Bachelor's degree or equivalent relevant experience.
Preferred Qualifications list:
- PSM I, Certified ScrumMaster, or comparable entry-level agile certification.
- Experience supporting software development, systems integration, data, or DevSecOps teams.
- Experience with government or Department of Defense programs.
- Familiarity with Confluence, Airtable, release planning, and risk tracking.
- U.S. citizenship and ability to satisfy any required customer-access or clearance requirements.
Measures of Success:
- Within The First 30 Days, The Successful Candidate Will Establish a consistent ceremony schedule across all three teams.
- Keep sprint and backlog information accurate and current.
- Ensure planned work meets an agreed definition of ready.
- Make cross-team dependencies and blockers visible before they affect milestones.
- Provide dependable sprint and milestone reporting to project leadership.
- Help the teams complete at least two retrospectives with documented improvement actions.
Pay: Salary Range $72,000 to $78,000.
Now produce HTML.
We need to wrap each list in - ...
. For prose use
. We must not include markdown fences. Let's craft. First metadata paragraph: maybe
Location: Remote. Clearance: U.S. Citizen with ability to obtain a Security Clearance. Application Deadline: September 30, 2026.
But we shouldn't add extra tags like strong? Not prohibited. Could just plain text. I'll do:Location: Remote. Clearance: U.S. Citizen with ability to obtain a Security Clearance. Application Deadline: September 30, 2026.
Now About the role: combine Position Summary and About S2i2 into onemaybe two paragraphs. We'll do:
About the role
We are seeking an early-career Agilist to coordinate delivery across 3 software integration teams: Front End Integration, Backend Integration, and Data. The successful individual will maintain the teams' shared Jira operating rhythm, facilitate agile ceremonies, improve backlog quality, track cross-team dependencies, and give project leadership reliable visibility into delivery progress. The position reports to the Project Manager and works closely with the technical lead, solutions architect, project coordinator, and 3 team leads. It facilitates delivery but does not own product priorities, make technical decisions, or replace the team leads' responsibility for execution.
S2i2 is a growing company with a supportive and inclusive culture and many opportunities for professional development and growth. We have created a supportive, family-like work environment where contributions are recognized. Regular company updates and open lines of communication with leadership fosters collaboration within the company. We Are Proud To Include Support to achieve professional certifications and degrees Leadership that is accessible to all employees Regular company updates Client networking social engagements Monthly team-building activities (past examples: Top Golf) Supporting our community - including veterans
Now Responsibilities:Responsibilities
- Facilitate sprint planning, backlog refinement, daily standups, sprint reviews, retrospectives, and cross-team dependency meetings.
- Administer the shared Jira backlog and sprint structure for all three teams.
- Ensure stories and tasks have clear descriptions, acceptance criteria, estimates, ownership, team assignments, and dependency links.
- Help team leads translate milestones and deliverables into appropriately sized sprint work.
- Monitor sprint commitments, blockers, aging work, scope changes, and delivery risks.
- Escalate unresolved blockers and cross-team dependencies to the appropriate project or technical leader.
- Maintain Jira dashboards and provide concise reporting on velocity, throughput, burndown, blocked work, and milestone progress.
- Keep Jira execution data aligned with the program's higher-level planning and reporting tools.
- Maintain action, decision, risk, and dependency records as assigned.
- Coach team members on practical Scrum and Kanban practices and encourage continuous improvement.
- Support release, demonstration, authorization, and stakeholder-readiness activities.
- Follow applicable government security, access, and information-handling requirements.
Requirements
- 1-3 years of experience as an Agile Coordinator, Scrum Master, Project Coordinator, Business Analyst, or similar delivery support professional.
- Practical experience using Jira to manage backlogs, sprints, workflows,