Home / Aerospace and defense program execution
Most program problems are not unique. The schedule that looks complete but has no real critical path, the customer request absorbed without a price, the closeout that stalls on missing documents: these repeat across aerospace and defense programs. These guides explain how each one works in practice, written by people who run programs rather than write about them.
How the guides are organized
The guides follow the life of a program. Starting a program covers the structure you need before the first milestone is at risk. Recovering a program covers what to do when the program is already late, over budget or at odds with the customer. Closing a program covers the work that turns a finished design into accepted, documented, producible hardware. Choosing help covers the decision many program leaders face first: what kind of outside support actually fits. Each guide stands on its own, so start with the one that matches where your program is today.
Behind all of them is one idea. If clear boundaries for success are not established at the beginning, made visible and executed against, the program will not succeed. Requirements, scope, schedule, cost, authority, accountability, communication, customer requests, risk and the definition of completion all have to be written down, agreed and kept in view.
Starting a program
These guides cover the structure a new program needs: a charter, a schedule the team believes, a baseline that survives review and supplier quality planning that starts early. For the full service, see front-end planning.
- Writing a project charter. What a charter for an engineered program should establish, from requirements and definition of success to payment milestones, risks, roles and escalation, and why it should be signed in the first one to two weeks.
- Building an integrated master schedule that works. How to build a schedule with real input from the people doing the work, so the critical path it shows is the one the program actually follows.
- Preparing for an integrated baseline review. What reviewers look for in the technical, schedule and cost baseline, and how to prepare control account managers to answer with confidence.
- EVMS and EIA-748 for defense contractors. What an earned value management system has to do, when EIA-748 applies, and how to keep earned value honest rather than a reporting exercise.
- AS9145 APQP and PPAP in practice. How advanced product quality planning and production part approval work on aerospace programs, and where suppliers most often underestimate the effort.
Recovering a program
These guides are for programs already in trouble. The common thread is establishing the real requirements and current status before building any new plan. For the full service, see program recovery.
- The requirements-to-work assessment. How to compare what the team is actually working on with what the contract requires, and why this is usually the first step in any recovery.
- Substantiating scope-change claims. How to trace configuration changes back to informal customer requests or contractual requirements and use your own financial data to show the real cost and schedule impact.
- Why aerospace and defense programs run late. The root causes behind most late programs, from unstable requirements to uncontrolled customer requests, and the early warning signs worth trusting.
- What a DCMA 14-point schedule assessment really checks. The fourteen schedule health checks, what each is meant to catch, and why passing them does not by itself make a schedule executable.
- How to build a schedule recovery plan that holds. How to build a recovery plan from real remaining work, so the new date is one the team and the customer can both believe.
- Supplier recovery on aerospace programs. How to find the real constraint at a late supplier and recover the parts your critical path depends on.
Closing a program
Closeout is where unfinished work from earlier phases surfaces. These guides cover the deliverables that most often hold up acceptance and production. For the full service, see project closeout.
- Delivering a complete technical data package. What a technical data package must contain for the customer to accept it, and where packages most often fall short.
- First article inspection under AS9102. How first article inspection works, what the forms have to show, and how to finish a stalled package.
- Configuration management through closeout. How to reconcile as-designed against as-built and close out a change backlog after the original engineers have moved on.
- Transitioning an aerospace program to production. What has to be true before a development program hands off to production, and how to catch the problems that usually appear in the first builds.
Choosing help
Before you bring in outside support, it helps to be clear on what kind of help the program needs. These comparisons explain the tradeoffs honestly.
- Program management firm or staffing agency? A staffing agency fills a seat; a program management firm is accountable for the program. How to tell which your program needs.
- Embedded execution or advisory consulting? Where advisors fit, where an embedded team fits, and what each actually costs a program that is already behind.
- Contract program manager or full-time hire? When a program needs someone now and when it needs someone permanent, with the real tradeoffs in speed, cost and risk.
Three questions every guide comes back to
Whatever phase your program is in, everyone on the team should be able to answer three questions: Where are we? Where are we going? What has to happen next to get there? The charter, the integrated schedule, the risk process and the communication rhythm described in these guides all exist to keep those answers clear. When the answers get vague, the program is drifting, and it is time to reset the boundaries.
When a guide is not enough
Guides explain the method. Applying it to a live program, with a real customer, a real contract and a team under pressure, is a different job. If you are reading these because your program is at risk, schedule a call and we will talk about your program specifically.
Questions
Common questions
Who are these guides written for?
Program managers, engineering managers, general managers and executives at aerospace, defense and maritime companies. Some readers are setting up a new program and want to get the structure right from the start. Others are dealing with a program that is late, over budget or in a difficult position with the customer. The guides assume you know your product and explain the program management practice around it.
Where should I start if my program is already late?
Start with the requirements-to-work assessment guide. On most troubled programs the first real finding is that the team is working on things the contract does not require, often in response to informal customer requests, while some required work is not moving. Once requirements and current status are established, the schedule recovery plan and supplier recovery guides show how to build and execute a credible path to completion.
Do I need all of these practices on every program?
No. The structure should fit the program, the customer and the level of risk. A smaller commercial program may need a charter, an integrated schedule and a weekly rhythm, but not a full earned value management system. A large defense contract may require EIA-748 compliance and formal baseline reviews. The guides explain when each practice applies so you can scale the structure to the program.
Are the guides based on real program experience?
Yes. They are written from the practice of running aerospace, defense and maritime programs, including engine controls, fuel pumps, gearboxes, wing programs, ship systems and defense electronics. Where a guide references a standard, such as AS9102, AS9145 or EIA-748, it explains how the standard works in practice, including what usually goes wrong, rather than restating the standard itself.
What is the difference between the guides and your services?
The guides explain the methods. Our services apply them to your program, with a Program Manager who owns time, money, strategy and major stakeholder communication, and Project Engineers where the program needs them, working inside your systems with your team. If a guide describes a problem you are facing now, a short call is usually the quickest way to see whether outside help makes sense.
Have a question that is not here? Ask Holly on a short call
