Test your basic knowledge |

Subjects : certifications, capm
Instructions:
  • Answer 50 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. A modification of a logical relationship that directs a delay in the successor activity.






2. Terms used when the source selection decision will be based on price






3. Process of redefining the cost performance/schedule/performance measurement/technical baseline. If cost variances are severe - re-baselining is needed to provide a realistic measure of performance.






4. The process in which the estimated costs of individual activities or work packages are aggregated to establish an authorized cost baseline.






5. Process of formally authorizing a new project or the next phase of an existing project; links the project to the ongoing work of the performing organization






6. Process of redefining the cost performance/schedule/performance measurement/technical baseline. If cost variances are severe - re-baselining is needed to provide a realistic measure of performance.






7. A formal or informal approach to obtain information from stakeholders by talking to them directly






8. Describes the processes required to ensure that the project is completed within the approved budget. It includes estimating the cost - determining the budget - and controlling the costs.






9. If the performing organization does not have a formal contracting group - then the project team will have to supply both the resources and expertise to support procurement activities






10. Schematic displays of the logical relationships (dependencies) among the project schedule activities; always drawn from left to right to reflect project work chronology






11. Process of estimating the type and quantities of resources like materials - people - equipment - or supplies required to perform each project activity






12. Technique to evaluate the degree to which data about risks is useful for risk management.






13. Broader view of Project Cost Management - whereby other than project costs - we consider the effect of project decisions on the cost of using the project's product.






14. Any modification to the agreed upon project scope as defined by the approved WBS






15. An uncertain event or condition that - if it occurs - has a positive or negative effect on the project objective.






16. Forecasts of potential project schedule and cost results listing the possible completion dates or project duration and costs with their associated confidence levels.






17. Approved modifications to the project schedule that are used to manage the project






18. A provision in the project management plan to mitigate cost and/or schedule risk. Often used with a modifier to provide further details on what types of risk are meant to be mitigated.






19. Process of defining how to conduct risk management activities for a project.






20. Also called risk symptoms or warning signs - they are indications that a risk has occurred or is about to occur. They may be discovered in the risk identification process and watched in the risk monitoring and control process.






21. The document that describes the communication 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 each type of communica






22. The calculated projection of cost performance that must be achieved on the remaining work to meet a specified management goal - such as the budget at completion (BAC) or the estimate at completion (EAC). It is the ratio of 'remaining work' to the 'fu






23. Used to generate - classify - and prioritize product requirements. Some methods used to reach group decisions are: unanimity - majority - plurality - and dictatorship.






24. Process of monitoring the status of the project and product scope and managing changes to the scope baseline.






25. The process of determining project stakeholders' information needs and defining a communication approach.






26. An estimating technique that uses parameters from a previous - similar project as the basis for estimating the same parameter/measure for a future project. Frequently used to estimate project duration when there is a limited amount of detailed inform






27. Structured review of the project plans and assumptions - prior project files - contracts - and other information.






28. Description of the product of the project - provides important information about any technical issues or concerns that would need to be considered during procurement planning






29. A general data gathering and creativity technique that can be used to identify risks - ideas - or solutions to issues by using a group of team members or subject matter experts which data can be addressed later in Perform qualitative and quantitative






30. Action taken to bring a defective or nonconforming item into compliance with requirements or specifications. It is a frequent cause of project overruns in most application areas.






31. Describes how risk management will be structured and performed on the project.






32. A schedule network analysis technique used to determine the amount of scheduling flexibility on various logical network paths in the project schedule network - and to determine the minimum total project duration. Early start and finish dates are calc






33. A functional organization has a hierarchy in which every employee has one clear superior. Staff members are grouped by areas of specialization. Functional organizations may still have projects - but the perceived scope of the project is defined by th






34. Structured review of the procurement process originating from the Plan Procurements process through Administer Procurements process. Objective is to identify successes and failures that warrant recognition in the preparation or administration of othe






35. A deliverable is a unique - tangible and verifiable work/product. Each project phase is marked by the completion of one or more deliverables.






36. An authorized time-phased budget at completion (BAC) used to measure - monitor - and control overall cost performance on the project. Developed as a summation of the approved budgets by time period and is typically displayed in the form of an S-curve






37. Changing the project management plan to eliminate the threat entirely.






38. A table that links requirements to their origin and traces them throughout the project life cycle






39. A collection of formal (note: not informal) documented procedures - which defines how the documentation and project deliverables will be managed - changed and approved.






40. It consists of tools and techniques used to gather - integrate and disseminate the outputs of project management processes. Supports all aspects of the project from initiating through closing - and can include both manual and automated systems.






41. Includes identified risks - risk owners - results of Perform qualitative risk analysis process - agreed upon response strategies - etc.






42. 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.






43. An estimating technique that uses a statistical relationship between historical data and other variables to calculate an estimate for activity parameters - such as scope - cost - budget - and duration. An example for the cost parameter is multiplying






44. Process of assessing and combining the impact and the likelihood of identified risks. Prioritizes risks according to their potential effect on project objectives for further analysis or action.






45. Documented direction for executing the project work to bring expected future performance of the project work in line with the project management plan.






46. Probability that a risk will occur.






47. The planned dates to perform schedule activities and the planned dates for meeting schedule milestones. Includes planned start and finish dates for the project's activities - milestones - work packages - planning packages - and control accounts. This






48. Integrates scope - cost (or resource) - and schedule measures to help the project management team assess project performance.






49. Lists or files maintained with information on prospective sellers. These lists will generally have information on relevant past experience and other characteristics of the prospective sellers






50. Defines what kinds of competencies are required from what kind of individuals or groups and in what time frames.