A focused course, tailored for you
Federal IT Project Manager's Programme-Authorship Playbook
How a Federal IT Project Manager authors a programme finance protects when portfolio rebalancing reaches federal IT delivery.
When federal IT services firms rebalance portfolios around AI-augmented delivery, PMs without published programme-authorship narratives read as labour-line cost.
$199 one-time
Tailored to your situation. Access within 24 hours. 30-day money-back.
Includes a hand-built implementation playbook delivered alongside course access, generated for your specific situation.
Why this course
Federal IT services firms running portfolio rebalancing reach Project Manager functions in the same operating-model cycle. PMs who continue running 'project delivery' without published programme-authorship are read by the deck as labour line. PMs with documented programme-authorship artefacts read as the leadership the next recompete cites.
The Federal IT PMs who survive own a documented programme strategy with measurable delivery outcomes, a stakeholder map across the agency client and capture team, and a quarterly programme-state artefact the programme director forwards to capture.
The course covers the three artefacts and the 90-day path to programme-authorship framing. Plus a hand-built implementation playbook against your real federal IT scope.
The 12 modules
Module 1. Reading federal rebalancing for PM implications
Federal portfolio rebalancing reorganises PM functions in three phases: enterprise contract-vehicle review, agency-vertical review, and PM-portfolio review. The diagnostic decodes which signals (recompete-win-rate drift, labour-category-cost ratios, contract-vehicle-mix shifts, agency budget cycle constraints) indicate that the PM layer is in the redraw set. Which Federal PMs survive as labour-line cost and which survive as programme-authorship owners with documented authority across agency client and capture.
Module 2. Generic PM vs programme-authorship owner
Two structurally different framings of the same Federal IT PM seat read very differently to the rebalancing review. Generic PM shows up as billable headcount on a labour-category line. Programme-authorship reads as the leadership the programme structurally depends on across recompete cycles: documented programme strategy with measurable delivery outcomes, stakeholder map across agency client and capture team, and quarterly state artefact the programme director forwards. The three artefacts that mark the shift.
Module 3. Your documented programme strategy
Construct the programme strategy as a programme director-grade two-page document anchored to measurable delivery outcomes: schedule performance index, cost performance index, customer satisfaction (agency CIO/CTO survey results), contract-modification capture rate, AI-augmented delivery contribution, and recompete win-rate. Three structural templates (ATO-anchored, agile-delivery-anchored, sustainment-anchored) and the formula for choosing the template that fits your programme.
Module 4. Stakeholder map across the agency client and capture team
Map your stakeholders across agency client (contracting officer, contracting officer representative, programme manager, end-user sponsors), capture team (capture lead, BD director, solutioning lead, pricing lead), and adjacent contractors (subcontractor PMs, integrator partners). Format: stakeholder name, sponsorship-level, last meaningful interaction, current dependency status, and recompete-influence level. The map capture cites by PM name.
Module 5. Quarterly programme-state artefact for the programme director
The quarterly artefact is a two-page state document covering programme momentum, agency-client status, capture-team alignment, AI-augmented delivery outcomes, federal-compliance positioning (ATO, FedRAMP, FISMA, RMF), and emerging risks. Cadence is end-of-quarter delivery to programme director with copies to capture, BD, and pricing leads. Three worked examples from real Federal IT PM portfolios at different recompete stages.
Module 6. Working with capture, BD, and contracting officers
PM work travels into capture (recompete-pursuit teams), BD (account expansion via modifications), and contracting officers (contract-modification negotiation, performance reviews). The collaboration pattern that strengthens defensibility positioning: programme artefacts shared with capture, joint pursuit-team participation, contracting-officer-relationship maintenance. Examples of capture narratives that elevated a Federal IT PM to Senior PM and how to document the partnership for the programme director.
Module 7. Federal-specific overlays: ATO, FedRAMP, FISMA, RMF
Federal IT compliance is heavy: ATO (Authority to Operate) sign-offs, FedRAMP (Federal Risk and Authorization Management Program) for cloud, FISMA (Federal Information Security Modernization Act) for system security, RMF (NIST Risk Management Framework) for risk-based authorisation, and CMMC for defence supply chain. The compliance overlays that strengthen the programme narrative as regulator-aware federal leadership. How to position compliance rigor as PM-grade IP the programme director cites in recompete defence.
Module 8. Cross-engagement leverage
Reusable Federal IT PM practices that scale across programmes: ATO-acceleration playbooks, agile-at-scale templates for federal cadence, AI-augmented delivery patterns for federal environments, customer-satisfaction maintenance protocols, stakeholder-management cadences. The leverage pattern that signals programme-authorship leadership rather than single-contract coverage. How to convert delivered programme work into published practice the programme director cites in rebalancing defence.
Module 9. Recompete preparation
Recompete reads the programme-state artefacts: past performance scoring, customer-satisfaction surveys, contract-modification capture rate, key-personnel continuity, and price-to-win analysis. The recompete-preparation cadence (24 months out: artefacts; 18 months out: capture coordination; 12 months out: solutioning; 6 months out: proposal) and how PM authorship across the cycle protects PM seats and produces winning recompete narratives. Three worked recompete examples.
Module 10. Scope statement: PM vs Senior PM / Programme Director
Two overlapping seats with different scopes. PM scope covers programme delivery, capture support, IP authorship at programme level. Senior PM scope adds programme-line ownership, succession sponsorship, cross-programme leverage. Programme Director scope adds practice-area P&L, recompete pursuit ownership, and federal-vertical-cabinet participation. The scope statement that puts you in the Senior PM and Programme Director track defensibly.
Module 11. Promotion mechanics inside federal IT delivery
Internal path from PM to Senior PM to Programme Director. The promotion artefact (programme strategy, agency-client relationship record, recompete-win contribution, federal-compliance leadership) and the cycle calendar (year-end performance review, capture-tied promotion review, federal-vertical cabinet announcement). What gets a PM shortlisted, what blocks a PM who is otherwise qualified, and how to time your move with the programme director's succession plan.
Module 12. Your 90-day move to programme-authorship framing
Day-by-day plan with daily artefacts. Days 1-7: programme strategy scaffold drafted from your programme inventory and KPI baseline. Days 8-21: stakeholder map v1 completed with agency-client sponsorship statuses confirmed. Days 22-45: quarterly artefact v1 delivered to programme director. Days 46-60: programme-line ownership conversation. Days 61-90: Senior PM conversation scheduled with federal-vertical sponsor identified in module 11.
How this addresses your situation
Specific modules that map to what you said you are dealing with.
Modules 1 and 2 cover the diagnostic.
Modules 3 to 5 produce the three artefacts.
Modules 6 to 9 cover capture cadence, federal compliance, leverage, and recompete prep.
Modules 10 to 12 cover scope, promotion, and 90-day execution.
FAQ
Will the programme director actually forward my quarterly artefact?
Module 5 is built around the format programme directors forward.
What if my contract vehicle does not support programme scope?
Module 9 covers that case.
Why pay for this instead of reading free PMI content?
Free content covers technique.
Is Senior PM actually open?
Module 11 covers that diagnostic.
What is in the implementation playbook for me specifically?
A draft programme strategy; a draft stakeholder map; a 90-day plan with conversations against your programme director.
