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






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






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






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






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






6. A collection of formal (note: not informal) documented procedures - which defines how the documentation and project deliverables will be managed - changed and approved.






7. A schedule compression technique in which cost and schedule tradeoffs are analyzed to determine how to obtain the greatest amount of compression for the least incremental cost. Crashing only works for activities where additional resources will shorte






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






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






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






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






12. An accepted action performed to bring projected future project performance in line with the project plan. These actions have to be documented.






13. The document that describes the communication needs and expectations for the project; how and in what format information will be communicated; when and where each communication will be made; and who is responsible for providing each type of communica






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






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






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






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






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






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






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






21. It shortens the project schedule without changing the project scope - in order to meet schedule constraints - imposed dates - or other schedule objectives. -. This technique includes crashing and fast tracking.






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






23. Involves setting a fixed total price for a defined product or service to be provided.






24. Allow for non-sequential activities (e.g. Loops or Conditional Branches); e.g. - GERT(Graphical Evaluation and Review Technique) and System Dynamics






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






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






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






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






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






30. Bring together prequalified stakeholders and subject matter experts to learn about their expectations and attitudes about a proposed product - service - or result






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






32. Describes the processes required to ensure timely completion of the project. It includes defining activities - sequencing activities - estimating activity resources - estimating activity durations - developing the schedule - and controlling the sched






33. The policies - guidelines - or procedures that govern the recruitment of staff.






34. Probability that a risk will occur.






35. Describes the processes required to acquire goods and services from outside the project team. It includes planning procurements - conducting procurements - administering procurements - and closing procurements.






36. Structured review of the project plans and assumptions - prior project files - contracts - and other information.






37. It compares cost performance over time - schedule activities or work packages overrunning and under running the budget - and estimated funds needed to complete work in progress.






38. Specify lessons that can be learned from each and every project - even from projects which are failures. They need to be documented. Most companies prefer post-implementation meetings and case studies to document Lessons Learned






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






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






41. A matrix that assigns risk ratings to risks or conditions based on a combining probability and impact scales. Risks with high probability and high impact will require further analysis.






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






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






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






45. This involves calculating the theoretical early and late start and finish dates for all project activities without regard to any resource pool restrictions.






46. Formal and informal policies that are required for project plan development. Organizational policies include quality management - personnel administration and financial controls.






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






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






49. Describes how project scope will be managed and how scope changes will be integrated into the project. It should also include an assessment of the expected stability of the project scope






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