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. Calculates the theoretical early start and finish dates - and late start and finish dates - for all activities without regard to any resource limitations. This is done by performing a forward and backward pass analysis through the schedule network.






2. Describes the processes required to ensure that the various elements of the project are properly coordinated. It includes developing the project plan - managing the execution of the project plan - monitoring & controlling work - integrating the chang






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






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






5. Generally used when considerations like technical approach and technical skills are paramount in source selection






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






7. A schedule compression technique in which phases or activities normally performed in sequence are performed in parallel. Fast tracking often results in rework and increased risk. Fast tracking only works if activities can be overlapped to shorten the






8. Process of formalizing acceptance of the completed project deliverables






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






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






11. Process of redefining the cost performance/schedule/performance measurement/technical baseline. If cost variances are severe - re-baselining is needed to provide a realistic measure of performance.






12. Documents the characteristics of the product - result - or service which the project is undertaken to create.






13. Modifications to the cost estimation prepared for the project






14. Charts/ Judgment provided based upon expertise in an application area - knowledge area - discipline - industry - etc. as appropriate for the activity being performed. Such expertise may be provided by any group or person with specialized education -






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






16. Used to rate or score seller proposals






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






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






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






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






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






22. Project Simulation uses a model that translates the specified detailed uncertainties of the project into their potential impact on project objectives.






23. Subdivision of project deliverables into smaller - more manageable components






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






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






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






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






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






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






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






31. The expected total cost of a schedule activity - a work breakdown structure component - or the project when the defined scope of work will be completed.






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






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






34. Factors that - for planning purposes - will be considered true - real or certain.






35. Estimating or predicting future project status and progress based on knowledge and information available at the time of forecasting.






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






37. Policies - guidelines and procedures that can help the project management team with various aspects of organizational planning.






38. Judgment provided based upon expertise in an application area - knowledge area - discipline - industry - etc. as appropriate for the activity being performed. Such expertise may be provided by any group or person with specialized education - knowledg






39. Describes the extent to which a risk is known or understood. Measures extent of data available as well as reliability of data.






40. A process of systematically gathering and analyzing quantitative and qualitative information to determine whose interests should be taken into account throughout the project. It identifies the interests - expectations - and influence of the stakehold






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






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






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






44. Any modification to the contents of the project plan or the supporting details.






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






46. Process of defining how to conduct risk management activities for a project.






47. Describes how individual requirements meet the business need for the project.






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






49. Collection of generally sequential project phases.






50. Factors that will limit the project management team's options (e.g. - a predefined budget)