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






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






3. An authorized time-phased budget at completion (BAC) used to measure - monitor - and control overall cost performance on the project. Developed as a summation of the approved budgets by time period and is typically displayed in the form of an S-curve






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






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






6. A technique for estimating that applies a weighted average of optimistic - pessimistic - and most likely estimates when there is uncertainty with the individual activity estimates.






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






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






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






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






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






12. Dependencies that are contractually required or those inherent in the nature of the work. Often involve physical limitations.






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






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






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






16. Process of managing procurement relationships - monitoring contract performance - ad making changes and corrections as needed.






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






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






19. It consists of tools and techniques used to gather - integrate and disseminate the outputs of project management processes. Supports all aspects of the project from initiating through closing - and can include both manual and automated systems.






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






21. Incurred for the exclusive benefit of the project (e.g. - salaries of full-time project staff).






22. Application of knowledge - skills - tools - and techniques to project activities to meet the project requirements.






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






24. A deliverable is a unique - tangible and verifiable work/product. Each project phase is marked by the completion of one or more deliverables.






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






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






27. Dependencies determined by the Project Management Team; involve a relationship between project activities and non-project activities (i.e. - dependencies on issues that are beyond the scope of the project). These dependencies are outside the project






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






29. Uses a project model that translates the uncertainties specified at a detailed level into their potential impact on objectives that are expressed at the level of the total project. Project simulation uses computer models and estimates of risk and are






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






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






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






33. Collection of generally sequential project phases.






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






35. Description of the product of the project - provides important information about any technical issues or concerns that would need to be considered during procurement planning






36. Provides a documented basis for making future project decisions and for confirming or developing common understanding of the project scope among the stakeholders






37. Process of monitoring the status of the project and product scope and managing changes to the scope baseline.






38. Describes the processes concerned with identifying - analyzing - and responding to project risk. It includes planning risk management - identifying risks - performing qualitative risk analysis - performing quantitative risk analysis - planning risk r






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






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






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






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






43. It includes the processes required to ensure timely and appropriate generation - collection - dissemination - storage - retrieval - and ultimate disposition of project information.






44. Seller is a subcontractor - vendor - or supplier - who will typically manage the work of the project. Buyer is the customer who has outsourced work to the seller.






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






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






47. Activities should have a coding structure to allow sorting and/or extractions based on different attributes assigned to the activities.






48. Records of previous project results that can be used to identify risks.






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






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