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 document that sets out the format and establishes the activities and criteria for planning - structuring - and controlling the project costs. The cost management plan is contained in - or is a subsidiary plan of - the project management plan.






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






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






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






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






6. Describes the processes required to ensure timely and appropriate generation - collection - dissemination and ultimate disposition of project information. It includes identifying stakeholders - planning communication - distributing information - mana






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






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






9. A formal or informal approach to obtain information from stakeholders by talking to them directly






10. Defines the procedures by which project scope can be changed; includes paperwork - tracking systems and approval levels necessary for authorizing changes.






11. Also known as "job shadowing -" it is usually done externally by the observer viewing the user performing her job.






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






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






14. A schedule compression technique in which phases or activities normally performed in sequence are performed in parallel. Fast tracking often results in rework and increased risk. Fast tracking only works if activities can be overlapped to shorten the






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






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






17. Action taken to bring a defective or nonconforming item into compliance with requirements or specifications. It is a frequent cause of project overruns in most application areas.






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






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






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






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






22. Policies - guidelines and procedures that can help the project management team with various aspects of organizational planning.






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. A hierarchically organized depiction of the project organization arranged so as to relate the work packages to the performing organizational units.






25. Description of the product of the project - provides important information about any technical issues or concerns that would need to be considered during procurement planning






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






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






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






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






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






31. Integrates scope - cost (or resource) - and schedule measures to help the project management team assess project performance.






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






33. The document that sets out the format and establishes the activities and criteria for planning - structuring - and controlling the project costs. The cost management plan is contained in - or is a subsidiary plan of - the project management plan.






34. An organizational placement strategy where the project team members are physically located close to one another in order to improve communication - working relationships - and productivity.






35. A formal - approved document used to define how the project is executed - controlled and monitored. It can either be at a detailed or high level and may contain one or more subsidiary plans.






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






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






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






39. It includes the processes required to ensure timely and appropriate generation - collection - dissemination - storage - retrieval - and ultimate disposition of project information.






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






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






42. Processes and procedures developed for the closing or canceling of projects.






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 the processes required to purchase or acquire products - services - or results needed from outside the project team.






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






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






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






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






49. Process of documenting project purchasing decisions - specifying the approach - and identifying potential sellers.






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