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. Involves procedures required to close a contract as specified in the prescribed procedures for close procurements. Includes product verification and administrative closure.






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






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






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






5. The process of making relevant information available to project stakeholders in a timely manner - as planned. Performed throughout the entire project life cycle and in all management processes.






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






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






8. Expectations The process of communicating and working with stakeholders to meet their needs and addressing issues as they occur. Project manager applies appropriate interpersonal skills to manage stakeholder expectations - for example - by building t






9. A modification of a logical relationship that directs a delay in the successor activity.






10. Process of formalizing acceptance of the completed project deliverables






11. An applicable restriction that will affect the performance of the project/process.






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. Involves setting a fixed total price for a defined product or service to be provided.






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






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






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






17. Formal written notice from a person or organization responsible for contract administration - informing that the contract has been completed.






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






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






20. Describes the processes required to ensure that the project is completed within the approved budget. It includes estimating the cost - determining the budget - and controlling the costs.






21. Testing identified assumptions against two criteria: assumption stability and consequences on the project if the assumption is false.






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






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






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






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






26. Technologies or methods to transfer information among project stakeholders.






27. Collection of generally sequential project phases.






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






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






30. Forecasts of potential project schedule and cost results listing the possible completion dates or project duration and costs with their associated confidence levels.






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. Predefined approaches to risk analysis and response in some organizations that have to be tailored to a particular project.






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






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






35. The expected cost needed to complete all the remaining work for a schedule activity - work break down structure component - or the project.






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






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






38. Process of estimating the type and quantities of resources like materials - people - equipment - or supplies required to perform each project activity






39. The process to identify and document project roles - responsibilities - and required skills - report relationships - and create a staffing management plan.






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






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






42. Costs allocated to the project by the performing organization as a cost of doing business (e.g. - salaries of corporate executives). Usually calculated as a percentage of direct costs.






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






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






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






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






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






48. Structured review of the procurement process originating from the Plan Procurements process through Administer Procurements process. Objective is to identify successes and failures that warrant recognition in the preparation or administration of othe






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






50. Modifications to the cost estimation prepared for the project