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. Technique to evaluate the degree to which data about risks is useful for risk management.






2. Project team must measure itself periodically against the expectations of those outside the project.






3. It is used to identify stakeholders that can provide information on detailed project and product requirements. It contains the following information regarding the identified stakeholders: identification information (name - designation - location - co






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






5. Allows for probabilistic treatment of both network logic and activity duration estimates






6. An organizational placement strategy where the project team members are physically located close to one another in order to improve communication - working relationships - and productivity.






7. Allow for non-sequential activities (e.g. Loops or Conditional Branches); e.g. - GERT(Graphical Evaluation and Review Technique) and System Dynamics






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






9. Projects are frequently divided into better manageable components or subprojects. Subprojects are often contracted to an external enterprise or another functional unit in the performing organization.






10. Describes the processes required to acquire goods and services from outside the project team. It includes planning procurements - conducting procurements - administering procurements - and closing procurements.






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






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






13. It includes the processes required to ensure timely and appropriate generation - collection - dissemination - storage - retrieval - and ultimate disposition of project information.






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






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






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






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






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






19. Factors that limit a buyer's options. E.g. - funds availability






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






21. Requests to expand or reduce project scope - modify policies/ processes/plans/procedures/costs and - if approved - can affect budgets or revise schedules. These change requests are processed through the Perform Integrated Change Control process.






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






23. The expected cost needed to complete all the remaining work for a schedule activity - work break down structure component - or the project.






24. Involves payments (cost reimbursements) to the seller for all legitimate actual costs incurred for completed work - plus a fee representing seller profit






25. Special category of revised cost estimates to an approved cost baseline.






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






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






28. Document that formally authorizes a project. Provides project manager with the authority to apply organizational resources to project activities.






29. A structured review of the seller's progress to deliver project scope and quality - within cost and on schedule - as compared to the contract.






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






31. Describes how project scope will be managed and how scope changes will be integrated into the project. It should also include an assessment of the expected stability of the project scope






32. Testing identified assumptions against two criteria: assumption stability and consequences on the project if the assumption is false.






33. Defines the procedures by which project scope can be changed; includes paperwork - tracking systems and approval levels necessary for authorizing changes.






34. For many procurement items - the procuring organization may elect to either prepare its own independent estimate - or have an estimate of costs prepared by an outside professional estimator - to serve as a benchmark on proposed responses.






35. Defines the process by which the procurement can be modified. It includes paperwork - tracking systems - dispute resolution procedures - and approval levels necessary for authorizing changes.






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






37. The process of making relevant information available to project stakeholders in a timely manner - as planned. Performed throughout the entire project life cycle and in all management processes.






38. Judgment provided based upon expertise in an application area - knowledge area - discipline - industry - etc. as appropriate for the activity being performed. Such expertise may be provided by any group or person with specialized education - knowledg






39. Process of identifying the specific actions to be performed to produce the project deliverables.






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






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






42. Process of defining and documenting stakeholders' needs to meet the project objectives






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






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






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






46. Any form of schedule network analysis in which scheduling decisions are driven by resource constraints.






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. Bring together prequalified stakeholders and subject matter experts to learn about their expectations and attitudes about a proposed product - service - or result






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






50. Used to solicit proposals from prospective sellers