Deputy Program Manager / Scrum Master
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We have overview paragraph, contributions (responsibilities), qualifications, preferred, about Steampunk (maybe "About the company"? Not listed but could be "About Steampunk"? Not in list but we could use "About the role"? Actually overview is like "About the role". So we can use About the role
with the overview paragraph.
Responsibilities: contributions list.
Requirements: qualifications list (mandatory). Possibly separate "Qualifications" heading.
Skills: maybe not needed; we can embed in qualifications.
Benefits: posting mentions benefits but not specifics; says "Learn more about additional Steampunk benefits here." No specific benefits listed, so we should NOT create Benefits section because no specific content.
Pay: we have salary range $140,000 - $200,000 USD yearly. So we should include Pay section with that info.
Schedule: mentions "Local to Baltimore, MD metro area and willing to go on client site at least 2 days a week". That's schedule/location info. Could be Schedule section. We'll include Schedule.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: EEO, identity statement, etc. Also remove "About Steampunk" maybe? It's not boilerplate but it's company description. Could be included as "About the company"? Not in allowed headings but we could still use About Steampunk
maybe not allowed? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. Probably we should stick to those. So we could incorporate Steampunk description into Overview or maybe omit. The overview already includes some description of role; the "About Steampunk" paragraph is separate. Could we include it under Overview? Might be okay to add a paragraph after overview. But we should not create a heading not listed. Safer to omit the About Steampunk paragraph? But we must preserve ALL substantive information. The About Steampunk paragraph is substantive about company. However we could incorporate it into Overview section as additional paragraph. That would preserve info without extra heading.
Similarly, the "Identity Statement" and EEO etc are boilerplate to remove.
Thus sections:
About the role
About the role
Overview paragraph (the first paragraph after "Overview Steampunk is seeking...") plus maybe the About Steampunk description? We'll keep overview as given. Then Responsibilities: list contributions. Then Qualifications: list mandatory qualifications. Then Skills? Not needed. Then Pay: salary range. Then Schedule: location and client site requirement. We must not include Benefits. We need to ensure we preserve all substantive info: contributions list, qualifications list, preferred qualifications? The preferred section includes CSM, PSM, scaled Agile frameworks, Human-Centered Design. Those are substantive; we could include them under Qualifications or maybe a separate "Preferred qualifications" but not in list. Could embed under Qualifications as a sublist? Might be okay to have a separate heading "Preferred qualifications" but not in examples. Safer to include under Qualifications as part of same list, maybe separate paragraph "Preferred:" but still under Qualifications heading. We must not invent placeholders. Let's extract details. Overview paragraph: "Steampunk is seeking a Deputy Program Manager / Scrum Master to support day-to-day execution of a large federal advisory program, applying the same program/project manager competency standard at the operational level. You'll be a client-facing leader, coach, and mentor — driving delivery in a government consulting environment with a proven track record of building Agile teams that are self-organizing, motivated, and client-focused, and comfortable engaging and mentoring at every level of a project team." We could also include the sentence about salary? No, that's separate. Responsibilities list (contributions): - Facilitate sprint planning, sprint reviews, retrospectives, and daily standups; manage Kanban flow to keep operational work visible and unblocked - Identify, track, and help remove delivery impediments and blockers at the team level before they escalate to program-level risk - Run the cross-team Scrum-of-Scrums logistics — agenda, cross-team dependency capture, and action-item tracking — feeding the integrated program schedule - Maintain team-level backlogs, sprint boards, and dependency maps in coordination with workstream leads - Run recurring project health checkpoints, converting retrospective findings into course corrections and monthly risk-register updates - Support acknowledgment and tracking of COR-directed actions and escalations - Coach delivery teams on Agile/Scrum practices and drive continuous process improvement - Support Transition-In logistics, including onboarding coordination and system/access tracking for incoming team members - Deputize for the Senior Program Manager in reviews and decision-making as needed Qualifications (mandatory): - Ability to obtain and maintain a U.S. government security clearance - Bachelor's degree, preferably in Information Technology or a related field, and 8+ total years of experience - 7+ years of program/project coordination experience, including 3+ years as a Scrum Master or Agile delivery lead - Current PMP, FAC-P/PM, or equivalent industry-recognized credential - Working proficiency in integrated scheduling and risk/issue tracking - Experience on federal or other large, complex enterprise programs - Strong facilitation skills and demonstrated judgment coordinating across multiple, culturally diverse stakeholder groups - Demonstrated ability to influence and consult while providing thought leadership to stakeholders on governance, program/project management, and business process challenges - Excellent written and verbal communication skills, with strong presentation and facilitation skills - Strong organizational and analytical skills - Local to Baltimore, MD metro area and willing to go on client site at least 2 days a week Preferred qualifications (maybe include under Qualifications): - CSM, PSM, or equivalent Agile certification - Experience supporting scaled Agile frameworks (SAFe or similar) - Experience with Human-Centered Design Pay: $140,000 - $200,000 USD yearly Schedule: Already covered in qualifications (local to Baltimore...). But we could still have Schedule section with that info. However we might duplicate. The instruction: avoid duplication? Not explicitly but we should preserve all info; duplication may be okay but better to avoid. We could place location info under Schedule and remove from Qualifications. But Qualifications includes "Local to Baltimore, MD metro area and willing to go on client site at least 2 days a week". That's a qualification? It's more location/schedule. We could move it to Schedule section and keep Qualifications without that line. That would avoid duplication. Let's do that. Thus Qualifications list excludes the location line. Schedule section: "Local to Baltimore, MD metro area and willing to go on client site at least 2 days a week." Pay section: "$140,000 - $200,000 USD yearly" Now About the role section: include overview paragraph plus maybe the About Steampunk description? We'll incorporate About Steampunk paragraph as additional paragraph under About the role. About Steampunk paragraph: "Steampunk relies on several factors to determine salary, including but not limited to geographic location, contractual requirements, education, knowledge, skills, competencies, and experience. The projected compensation range for this position is $140,000 to $200,000. The estimate displayed represents a typical annual salary range for this position. Annual salary is just one aspect of Steampunk’s total compensation package for employees. Learn more about additional Steampunk benefits here." But we already have Pay section with salary range; the above paragraph repeats salary range and mentions benefits. We could keep it but might duplicate salary. However we should preserve all substantive info; duplication may be okay but we could incorporate the benefits mention? But we are not creating Benefits section because no specific benefits. The sentence "Learn more about additional Steampunk benefits here." is a link; we could keep as a sentence but it's basically a referral. Might be considered boilerplate? It's not EEO but it's a generic benefits link. Might be okay to keep as part of About the role? It's not essential. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those categories but it's a generic benefits link; could be considered boilerplate? It's not legal/EEO. It's a reference to benefits page. Might be considered navigation? It's a link to benefits. Might be considered navigation? Safer to omit that sentence as it's not substantive detail about the job. The substantive detail about salary is already captured in Pay section. So we can omit the About Steampunk paragraph entirely, or keep only the first sentence about factors determining salary? That's also somewhat generic. I'd say we can omit the whole About Steampunk paragraph as it's mostly generic and duplicates salary info. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The About Steampunk paragraph is not substantive about the role; it's about compensation determination and benefits link. Since we have Pay section, we can drop it. Thus About the role only includes the overview paragraph. Now we need to output HTML fragment only, no markdown. Let's craft:
About the role
Steampunk is seeking a Deputy Program Manager / Scrum Master to support day-to-day execution of a large federal advisory program, applying the same program/project manager competency standard at the operational level. You'll be a client-facing leader, coach, and mentor — driving delivery in a government consulting environment with a proven track record of building Agile teams that are self-organizing, motivated, and client-focused, and comfortable engaging and mentoring at every level of a project team.
Responsibilities
- Facilitate sprint planning, sprint reviews, retrospectives, and daily standups; manage Kanban flow to keep operational work visible and unblocked
- Identify, track, and help remove delivery impediments and blockers at the team level before they escalate to program-level risk
- Run the cross-team Scrum-of-Scrums logistics — agenda, cross-team dependency capture, and action-item tracking — feeding the integrated program schedule
- Maintain team-level backlogs, sprint boards, and dependency maps in coordination with workstream leads
- Run recurring project health checkpoints, converting retrospective findings into course corrections and monthly risk-register updates
- Support acknowledgment and tracking of COR-directed actions and escalations
- Coach delivery teams on Agile/Scrum practices and drive continuous process improvement
- Support Transition-In logistics, including onboarding coordination and system/access tracking for incoming team members
- Deputize for the Senior Program Manager in reviews and decision-making as needed
Qualifications
- Ability to obtain and maintain a U.S. government security clearance
- Bachelor's degree, preferably in Information Technology or a related field, and 8+ total years of experience
- 7+ years of program/project coordination experience, including 3+ years as a Scrum Master or Agile delivery lead
- Current PMP, FAC-P/PM, or equivalent industry-recognized credential
- Working proficiency in integrated scheduling and risk/issue tracking
- Experience on federal or other large, complex enterprise programs
- Strong facilitation skills and demonstrated judgment coordinating across multiple, culturally diverse stakeholder groups
- Demonstrated ability to influence and consult while providing thought leadership to stakeholders on governance, program/project management, and business