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. Used to generate - classify - and prioritize product requirements. Some methods used to reach group decisions are: unanimity - majority - plurality - and dictatorship.






2. Describes the processes required to ensure timely completion of the project. It includes defining activities - sequencing activities - estimating activity resources - estimating activity durations - developing the schedule - and controlling the sched






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






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






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






6. Precedence Diagramming Method (PDM) includes four types of dependencies or relationships between activities: 1. Finish to Start; 2. Finish to Finish; 3. Start to Finish; 4. Start to Start






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






8. Testing identified assumptions against two criteria: assumption stability and consequences on the project if the assumption is false.






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






10. A matrix that assigns risk ratings to risks or conditions based on a combining probability and impact scales. Risks with high probability and high impact will require further analysis.






11. A provision in the project management plan to mitigate cost and/or schedule risk. Often used with a modifier to provide further details on what types of risk are meant to be mitigated.






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






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






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






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






16. The process in which the estimated costs of individual activities or work packages are aggregated to establish an authorized cost baseline.






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






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






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






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






21. Involves procedures required to close a contract as specified in the prescribed procedures for close procurements. Includes product verification and administrative closure.






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






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






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






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






26. Process of numerically analyzing the effect of identified risks on overall project objectives.






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






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






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






30. Documented direction for executing the project work to bring expected future performance of the project work in line with the project management plan.






31. Costs allocated to the project by the performing organization as a cost of doing business (e.g. - salaries of corporate executives). Usually calculated as a percentage of direct costs.






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






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






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






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






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






37. Seller prepared documents that describe the seller's ability and willingness to provide the requested product.






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






39. Reduce the probability and/or consequence of an adverse risk event to be within acceptable threshold limits.






40. Dependencies determined by the Project Management Team; involve a relationship between project activities and non-project activities (i.e. - dependencies on issues that are beyond the scope of the project). These dependencies are outside the project






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






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






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






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






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






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






47. Forecasts of potential project schedule and cost results listing the possible completion dates or project duration and costs with their associated confidence levels.






48. Describes the processes required to ensure that the various elements of the project are properly coordinated. It includes developing the project plan - managing the execution of the project plan - monitoring & controlling work - integrating the chang






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






50. Checklists are structured tools - usually component specific - used to verify that a set of required steps has been performed and to ensure consistency in frequently performed tasks. These can be developed based on historical information and knowledg






Can you answer 50 questions in 15 minutes?



Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests