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. Factors that limit a buyer's options. E.g. - funds availability






2. The work that must be done to deliver a product with the specified features and functions






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






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






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






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






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






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






9. A requirement imposed by a governmental body and its compliance is mandatory.






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






12. Lists or files maintained with information on prospective sellers. These lists will generally have information on relevant past experience and other characteristics of the prospective sellers






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






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






15. If the performing organization does not have a formal contracting group - then the project team will have to supply both the resources and expertise to support procurement activities






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






17. Any form of schedule network analysis in which scheduling decisions are driven by resource constraints.






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






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






20. Involves immediate corrective or preventive action as a consequence of quality control measurements.






21. It consists of tools and techniques used to gather - integrate and disseminate the outputs of project management processes. Supports all aspects of the project from initiating through closing - and can include both manual and automated systems.






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






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






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






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






26. Includes all those activities designed to enhance the competencies of the project team members. Training can be formal or informal.






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






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






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






30. Focused sessions that bring key cross-functional stakeholders together to define product requirements






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






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






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






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






35. Activities that assist in developing/enhancing the ability of team members to work together effectively and contribute to the success of the project team. It improves the people skills - technical competencies - and overall team environment and proje






36. Estimating or predicting future project status and progress based on knowledge and information available at the time of forecasting.






37. Modifications to the cost estimation prepared for the project






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






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






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






41. A collection of formal (note: not informal) documented procedures - which defines how the documentation and project deliverables will be managed - changed and approved.






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






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






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






45. Process to monitor the status of the project to update the project budget and manage changes to the cost baseline.






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






47. Structured review of the procurement process originating from the Plan Procurements process through Administer Procurements process. Objective is to identify successes and failures that warrant recognition in the preparation or administration of othe






48. Organize and summarize the information gathered - and present the results of any analysis as compared to the performance measurement baseline. Reports should provide status and progress of the project at the required level of detail.






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






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