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. It can include correspondence - memos - meeting minutes - and documents describing the project.






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






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






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






5. Structured method to guide the project team during development of project plan. Standard forms and templates or even complicated simulations may be used.






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






7. Involves setting a fixed total price for a defined product or service to be provided.






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






9. The work that must be done to deliver a product with the specified features and functions






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






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






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






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






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






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






16. Includes the processes required to purchase or acquire products - services - or results needed from outside the project team.






17. The process of collecting and distributing performance information - including status reports - progress measurements - and forecasts to stakeholders.






18. A formal - approved document used to define how the project is executed - controlled and monitored. It can either be at a detailed or high level and may contain one or more subsidiary plans.






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






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






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






22. Persons or organizations who are actively involved in the project or whose interests may be positively or negatively affected by the performance or completion of the project. They may also exert influence over the project - its deliverables - and the






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






24. Risks that arise as a direct result of implementing a risk response.






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






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






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






28. Risks that remain after planned responses have been implemented - as well as those that have been deliberately accepted.






29. Clarify the structure - requirements and other terms of the purchases so that mutual agreement can be reached prior to signing the contract.






30. Formal written notice from a person or organization responsible for contract administration - informing that the contract has been completed.






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






32. Activities should have a coding structure to allow sorting and/or extractions based on different attributes assigned to the activities.






33. The policies - guidelines - or procedures that govern the recruitment of staff.






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






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






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






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






38. Used to identify project and product requirements; some of the techniques used are: Brainstorming - Nominal group technique - The Delphi technique - Idea/mind mapping - and Affinity diagram.






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






40. Incurred for the exclusive benefit of the project (e.g. - salaries of full-time project staff).






41. Seller is a subcontractor - vendor - or supplier - who will typically manage the work of the project. Buyer is the customer who has outsourced work to the seller.






42. This compares technical accomplishments during project execution with the project management plan's schedule of technical achievement.






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






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






45. Focused sessions that bring key cross-functional stakeholders together to define product requirements






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






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






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






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






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