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






2. Used to identify project and product requirements; some of the techniques used are: Brainstorming - Nominal group technique - The Delphi technique - Idea/mind mapping - and Affinity diagram.






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






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






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






6. Describes the processes required to make the most effective use of the people involved with the project. It includes developing the human resource plan - acquiring the project team - developing the project team - and managing the project team.






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






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






9. The process of identifying all people or organizations impacted by the project and documenting relevant information regarding their interests - involvement - and impact on project success.






10. Process of formally authorizing a new project or the next phase of an existing project; links the project to the ongoing work of the performing organization






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






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






13. Quantities to be performed for each specific category - and can be used to estimate activity durations






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






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






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






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






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. Meetings held to assess project status and/or progress.






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






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






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






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






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






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






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






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






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






29. Used to solicit proposals from prospective sellers






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






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






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






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






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






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






36. The process of collecting and distributing performance information - including status reports - progress measurements - and forecasts to stakeholders.






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






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






39. Describes the processes required to ensure that the project includes only the essential work required to complete the project successfully. It includes collecting the requirements - defining the scope - verifying the scope and controlling the scope o






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






41. Risks that remain after planned responses have been implemented - as well as those that have been deliberately accepted.






42. If the performing organization does not have a formal contracting group - then the project team will have to supply both the resources and expertise to support procurement activities






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






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






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






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






47. Testing identified assumptions against two criteria: assumption stability and consequences on the project if the assumption is false.






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






49. Risks that arise as a direct result of implementing a risk response.






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