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. Application of knowledge - skills - tools - and techniques to project activities to meet the project requirements.






2. The conclusion of a project phase is marked by a review of both key deliverables and project performance till date to determine if the project should continue into its next phase and detect and correct errors cost-effectively. These phase end reviews






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






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






5. Modifications to the cost estimation prepared for the project






6. Documents how requirements will be analyzed - documented - and managed throughout the project






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






8. A modification of a logical relationship that allows an acceleration of the successor activity. A negative lead is equivalent to a positive lag.






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






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






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






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






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






14. 1. Operations do not have any timelines. Projects are temporary and have finite time duration. 2. Operation's objective is usually to sustain the business. Project's objective is to achieve the target and close the project.






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






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






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






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






19. Used to rate or score seller proposals






20. Process of formalizing acceptance of the completed project deliverables






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






22. Project team accepts the risk - i.e. team decides not to change the project plan to deal with the risk - or is unable to identify any other suitable response strategy.






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






24. Process of monitoring the status of the project to update project progress and manage changes to the schedule baseline






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






26. Used to solicit proposals from prospective sellers






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






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






29. The process of confirming human resource availability and obtaining the team necessary to complete project assignments.






30. This compares technical accomplishments during project execution with the project management plan's schedule of technical achievement.






31. Probability that a risk will occur.






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






33. Records of previous project results that can be used to identify risks.






34. Describes the processes required to acquire goods and services from outside the project team. It includes planning procurements - conducting procurements - administering procurements - and closing procurements.






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






36. Risks that arise as a direct result of implementing a risk response.






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






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






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






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






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






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






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






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






45. Technologies or methods to transfer information among project stakeholders.






46. This involves calculating the theoretical early and late start and finish dates for all project activities without regard to any resource pool restrictions.






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






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






49. Hybrid type of contractual agreements that contain aspects of both cost-reimbursable and fixed- price contracts. Some characteristics: · Open-ended - i.e. - full value of the agreement and the exact quantity of items to be delivered may not be define






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