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






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






3. The process to identify and document project roles - responsibilities - and required skills - report relationships - and create a staffing management plan.






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






5. Probability that a risk will occur.






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






7. Special category of revised cost estimates to an approved cost baseline.






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






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






10. Activities that assist in developing/enhancing the ability of team members to work together effectively and contribute to the success of the project team. It improves the people skills - technical competencies - and overall team environment and proje






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






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






13. A -specific version of the schedule model used to compare actual results to the plan to determine if preventive or corrective action is needed to meet the project objectives.






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






15. Meetings with all prospective sellers and buyers prior to submittal of a bid or proposal. Used to ensure that all prospective sellers have a clear and common understanding of the procurement - and that no bidders receive preferential treatment.






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






17. Deliverable- oriented grouping of project components that organizes and defines the total scope of the project - work not in the WBS is outside the scope of the project.






18. A formal procedure for authorizing project work to ensure that work is done by the identified organization at the right time and in proper sequence.






19. Clarify the structure - requirements and other terms of the purchases so that mutual agreement can be reached prior to signing the contract.






20. Modifications to the cost estimation prepared for the project






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






22. Broader view of Project Cost Management - whereby other than project costs - we consider the effect of project decisions on the cost of using the project's product.






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






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






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






26. The work that must be done to deliver a product with the specified features and functions






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






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






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






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






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






32. Systematic process of planning - identifying - analyzing - responding - and monitoring and controlling project risk. It increases the probability and impact of positive events - and decrease the probability and impact of negative events in the projec






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






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






35. Meetings held to assess project status and/or progress.






36. Group of related projects managed in a coordinated way to obtain control and benefits that are not available if managed individually.






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






38. An applicable restriction that will affect the performance of the project/process.






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






40. Charts that are used to show positions and relationships in a graphical format.






41. Project team must measure itself periodically against the expectations of those outside the project.






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






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






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






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






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






47. A structure that relates the project organizational breakdown structure to the work breakdown structure to help ensure that each component of the project's scope of work is assigned to a person or team. It illustrates the connections between work pac






48. A general management technique used to determine whether a particular work can be accomplished by the project team or must be purchased from outside sources.






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






50. A hierarchically organized depiction of the project organization arranged so as to relate the work packages to the performing organizational units.