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






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






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






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






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






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






7. A mathematical technique to forecast future outcomes based on historical results. This is performed using run charts.






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






9. It compares cost performance over time - schedule activities or work packages overrunning and under running the budget - and estimated funds needed to complete work in progress.






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






11. Deliverable- oriented grouping of project components that organizes and defines the total scope of the project - work not in the WBS is outside the scope of the project.






12. Project team accepts the risk - i.e. team decides not to change the project plan to deal with the risk - or is unable to identify any other suitable response strategy.






13. Involves immediate corrective or preventive action as a consequence of quality control measurements.






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






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






16. Records of previous project results that can be used to identify risks.






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






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






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






20. Probability that a risk will occur.






21. Processes and procedures developed for the closing or canceling of projects.






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






23. Describes how individual requirements meet the business need for the project.






24. Process of managing procurement relationships - monitoring contract performance - ad making changes and corrections as needed.






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






26. Process of identifying and documenting relationships among the project activities. Sequencing can be performed by using project management software or by using manual or automated techniques.






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






28. Any numbering system used to uniquely identify each component of the work breakdown structure.






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






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






31. Responses to emerging risks that was previously unidentified or accepted. These were not planned in advance of the occurrence of the risk event.






32. It is a tool and technique which is used to determine the information needs of the project stakeholders. This is a key component for planning the project's actual communications. It would assist in determining and limiting who will communicate with w






33. Reduce the probability and/or consequence of an adverse risk event to be within acceptable threshold limits.






34. Process of obtaining seller responses - selecting a seller - and awarding a contract






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






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






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






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






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






40. Describes the processes concerned with identifying - analyzing - and responding to project risk. It includes planning risk management - identifying risks - performing qualitative risk analysis - performing quantitative risk analysis - planning risk r






41. This is done to take care of risks that were not identified in the risk response plan - or their impact on objectives is greater than expected.






42. Formal and informal policies that are required for project plan development. Organizational policies include quality management - personnel administration and financial controls.






43. They possess a blend of functional and projectized characteristics. Weak matrices maintain many of the characteristics of a functional organization - and the Project Manager's role is more that of a coordinator or expediter than that of a manager. Si






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






45. A group of documented procedure used to apply technical and administrative direction and surveillance to: a) Identify and document the system's functional and physical characteristics; b)Control any changes to such characteristics; c) Record and repo






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






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






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






49. Hybrid type of contractual agreements that contain aspects of both cost-reimbursable and fixed- price contracts. Some characteristics: · Open-ended - i.e. - full value of the agreement and the exact quantity of items to be delivered may not be define






50. Risk Audits examine and document the effectiveness of risk responses in dealing with identified risks and their root causes - as well as the effectiveness of the risk management process.