I just finished Chapter 7 of this book, which used the F/A-18E/F program—from ol' McDonnell right here in St. Louis—as a case study for how to integrate project management and systems engineering via integrated product teams (IPTs). I've never really thought much about the whys and wherefores of IPTs. They're just part of the air that you breathe on large aerospace/defense programs, projects decomposed into functional teams and subteams and so on. I wasn't sure if IPTs are still in style or not—I think we're all agile now—but clearly aerospace companies are putting that in their job postings, so it must still have some currency.
Anyway. You either have access to that book or you don't. But it is drawn heavily from other references that are readily available. If F/A-18E/F is as good of an example of how to integrate systems engineering and program management as the book describes it—ahead of time, under budget, under weight (in a good way)—then it's something worth learning more about, to see how they did it.
- Bailey, E. (1998, April 9). The F/A‐18E/F: An Integrated Product Team (IPT) case study. Institute for Defense Analyses. IDA NS D‐8027. https://www.ida.org/research-and-publications/publications/all/t/th/the-fa18ef-an-integrated-product-team-ipt-case-study
- Bailey, E., Nash, S., & Woolsey, J. (1999, January). Integrated product and process development case study, Development of the F/A‐18E/F. Institute for Defense Analyses. IDA D‐2228. https://apps.dtic.mil/sti/citations/ADA379633
- White, J. W. (1997). Application of new management concepts to the development of F/A‐18 aircraft. Johns Hopkins APL Technical Digest, 18(1), 21–32. https://www.jhuapl.edu/Content/techdigest/pdf/V18-N01/18-01-White.pdf
- Younossi, O., Stem, D., Lorell, M., & Lussier, F. (2005). Lessons learned from the F/A–22 and F/A–18E/F development programs. Rand Corporation. Report MG‐276. ISBN 0‐8330‐3749‐8. https://www.rand.org/content/dam/rand/pubs/monographs/2005/RAND_MG276.pdf