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. Testing identified assumptions against two criteria: assumption stability and consequences on the project if the assumption is false.






2. Describes the extent to which a risk is known or understood. Measures extent of data available as well as reliability of data.






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






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






5. Process of formalizing acceptance of the completed project deliverables






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






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






8. The process of collecting and distributing performance information - including status reports - progress measurements - and forecasts to stakeholders.






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






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






11. Process of defining and documenting stakeholders' needs to meet the project objectives






12. A documented list of project team members - their project roles - and communication information.






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






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






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






16. Group of related projects managed in a coordinated way to obtain control and benefits that are not available if managed individually.






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






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






19. A general data gathering and creativity technique that can be used to identify risks - ideas - or solutions to issues by using a group of team members or subject matter experts which data can be addressed later in Perform qualitative and quantitative






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






21. Factors which - for planning purposes - are considered to be true - real or certain.






22. Charts/ Judgment provided based upon expertise in an application area - knowledge area - discipline - industry - etc. as appropriate for the activity being performed. Such expertise may be provided by any group or person with specialized education -






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






24. This is done to take care of risks that were not identified in the risk response plan - or their impact on objectives is greater than expected.






25. Collection of generally sequential project phases.






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






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






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






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






30. A method of estimating a component of work. The work is decomposed into more detail. An estimate is prepared of what is needed to meet the requirements of each of the lower - more detailed pieces of work. These estimates are then aggregated into a to






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






32. An uncertain event or condition that - if it occurs - has a positive or negative effect on the project objective.






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






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






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






36. A functional organization has a hierarchy in which every employee has one clear superior. Staff members are grouped by areas of specialization. Functional organizations may still have projects - but the perceived scope of the project is defined by th






37. Defines what kinds of competencies are required from what kind of individuals or groups and in what time frames.






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






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






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






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






42. Factors that limit a buyer's options. E.g. - funds availability






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






44. Process of formally authorizing a new project or the next phase of an existing project; links the project to the ongoing work of the performing organization






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






46. A structured review of the seller's progress to deliver project scope and quality - within cost and on schedule - as compared to the contract.






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






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






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






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