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






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






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






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






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






6. Process of implementing risk response plans - tracking identified risks - monitoring residual risks - identifying new risks - and evaluating risk process effectiveness throughout the project.






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






8. Subdivision of project deliverables into smaller - more manageable components






9. A functional organization has a hierarchy in which every employee has one clear superior. Staff members are grouped by areas of specialization. Functional organizations may still have projects - but the perceived scope of the project is defined by th






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






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






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






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






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






15. It is a tool and technique which is used to determine the information needs of the project stakeholders. This is a key component for planning the project's actual communications. It would assist in determining and limiting who will communicate with w






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






17. Integrates scope - cost (or resource) - and schedule measures to help the project management team assess project performance.






18. Describes how risk management will be structured and performed on the project.






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






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






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






22. Provides a documented basis for making future project decisions and for confirming or developing common understanding of the project scope among the stakeholders






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. Effect on project objectives if the risk event occurs.






25. Process of monitoring the status of the project and product scope and managing changes to the scope baseline.






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






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






28. An analytical technique used to determine the basic underlying reason that causes a variance or a defect or a risk. Root cause may underlie more than one variance or defect or risk. Root cause analysis is done as part of corrective action - Helps ide






29. Process of identifying and documenting relationships among the project activities. Sequencing can be performed by using project management software or by using manual or automated techniques.






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






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






32. Describes how the procurement processes (from developing procurement documentation through contract closure) will be managed






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






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






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






36. Modifications to the cost estimation prepared for the project






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






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






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






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






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






42. Technique that explores the validity of assumptions basing on which every identified project risk is conceived and developed. It identifies risks to the project from inaccuracy - instability - inconsistency - or incompleteness of assumptions.






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






44. 1. Performed by people; 2. Constrained by limited resources; 3. Planned - excuted - monitored - and controlled; 4. Ultimate goal is to achieve organizational objectives or stratregic plans






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






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






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






48. Includes the processes that organize - manage - and lead the project team.






49. A modification of a logical relationship that directs a delay in the successor activity.






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