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. A method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it.






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






3. It is used to identify stakeholders that can provide information on detailed project and product requirements. It contains the following information regarding the identified stakeholders: identification information (name - designation - location - co






4. Persons or organizations who are actively involved in the project or whose interests may be positively or negatively affected by the performance or completion of the project. They may also exert influence over the project - its deliverables - and the






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






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






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






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






9. Modifications to the cost estimation prepared for the project






10. Includes the processes that help to estimate - budget - and control costs - so that the project can be completed within the approved budget.






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






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






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






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






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






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






17. Meetings that are regularly scheduled to exchange and analyze information about the project and its performance.






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






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






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






21. Outcome of activities performed to accomplish the project.






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






23. Describes the procurement item in sufficient detail to allow prospective sellers to determine if they are capable of providing the products - services - or results.






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






25. The calculated projection of cost performance that must be achieved on the remaining work to meet a specified management goal - such as the budget at completion (BAC) or the estimate at completion (EAC). It is the ratio of 'remaining work' to the 'fu






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






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






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






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






30. Structured method to guide the project team during development of project plan. Standard forms and templates or even complicated simulations may be used.






31. Process of assessing and combining the impact and the likelihood of identified risks. Prioritizes risks according to their potential effect on project objectives for further analysis or action.






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






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






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






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






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






37. It can include correspondence - memos - meeting minutes - and documents describing the project.






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






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






40. Features or services that characterize a product - result - or service






41. Defines the process by which the procurement can be modified. It includes paperwork - tracking systems - dispute resolution procedures - and approval levels necessary for authorizing changes.






42. Process of developing options and actions to enhance opportunities and to reduce threats to project objectives. Includes the identification and assignment of individuals to take responsibility for each agreed-to and funded risk response.






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






44. Used to rate or score seller proposals






45. Collection of generally sequential project phases.






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






47. Hybrid type of contractual agreements that contain aspects of both cost-reimbursable and fixed- price contracts. Some characteristics: · Open-ended - i.e. - full value of the agreement and the exact quantity of items to be delivered may not be define






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






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






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