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. Outcome of activities performed to accomplish the project.






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






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






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






5. Seeking to shift the consequences of the risk to a third party together with the ownership for the response.






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






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






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






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






10. They involve measuring value or attractiveness to the project owner. Includes considering the decision criteria and a means to calculate value under uncertainty.






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






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






13. A modification of a logical relationship that allows an acceleration of the successor activity. A negative lead is equivalent to a positive lag.






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






15. Determining which risks may affect the project and documenting their characteristics.






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






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






18. Calculates the theoretical early start and finish dates - and late start and finish dates - for all activities without regard to any resource limitations. This is done by performing a forward and backward pass analysis through the schedule network.






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






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






21. Approved modifications to the project schedule that are used to manage the project






22. Collection of generally sequential project phases.






23. Process of documenting project purchasing decisions - specifying the approach - and identifying potential sellers.






24. The process of analyzing activity sequences - durations - resource requirements - and schedule constrains to create the project schedule






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






26. Repository that provides for collection - maintenance - and analysis of data gathered and used in the risk management process. Use of this database assists risk management throughout the organization and - over time - forms the basis of a risk lesson






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






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






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






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. Technique that explores the validity of assumptions basing on which every identified project risk is conceived and developed. It identifies risks to the project from inaccuracy - instability - inconsistency - or incompleteness of assumptions.






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






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






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






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






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






37. The conclusion of a project phase is marked by a review of both key deliverables and project performance till date to determine if the project should continue into its next phase and detect and correct errors cost-effectively. These phase end reviews






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






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






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






41. Clarify the structure - requirements and other terms of the purchases so that mutual agreement can be reached prior to signing the contract.






42. Also called risk symptoms or warning signs - they are indications that a risk has occurred or is about to occur. They may be discovered in the risk identification process and watched in the risk monitoring and control process.






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






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






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






46. Seller prepared documents that describe the seller's ability and willingness to provide the requested product.






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






48. A table that links requirements to their origin and traces them throughout the project life cycle






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






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