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






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






3. A management control point where the resource plans - scope - schedule and actual cost are integrated and compared to earned value for performance measurement.






4. The process of making relevant information available to project stakeholders in a timely manner - as planned. Performed throughout the entire project life cycle and in all management processes.






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






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






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






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






9. A structured review of the seller's progress to deliver project scope and quality - within cost and on schedule - as compared to the contract.






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






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






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






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






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






15. Document that formally authorizes a project. Provides project manager with the authority to apply organizational resources to project activities.






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






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






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






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






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






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






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






23. Process of implementing risk response plans - tracking identified risks - monitoring residual risks - identifying new risks - and evaluating risk process effectiveness throughout the project.






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






25. Any form of schedule network analysis in which scheduling decisions are driven by resource constraints.






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






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






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






29. Also known as "job shadowing -" it is usually done externally by the observer viewing the user performing her job.






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






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






32. The amount of time that a schedule activity can be delayed without delaying the early start date of any immediately following schedule activities.






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






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






35. Helps to determine which risks have the most potential impact on the project. Examines the extent to which the uncertainty of each project element affects the objective being examined when all the other uncertain elements are held at their baseline v






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






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






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






39. A schedule network analysis technique used to determine the amount of scheduling flexibility on various logical network paths in the project schedule network - and to determine the minimum total project duration. Early start and finish dates are calc






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






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






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






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






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






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






46. Lists or files maintained with information on prospective sellers. These lists will generally have information on relevant past experience and other characteristics of the prospective sellers






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






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






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






50. A modification of a logical relationship that directs a delay in the successor activity.