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. Approved modifications to the project schedule that are used to manage the project






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






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






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






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






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






7. Process of changing the schedule baseline. It is done when schedule delays are very severe - and the project schedule has to be completely changed.






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






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






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. Diagram that describes a decision under consideration and the implications of choosing one or another of the available alternatives.






12. A -specific version of the schedule model used to compare actual results to the plan to determine if preventive or corrective action is needed to meet the project objectives.






13. Requests to expand or reduce project scope - modify policies/ processes/plans/procedures/costs and - if approved - can affect budgets or revise schedules. These change requests are processed through the Perform Integrated Change Control process.






14. Describes the processes required to ensure timely and appropriate generation - collection - dissemination and ultimate disposition of project information. It includes identifying stakeholders - planning communication - distributing information - mana






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






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






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






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






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






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






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






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






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






24. Describes how risk management will be structured and performed on the project.






25. Charts that are used to show positions and relationships in a graphical format.






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






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






28. Describes how the procurement processes (from developing procurement documentation through contract closure) will be managed






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






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






31. Refers to the centralized management of one or more portfolios to achieve strategic business objectives. Portfolio management ensures that the portfolios are reviewed to ascertain that resources are allocated as per priority and the allocation is con






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






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






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






35. Includes identified risks - risk owners - results of Perform qualitative risk analysis process - agreed upon response strategies - etc.






36. List of risks includes those that pose the greatest threat or present the greatest opportunity to the project together with a measure of their impact.






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






38. Effect on project objectives if the risk event occurs.






39. Precedence Diagramming Method (PDM) includes four types of dependencies or relationships between activities: 1. Finish to Start; 2. Finish to Finish; 3. Start to Finish; 4. Start to Start






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






41. Collection of generally sequential project phases.






42. They possess a blend of functional and projectized characteristics. Weak matrices maintain many of the characteristics of a functional organization - and the Project Manager's role is more that of a coordinator or expediter than that of a manager. Si






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






44. An estimating technique that uses the values of parameters - such as scope - cost - budget - and duration or measure of scale such as size - weight - and complexity - from a previous - similar activity as the basis for estimating the same parameter o






45. A subsequent phase of a project is sometimes begun prior to approval of the previous phase deliverables when the risks involved are deemed acceptable. This practice of overlapping phases is often called fast tracking






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






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






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






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






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