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. Integrates scope - cost (or resource) - and schedule measures to help the project management team assess project performance.

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

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

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

5. Process of changing the schedule baseline. It is done when schedule delays are very severe - and the project schedule has to be completely changed.

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

7. Describes the processes required to ensure that the project is completed within the approved budget. It includes estimating the cost - determining the budget - and controlling the costs.

8. Specify lessons that can be learned from each and every project - even from projects which are failures. They need to be documented. Most companies prefer post-implementation meetings and case studies to document Lessons Learned

9. Predefined approaches to risk analysis and response in some organizations that have to be tailored to a particular project.

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

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

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

13. A schedule compression technique in which cost and schedule tradeoffs are analyzed to determine how to obtain the greatest amount of compression for the least incremental cost. Crashing only works for activities where additional resources will shorte

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

15. They involve measuring value or attractiveness to the project owner. Includes considering the decision criteria and a means to calculate value under uncertainty.

16. Project Simulation uses a model that translates the specified detailed uncertainties of the project into their potential impact on project objectives.

17. Used to rate or score seller proposals

18. It can include correspondence - memos - meeting minutes - and documents describing the project.

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

20. Process of estimating the type and quantities of resources like materials - people - equipment - or supplies required to perform each project activity

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

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

23. The calculated projection of cost performance that must be achieved on the remaining work to meet a specified management goal - such as the budget at completion (BAC) or the estimate at completion (EAC). It is the ratio of 'remaining work' to the 'fu

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

25. Describes the extent to which a risk is known or understood. Measures extent of data available as well as reliability of data.

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

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

28. A general management technique used to determine whether a particular work can be accomplished by the project team or must be purchased from outside sources.

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

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

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

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

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

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

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

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

37. Approved modifications to the project schedule that are used to manage the project

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

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

40. Includes identified risks - risk owners - results of Perform qualitative risk analysis process - agreed upon response strategies - etc.

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

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

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

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

45. A documented list of project team members - their project roles - and communication information.

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

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

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

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

50. The expected total cost of a schedule activity - a work breakdown structure component - or the project when the defined scope of work will be completed.