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 general management technique used to determine whether a particular work can be accomplished by the project team or must be purchased from outside sources.






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






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






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






5. Quantities to be performed for each specific category - and can be used to estimate activity durations






6. Used to rate or score seller proposals






7. The conclusion of a project phase is marked by a review of both key deliverables and project performance till date to determine if the project should continue into its next phase and detect and correct errors cost-effectively. These phase end reviews






8. Determining which risks may affect the project and documenting their characteristics.






9. Documentation resulting from project activities. These files may also maintain records of other projects that are detailed enough to aid in developing cost estimates.






10. Documents how requirements will be analyzed - documented - and managed throughout the project






11. Factors that - for planning purposes - will be considered true - real or certain.






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






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






14. A modification of a logical relationship that directs a delay in the successor activity.






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






16. It shortens the project schedule without changing the project scope - in order to meet schedule constraints - imposed dates - or other schedule objectives. -. This technique includes crashing and fast tracking.






17. Calculates the theoretical early start and finish dates - and late start and finish dates - for all activities without regard to any resource limitations. This is done by performing a forward and backward pass analysis through the schedule network.






18. The process of confirming human resource availability and obtaining the team necessary to complete project assignments.






19. The total amount of time that a schedule activity may be delayed from its early start without delaying the project finish date - or violating a schedule constraint. Calculated using the critical path method technique and determining the difference be






20. It can include correspondence - memos - meeting minutes - and documents describing the project.






21. A partially complete document in a predefined format that provides a defined structure for collecting - organizing - and presenting information and data.






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






23. Repository that provides for collection - maintenance - and analysis of data gathered and used in the risk management process. Use of this database assists risk management throughout the organization and - over time - forms the basis of a risk lesson






24. Modifications to the cost estimation prepared for the project






25. Activities specifically taken by management and team members to help individual team members work together effectively - thereby improving team performance






26. Measuring - examining and testing undertaken to determine whether results conform to requirements; also called reviews - product reviews - audits - and walkthroughs






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






28. Dependencies determined by the Project Management Team; involve a relationship between project activities and non-project activities (i.e. - dependencies on issues that are beyond the scope of the project). These dependencies are outside the project






29. Involves developing a better understanding of the product of the project






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






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






32. Documents the characteristics of the product - result - or service which the project is undertaken to create.






33. Describes the processes required to make the most effective use of the people involved with the project. It includes developing the human resource plan - acquiring the project team - developing the project team - and managing the project team.






34. The process of analyzing activity sequences - durations - resource requirements - and schedule constrains to create the project schedule






35. An analytical technique used to determine the basic underlying reason that causes a variance or a defect or a risk. Root cause may underlie more than one variance or defect or risk. Root cause analysis is done as part of corrective action - Helps ide






36. A management control point where the resource plans - scope - schedule and actual cost are integrated and compared to earned value for performance measurement.






37. Descriptions of which resources will be available at what times and in what patterns necessary for schedule development






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






39. Describes the processes required to ensure timely and appropriate generation - collection - dissemination and ultimate disposition of project information. It includes identifying stakeholders - planning communication - distributing information - mana






40. The state - quality - or sense of being restricted to a given course of action or inaction. An applicable restriction or limitation - either internal or external to a project - which will affect the performance of the project or a process.






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






42. Process of implementing risk response plans - tracking identified risks - monitoring residual risks - identifying new risks - and evaluating risk process effectiveness throughout the project.






43. A method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it.






44. Process to monitor the status of the project to update the project budget and manage changes to the cost baseline.






45. Complete set of indexed contract documentation - including the closed contract - that is prepared for inclusion with the final project files






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






47. The process to develop an approximation (estimate) of the monetary resources needed to complete project activities.






48. Generally used when considerations like technical approach and technical skills are paramount in source selection






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






50. Effect on project objectives if the risk event occurs.