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. Any numbering system used to uniquely identify each component of the work breakdown structure.






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






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






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






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






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






7. The calculated projection of cost performance that must be achieved on the remaining work to meet a specified management goal - such as the budget at completion (BAC) or the estimate at completion (EAC). It is the ratio of 'remaining work' to the 'fu






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






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






10. Broader view of Project Cost Management - whereby other than project costs - we consider the effect of project decisions on the cost of using the project's product.






11. A documented tabulation of schedule activities that shows the activity description - activity identifier - and a sufficiently detailed scope of work description so project team members understand what work is to be performed.






12. Process of implementing risk response plans - tracking identified risks - monitoring residual risks - identifying new risks - and evaluating risk process effectiveness throughout the project.






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






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






15. Documented direction for executing the project work to bring expected future performance of the project work in line with the project management plan.






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






17. Describes the processes required to ensure that the various elements of the project are properly coordinated. It includes developing the project plan - managing the execution of the project plan - monitoring & controlling work - integrating the chang






18. Documents the characteristics of the product - result - or service which the project is undertaken to create.






19. Includes identified risks - risk owners - results of Perform qualitative risk analysis process - agreed upon response strategies - etc.






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






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






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






23. Involves developing a better understanding of the product of the project






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






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






26. Risk Audits examine and document the effectiveness of risk responses in dealing with identified risks and their root causes - as well as the effectiveness of the risk management process.






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






28. Deliverable- oriented grouping of project components that organizes and defines the total scope of the project - work not in the WBS is outside the scope of the project.






29. Documented direction for executing the project work to bring expected future performance of the project work in line with the project management plan.






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






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






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






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






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






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. A formal or informal approach to obtain information from stakeholders by talking to them directly






37. It is used to identify stakeholders that can provide information on detailed project and product requirements. It contains the following information regarding the identified stakeholders: identification information (name - designation - location - co






38. Mutually binding legal agreement that obligates the seller to provide the specified products - services - or results - and obligates the buyer to compensate the seller.






39. A mathematical technique to forecast future outcomes based on historical results. This is performed using run charts.






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






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






42. Predefined approaches to risk analysis and response in some organizations that have to be tailored to a particular project.






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






44. The total amount of time that a schedule activity may be delayed from its early start without delaying the project finish date - or violating a schedule constraint. Calculated using the critical path method technique and determining the difference be






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






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






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






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






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






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