Test your basic knowledge |

Subjects : certifications, capm
  • 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. Process of implementing risk response plans - tracking identified risks - monitoring residual risks - identifying new risks - and evaluating risk process effectiveness throughout the project.

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

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

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

5. Factors which - for planning purposes - are considered to be true - real or certain.

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

7. A documented tabulation of schedule activities that shows the activity description - activity identifier - and a sufficiently detailed scope of work description so project team members understand what work is to be performed.

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

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

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

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

12. Policies - guidelines and procedures that can help the project management team with various aspects of organizational planning.

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

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

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

16. Any modification to the contents of the project plan or the supporting details.

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

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

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

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

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

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

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

24. An applicable restriction that will affect the performance of the project/process.

25. Includes the processes that help to estimate - budget - and control costs - so that the project can be completed within the approved budget.

26. The amount of time that a schedule activity can be delayed without delaying the early start date of any immediately following schedule activities.

27. Describes the processes required to ensure that the project satisfies the needs for which it is undertaken. It includes quality planning - performing quality assurance and control.

28. 1. Operations do not have any timelines. Projects are temporary and have finite time duration. 2. Operation's objective is usually to sustain the business. Project's objective is to achieve the target and close the project.

29. Methods used to distribute information to team members and other stakeholders.

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

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

32. Factors that will limit the project management team's options (e.g. - a predefined budget)

33. Process of developing a detailed description of the project and product

34. Charts that are used to show positions and relationships in a graphical format.

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

36. Group of related projects managed in a coordinated way to obtain control and benefits that are not available if managed individually.

37. Process of documenting project purchasing decisions - specifying the approach - and identifying potential sellers.

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

39. Process of formalizing acceptance of the completed project deliverables

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

41. An estimating technique that uses the values of parameters - such as scope - cost - budget - and duration or measure of scale such as size - weight - and complexity - from a previous - similar activity as the basis for estimating the same parameter o

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

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

44. Used to solicit proposals from prospective sellers

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

46. A hierarchically organized depiction of the project organization arranged so as to relate the work packages to the performing organizational units.

47. Describes the need - justification - requirements - and current boundaries for the project.

48. An accepted action performed to bring projected future project performance in line with the project plan. These actions have to be documented.

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

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.