Test your basic knowledge |

PMBOK Definitions: Outputs And Inputs

Instructions:
  • Answer 32 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. <Process Input> - Any item - whether internal or external to the project that is required by a process before that process proceeds. May be a output from a predecessor process.






2. <Output / Input> - A change request that has been processed through the integrated change control process and approved.






3. <Output / Input> - The expected cost needed to complete all the remaining work for a shcedule activity - work breakdown structure component - or the project. See also earned value technique and estimate at completion.






4. <Output / Input> - The expected total cost of a schedule activity - a work breakdown structure component - or the project when the defined scope of work will be completed. The EAC may be calculated based on performance to date or estimated by the pr






5. <Output / Input> - Any unique and verifiable product - result - or capability to perform a service that must be produced to complete a process - phase - or project. Often used more narrowly in reference to an external deliverable - which is a delive






6. <Output / Input> - The documents utilized in bid and proposal activities - which include the buyer's invitation for Bid - invitation for Negotiations - Request for Information - Request for Quotation - Request for Proposal and seller's responses.






7. <Output / Input> - A documented tabulation of schedule activities that shows the activity description - activity identifier - and a sufficiently detailed scope of work description so project team members understand what work is to be performed.






8. <Output / Input> - A formal - approved document that defined how the project is executed - monitored - and controlled. It may be a summary or detailed and may be composed of one or more subsidiary management plans and other planning documents.






9. <Output / Input> - Information and data - on the status of the project schedule activities being performed to accomplish the project work - collected as part of the direct and manage project execution processes. Information includes: status of deliv






10. <Output / Input> - The quality management plan describes how the project management team will impliment the performing organization's quality policy. The quality mangement plan is a component or a subisdiary plan of the project management plan.






11. <Output / Input> - The document that establishes criteria and the activities for developing and controlling the project schedule. It is contained in - or is a subsidiary plan of - the project management plan.






12. <Output / Input> - A contract is a mutually binding agreement that obligates the seller to provide the specified product or service or result and obligates the buyer to pay for it.






13. <Output / Input> - Documents and presentations that provide organized and summarized work performance information - earned value management parameters and calculations - and analyses of project work progress and status.






14. <Output / Input> - The narrative description of the project scope - including major deliverable - project assumptions - project constraints - and a description of work - that provides a documented basis for making future project decisions and for co






15. <Output / Input> - The document that describes how the proejct scope will be defined - developed - and verified and how the work breakdown structure will be created and defined - and that provides guidance on how the proejct scope will be managed an






16. <Output / Input> - The document that describes: the communications needs and expectations for the project; how and in what format information will be communicated; when and where each communication will be made; and who is responsible for providing






17. <Output / Input> - The document containing the results of the qualitative risk analysis - quantitative risk analysis - and risk response planning. The risk register details all identified risks - including description - category - cause - probabilit






18. <Output / Input> - The document describing how project risk management will be structured and performed on the project. It is contained in or is a subsidiary plan of the project management plan. Information in the risk management plan varies by appl






19. <Output / Input> - The document that sets out the format and establishes the activities and criteria for planning - structuring - and controlling the project costs. The cost management plan is contained in - or is a subsidiary plan of - the project






20. <Output / Input> - A document that graphically depicts the project team members and their relationships for a specific project.






21. <Output / Input> - The document that describes how procurement processes from developing procurement documentation through contract closure will be managed.






22. <Output / Input> - Multiple attributes associated with each schedule activity that can be included within the activity list. Includes activity codes - predecessor activities - successor activities - logical relationships - leads and lags - resource






23. <Output / Input> - Any or all process related assets - from any or all of the organizations involved in the project that are or can be used to influence the project's success. These process assets include formal or informal plans - policies - proced






24. <Output / Input> - The learning gained from the process of performing the project. Lessons learned may be identified at any point. Also considered a project record - to be included in the lessons learned knowledge base.






25. <Output / Input> - Any schematic display of the logical relationships among the project schedule activities. Always drawn from left to right to reflect project work chronology.






26. <Output / Input> - The planned dates for performing schedule activities and the planned dates for meeting schedule milestones.






27. <Output / Input> - A document that describes each component in the work breakdown structure (WBS). For each WBS component - the WBS dictionary includes a brief definition of the scope or statement of work - defined deliverable(s) - a list of associa






28. <Output / Input> - The amount of funds - budget - or time needed above the estimate to reduce the risk of overruns of project objectives to a level acceptable to the organization.






29. <Output / Input> - A document issued by the project initiator or sponsor that formally authorizes the existance of a project - and provides the project manager with the authority to apply organizational resources to project activities.






30. <Output / Input> - A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






31. <Output / Input> - A formally documented change request that is submitted for approval to the integrated change control process.






32. <Output / Input> - Any or all external environmental factors and internal organizational environmental factors that surround or influence the project's success. These factors are from any or all of the enterprises involved in the project - and inclu