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. Schematic displays of the logical relationships (dependencies) among the project schedule activities; always drawn from left to right to reflect project work chronology






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






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






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






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






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






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






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






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






10. 1. Operations do not have any timelines. Projects are temporary and have finite time duration. 2. Operation's objective is usually to sustain the business. Project's objective is to achieve the target and close the project.






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






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






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






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






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






16. A management control point where the resource plans - scope - schedule and actual cost are integrated and compared to earned value for performance measurement.






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






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






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






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






21. A partially complete document in a predefined format that provides a defined structure for collecting - organizing - and presenting information and data.






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






23. 1. Performed by people; 2. Constrained by limited resources; 3. Planned - excuted - monitored - and controlled; 4. Ultimate goal is to achieve organizational objectives or stratregic plans






24. In a projectized organization - most of the organization's resources are involved in project work - and Project Managers have a great deal of independence and authority.






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






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






27. Used to solicit proposals from prospective sellers






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






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






31. The process of confirming human resource availability and obtaining the team necessary to complete project assignments.






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






33. Process of defining how to conduct risk management activities for a project.






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






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






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






37. Measuring - examining and testing undertaken to determine whether results conform to requirements; also called reviews - product reviews - audits - and walkthroughs






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






39. Considers the characteristics of those prospective staff who are available to join the project team.






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






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






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






43. Reduce the probability and/or consequence of an adverse risk event to be within acceptable threshold limits.






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






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






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. A documented list of project team members - their project roles - and communication information.






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






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






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