Largely agreed. The tit-for-tat that can happen where positions get filled on programs having little to do with the FFRDC they're staffed under is a problem and it makes MITRE a target for other contractors who will complain to congress about, etc. It's an existential issue for them.
I've noticed federal agencies twist themselves into knots to try to get MITRE to staff something, and jump through the hoops, and really stretch the FFRDC charter, precisely because staffing anyone in the government is a shit show. I think the percieved value is a good chance of someone who isn't useless in the role and some stability.
I don't know who's fault that is, but I know MITRE hammers the line into PMs heads, you know, you're not a body shop. R&D/prototype work only.
At the same time, portfolio managers would be rewarded for forging new partnerships and getting new projects awarded via the FFRDC, even if they were kind of BS beyond a nice slide deck. Having projects to staff those PhDs on and getting kudos from the sponsors is what matters for advancement so...
I think we are pretty much in agreement. It really doesn't help how much the government is willing to stretch the definitions of R&D and System Engineering either.
I've noticed federal agencies twist themselves into knots to try to get MITRE to staff something, and jump through the hoops, and really stretch the FFRDC charter, precisely because staffing anyone in the government is a shit show. I think the percieved value is a good chance of someone who isn't useless in the role and some stability.
I don't know who's fault that is, but I know MITRE hammers the line into PMs heads, you know, you're not a body shop. R&D/prototype work only.
At the same time, portfolio managers would be rewarded for forging new partnerships and getting new projects awarded via the FFRDC, even if they were kind of BS beyond a nice slide deck. Having projects to staff those PhDs on and getting kudos from the sponsors is what matters for advancement so...
Ehhhhh.