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






2. Helps to determine which risks have the most potential impact on the project. Examines the extent to which the uncertainty of each project element affects the objective being examined when all the other uncertain elements are held at their baseline v






3. Process of defining and documenting stakeholders' needs to meet the project objectives






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






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






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






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






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






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






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






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






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






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






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






15. A project is a temporary endeavor undertaken to create a unique product - service - or result






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






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






18. Judgment provided based upon expertise in an application area - knowledge area - discipline - industry - etc. as appropriate for the activity being performed. Such expertise may be provided by any group or person with specialized education - knowledg






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






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






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






22. A method of estimating a component of work. The work is decomposed into more detail. An estimate is prepared of what is needed to meet the requirements of each of the lower - more detailed pieces of work. These estimates are then aggregated into a to






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






24. Clarify the structure - requirements and other terms of the purchases so that mutual agreement can be reached prior to signing the contract.






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






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






27. The planned dates to perform schedule activities and the planned dates for meeting schedule milestones. Includes planned start and finish dates for the project's activities - milestones - work packages - planning packages - and control accounts. This






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






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






30. Modifications to the cost estimation prepared for the project






31. List of risks includes those that pose the greatest threat or present the greatest opportunity to the project together with a measure of their impact.






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






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






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






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






36. Describes how individual requirements meet the business need for the project.






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






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






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






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






41. Quantities to be performed for each specific category - and can be used to estimate activity durations






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






43. Process of assessing and combining the impact and the likelihood of identified risks. Prioritizes risks according to their potential effect on project objectives for further analysis or action.






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






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






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






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






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






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






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