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. Records of previous project results that can be used to identify risks.






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






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






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






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






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






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






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






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






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






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






12. Any modification to the contents of the project plan or the supporting details.






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






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






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






16. Process of managing procurement relationships - monitoring contract performance - ad making changes and corrections as needed.






17. Used to identify project and product requirements; some of the techniques used are: Brainstorming - Nominal group technique - The Delphi technique - Idea/mind mapping - and Affinity diagram.






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






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






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






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






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






23. An estimating technique that uses parameters from a previous - similar project as the basis for estimating the same parameter/measure for a future project. Frequently used to estimate project duration when there is a limited amount of detailed inform






24. Descriptions of which resources will be available at what times and in what patterns necessary for schedule development






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






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






27. Process of developing a detailed description of the project and product






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






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






30. Collection of generally sequential project phases.






31. Process of changing the schedule baseline. It is done when schedule delays are very severe - and the project schedule has to be completely changed.






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






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






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






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






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






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






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






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






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






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






42. Systematic process of planning - identifying - analyzing - responding - and monitoring and controlling project risk. It increases the probability and impact of positive events - and decrease the probability and impact of negative events in the projec






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






44. Allow for non-sequential activities (e.g. Loops or Conditional Branches); e.g. - GERT(Graphical Evaluation and Review Technique) and System Dynamics






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






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






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






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






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






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