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






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






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






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






5. A table that links requirements to their origin and traces them throughout the project life cycle






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






7. A calendar of working days and non- working days that determines those dates on which each specific resource is ideal or can be active; typically defines the resource specific holidays and resource availability periods; the calendars that specify whe






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






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






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






11. Describes the processes required to ensure that the project includes only the essential work required to complete the project successfully. It includes collecting the requirements - defining the scope - verifying the scope and controlling the scope o






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






13. Features or services that characterize a product - result - or service






14. Process of redefining the cost performance/schedule/performance measurement/technical baseline. If cost variances are severe - re-baselining is needed to provide a realistic measure of performance.






15. Responses to emerging risks that was previously unidentified or accepted. These were not planned in advance of the occurrence of the risk event.






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






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






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






19. Involves payments (cost reimbursements) to the seller for all legitimate actual costs incurred for completed work - plus a fee representing seller profit






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






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






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






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






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






25. A -specific version of the schedule model used to compare actual results to the plan to determine if preventive or corrective action is needed to meet the project objectives.






26. Process of estimating the type and quantities of resources like materials - people - equipment - or supplies required to perform each project activity






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






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






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






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






31. A formal procedure for authorizing project work to ensure that work is done by the identified organization at the right time and in proper sequence.






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






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






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






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






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






37. Any modification to the agreed upon project scope as defined by the approved WBS






38. Process of obtaining seller responses - selecting a seller - and awarding a contract






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






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






41. Uses a project model that translates the uncertainties specified at a detailed level into their potential impact on objectives that are expressed at the level of the total project. Project simulation uses computer models and estimates of risk and are






42. Methods used to distribute information to team members and other stakeholders.






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






44. Bring together prequalified stakeholders and subject matter experts to learn about their expectations and attitudes about a proposed product - service - or result






45. Factors that - for planning purposes - will be considered true - real or certain.






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






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






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






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






50. Describes the processes required to ensure that the project satisfies the needs for which it is undertaken. It includes quality planning - performing quality assurance and control.