What do all the org project enabling processes take as an input?
All the organizational project-enabling processes take the organization strategic plan as an input
What is something important that LCMM’s activities include that you might forget?
Actually establishing a LCMM process
What are inputs and outputs for LCMM you might forget?
It gets a couple inputs from QM and the organization tailoring strategy from TLR. Its outputs go to MEAS (org process performance measures needs/data), and to Control (basically OPAs)
What inputs and outputs for INFRAM are ones you’d forget?
IFRAM gets infrastructure needs from both PM and PP. Its outputs (org. infrastructure and project infrastructure) to the organization and the project(s) are enablers to both.
What inputs and outputs of PM might you miss?
PM gets supply strategy from SUP (note there is no similar input from ACQ). It also gets project status reports from PAC. Distinct outputs are project direction to PP and PAC, org lessons learned to KM, project portfolio to PP/HRM.
What I/Os of KM might you miss?
KM has pretty predictable inputs and outputs. Key inputs are both org lessons learned from PM and project lessons learned from PAC; the key output is the KM system which is then an enabler.
What Tailoring IPOs might I miss?
Tailoring primarily takes the life cycle models from LCMM, and outputs both org and project tailoring strategies (LCMM and PP). The activity I’m most likely to forget is “Take due account of the life cycle structures recommended or mandated by standards.”
What ACQ actvities might I miss?
- Establish and maintain an agreement
- Monitor the agreement
- Accept the product or service
What ACQ I/Os might I miss?
- Inputs : Acquisition need from PP and Enabling System Requirements from all the process on the bottom and right half of the V. You also get acquisition replies and acquired systems from SUP.
- Outputs :
- Acq strategy [PP]
- Request for supply [SUP]
- Acquisition agreement [Control]
- Accepted System or system element [INT]
- Acquisition payment [SUP]
What SUP activities might I miss?
- Establish and maintain an agreement
- Execute the agreement
- Deliver and support the product or service
What SUP inputs might I miss?
- Request for supply [ACQ]
- Supply Payment [ACQ]
- Validated system [VAL]
- Disposed system [DISP]
Which SUP outputs might I miss?
- Supply strategy [PM]
- Supply response [ACQ - Acquisition reply] and [PP]
- Supply agreement [Control]
- Supplied system [ACQ – Acquired system]
- Supply report [PAC]
- Supply record [KM]
What is a RM activity I may miss?
Manage the Risk Profile
What is it from all the the other life cycle processes that could be inputs into CM?
CIs generated by any other life cycle process
Where do major, specific outputs of the TM processes almost always go?
PAC
What might I miss about QA’s inputs?
None of them come from the technical processes, not even from verification or validation.
Where do CRs from PAC go?
Into CM and INFOM
What about life cycle concepts/constraints could I miss?
- Life cycle concepts (i.e. operations concept, disposal concept, support concept) get developed in BMA (preliminary) and SNRD, and then serve as inputs to all technical processes thereafter.
- Life cycle constraints are generated by technical processes on the bottom and right side of the V, and they are inputs to everything in the V “left” of the processes that generate them. They are worded in the outputs as X constraints where X is the name of the TP
How does the RVTM trace through the life cycle?
- Initial version gets created in SNRD
- Updated in SRD
- Then is an input to VER, where the final version of it comes back as an input to SRD
- Final RVTM is an input into VAL
Trace MOEs/MOPs/TPMs through the life cycle
- Preliminary MOE needs/data get generated in BMA and finalized in SNRD
- MOP needs and data are generated in SRD. Note: there are no preliminary MOPs
- TPM needs and data are generated in a preliminary version in AD, finalized in DD.
- MOE/MOP/TPM needs and data are all inputs into MEAS
What are source documents?
Source documents are external documents relevant to the particular stage of procurement activity for the system of interest. Inputs into PP, BMA, and SNRD.
What’s the trace for Project Constraints through the life cycle?
Project Constraints get generated by Project Planning, but are only inputs into BMA and SNRD
How do the various traceabiities (e.g. design traceability, implementation traceability) evolve through the V?
In the left side and bottom of the V, traceabilities are bi-directional and generally from/to before/after. E.g. for IMPL: Design traceability (from the predecessor process) is an input to IMPL. Implementation traceability flow both back to DD and forward to INT.
What is a key input from ACQ to INT?
Accepted system
