Description

A focused course, tailored for you

Federal Software Architect's Capability-Authorship Playbook

How a software architect at a federal services firm authors a capability the next recompete cites when portfolio rebalancing reaches architecture.

When portfolio rebalancing reaches federal architecture, software architects without an authored capability read as advisory cost. Architects with one read as the capability the next recompete cites.

$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 services firms running contribution agreements and divestitures rebalance architecture functions in the same operating-model cycle. Software architects who continue producing bespoke advisory work without a published capability are read by the deck as cost. Architects with a capability artefact read as IP.

The architects who survive own a published reference architecture under their byline, a capability statement the next recompete cites, and a weekly architecture-state artefact the programme manager forwards to capture.

The course covers the three artefacts and the 90-day path to capability-authorship framing. Plus a hand-built implementation playbook against your real architecture work.

What you walk away with

A published reference architecture under your byline.
A capability statement the next recompete cites.
A weekly architecture-state artefact the programme manager forwards to capture.
A clean translation from advisory architect to capability-authorship owner.
A defensible answer when the recompete asks which capability the seat owns.
A 90-day plan to land the framing.

The 12 modules

Module 1. Reading federal rebalancing for software architect implications

Federal portfolio rebalancing reorganises architecture functions in the same operating-model cycle. The diagnostic for the Software Architect layer specifically. What 'rebalancing' means at federal software architect level.

Module 2. Advisory architect vs capability-authorship architect

Two structurally different framings of the same Software Architect seat. Advisory architect reads as cost; capability-authorship architect reads as the IP the next recompete cites. The three artefacts that mark the shift.

Module 3. Your published reference architecture

Implementation-ready reference architecture customers can deploy. Components, decisions, trade-offs, the named owner. The artefact that defines Software Architect work at federal scope.

Module 4. Capability statement

Capability statement that the next recompete can adopt verbatim. Worked examples for cloud, data platform, and mission-system capabilities at federal scope.

Module 5. Weekly architecture-state artefact for the programme manager

Format, cadence, content of the weekly architecture-state artefact the programme manager forwards to capture. Three worked examples for federal software architecture workloads.

Module 6. Working with capture, BD, and partner channel

Capability work travels via capture, BD, and partner channel during recompete cycles. The collaboration pattern that strengthens capability-authorship positioning.

Module 7. Federal-specific overlays: ATO, FedRAMP, FISMA

Federal architecture engagement includes ATO, FedRAMP, FISMA, RMF compliance. The overlays that strengthen the capability artefact rather than burying it.

Module 8. Cross-engagement leverage

Reusable software architecture IP across federal contracts. Reference designs, decision records, evaluation frameworks. The patterns that compound across the federal software practice.

Module 9. Customer references

First customer implementation becomes the reference the next recompete cites. The reference-shaping conversation. The case study with your name.

Module 10. Scope statement: Software Architect vs Lead Architect

Two overlapping seats. The scope statement that puts you in the Lead Architect track defensibly.

Module 11. Promotion mechanics inside federal services

Internal path inside federal services architecture. The promotion artefact. The two reviewers who matter.

Module 12. Your 90-day move to capability-authorship framing

Day-by-day plan. Reference architecture target chosen by week one. Reference architecture v1 in front of programme manager by week two. Capability statement adopted by capture by month one. Lead Architect conversation in month three.

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 references.

Modules 10 to 12 cover scope, promotion, and 90-day execution.

What you get with this course

The 12-module course delivered as text plus downloadable templates.
Templates for the reference architecture, the capability statement, and the weekly artefact.
A hand-built implementation playbook generated for your specific work.
Three worked examples of the weekly artefact.
Scripted talking points for the programme manager conversation.

What you will have in hand by Day 1, Week 1, Month 1

Day 1: Reference architecture target chosen.

Week 1: Reference architecture v1 in front of programme manager.

Month 1: Capability statement adopted by capture; weekly artefact running; Lead Architect conversation scheduled.

Before and after

Before

You ship software architect work. Engagements land. The rebalancing is being discussed.

After

Your reference architecture is the document the programme manager points capture to. The capability statement is what the next recompete cites. The weekly artefact lands with the programme manager. The Lead Architect conversation is scheduled.

What happens if you do not address this

Federal rebalancing reorganises architecture within one or two recompete cycles.

Who it is for

For Software Architects, Senior Software Architects, and Lead Architects at federal services firms in portfolio rebalancing cycles.

Who this is NOT for. Commercial software architects. Junior architects. Architects at firms not in active rebalancing.

How it arrives

Text-based course via LMS, plus downloadable templates and the hand-built implementation playbook.

Time investment. Roughly 12 hours of reading and 15 to 20 hours producing your real artefacts.

Why $199 is the right number

Internal federal training is contract-specific. Free architecture content covers technique not federal context. A senior Lead Architect mentor would cover maybe four of these 12 modules informally. $199 buys the focused playbook plus the implementation document for your federal architecture work.

FAQ

Will the programme manager actually forward my weekly artefact?

Module 5 is built around the format programme managers forward.

What if my workload has no formal capability scope?

Module 4 covers that case.

What is in the implementation playbook for me specifically?

A draft reference architecture; a draft capability statement; a 90-day plan with conversations against your programme manager.

30-day money-back guarantee. If after a week of working through the materials this is not what you needed, reply to the receipt email and a full refund is processed. No questions, no forms.

Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.