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

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

3. Process of developing options and actions to enhance opportunities and to reduce threats to project objectives. Includes the identification and assignment of individuals to take responsibility for each agreed-to and funded risk response.

4. A general data gathering and creativity technique that can be used to identify risks - ideas - or solutions to issues by using a group of team members or subject matter experts which data can be addressed later in Perform qualitative and quantitative

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

6. The process of identifying all people or organizations impacted by the project and documenting relevant information regarding their interests - involvement - and impact on project success.

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

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

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

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

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. Describes the need - justification - requirements - and current boundaries for the project.

13. Meetings with all prospective sellers and buyers prior to submittal of a bid or proposal. Used to ensure that all prospective sellers have a clear and common understanding of the procurement - and that no bidders receive preferential treatment.

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

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

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

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

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

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

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

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

22. This involves calculating the theoretical early and late start and finish dates for all project activities without regard to any resource pool restrictions.

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

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

25. Describes the procurement item in sufficient detail to allow prospective sellers to determine if they are capable of providing the products - services - or results.

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

27. A formal or informal approach to obtain information from stakeholders by talking to them directly

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

29. Considers the characteristics of those prospective staff who are available to join the project team.

30. Meetings that are regularly scheduled to exchange and analyze information about the project and its performance.

31. A process of systematically gathering and analyzing quantitative and qualitative information to determine whose interests should be taken into account throughout the project. It identifies the interests - expectations - and influence of the stakehold

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

33. The process to identify and document project roles - responsibilities - and required skills - report relationships - and create a staffing management plan.

34. Provide a structure that ensures a comprehensive process of systematically identifying risks to a consistent level of detail and contributes to the effectiveness and quality of the Identify Risks process. They include categories like technical - exte

35. Terms used when the source selection decision will be based on price

36. Dependencies that are contractually required or those inherent in the nature of the work. Often involve physical limitations.

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

38. Defines what kinds of competencies are required from what kind of individuals or groups and in what time frames.

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

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

41. The process of approximating the number of work periods needed to complete individual activities with estimated resources

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

43. A technique for estimating that applies a weighted average of optimistic - pessimistic - and most likely estimates when there is uncertainty with the individual activity estimates.

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

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

46. A subdivision (fragment) of a project schedule network diagram - used to illustrate or study some potential or proposed schedule condition - such as changes in preferential schedule logic or project scope.

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

48. Mutually binding legal agreement that obligates the seller to provide the specified products - services - or results - and obligates the buyer to compensate the seller.

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

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