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






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






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






4. Document that formally authorizes a project. Provides project manager with the authority to apply organizational resources to project activities.






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






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






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






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






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






10. Used to generate - classify - and prioritize product requirements. Some methods used to reach group decisions are: unanimity - majority - plurality - and dictatorship.






11. A schedule compression technique in which cost and schedule tradeoffs are analyzed to determine how to obtain the greatest amount of compression for the least incremental cost. Crashing only works for activities where additional resources will shorte






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






13. Technique to evaluate the degree to which data about risks is useful for risk management.






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






15. Describes the processes required to make the most effective use of the people involved with the project. It includes developing the human resource plan - acquiring the project team - developing the project team - and managing the project team.






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






17. An analytical technique used to determine the basic underlying reason that causes a variance or a defect or a risk. Root cause may underlie more than one variance or defect or risk. Root cause analysis is done as part of corrective action - Helps ide






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






19. Describes how project scope will be managed and how scope changes will be integrated into the project. It should also include an assessment of the expected stability of the project scope






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






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






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






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






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






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






26. A structure that relates the project organizational breakdown structure to the work breakdown structure to help ensure that each component of the project's scope of work is assigned to a person or team. It illustrates the connections between work pac






27. A hierarchically organized depiction of the project organization arranged so as to relate the work packages to the performing organizational units.






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






29. A method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it.






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






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






32. Meetings with all prospective sellers and buyers prior to submittal of a bid or proposal. Used to ensure that all prospective sellers have a clear and common understanding of the procurement - and that no bidders receive preferential treatment.






33. Meetings held to assess project status and/or progress.






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






35. Involves setting a fixed total price for a defined product or service to be provided.






36. Used to rate or score seller proposals






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






38. Records of previous project results that can be used to identify risks.






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






40. Changing the project management plan to eliminate the threat entirely.






41. Terms used when the source selection decision will be based on price






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






43. The process of determining project stakeholders' information needs and defining a communication approach.






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






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






46. A provision in the project management plan to mitigate cost and/or schedule risk. Often used with a modifier to provide further details on what types of risk are meant to be mitigated.






47. Allows for probabilistic treatment of both network logic and activity duration estimates






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






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






50. Modifications to the cost estimation prepared for the project