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. Structured method to guide the project team during development of project plan. Standard forms and templates or even complicated simulations may be used.






2. Process of obtaining seller responses - selecting a seller - and awarding a contract






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






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






5. Process of documenting project purchasing decisions - specifying the approach - and identifying potential sellers.






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






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






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






9. This compares technical accomplishments during project execution with the project management plan's schedule of technical achievement.






10. A general data gathering and creativity technique that can be used to identify risks - ideas - or solutions to issues by using a group of team members or subject matter experts which data can be addressed later in Perform qualitative and quantitative






11. Schematic displays of the logical relationships (dependencies) among the project schedule activities; always drawn from left to right to reflect project work chronology






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






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






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






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






16. Hybrid type of contractual agreements that contain aspects of both cost-reimbursable and fixed- price contracts. Some characteristics: · Open-ended - i.e. - full value of the agreement and the exact quantity of items to be delivered may not be define






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






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






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






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






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






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






23. The process of determining project stakeholders' information needs and defining a communication approach.






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






25. Used to solicit proposals from prospective sellers






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






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






28. It is a tool and technique which is used to determine the information needs of the project stakeholders. This is a key component for planning the project's actual communications. It would assist in determining and limiting who will communicate with w






29. Describes how risk management will be structured and performed on the project.






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






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






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






33. An uncertain event or condition that - if it occurs - has a positive or negative effect on the project objective.






34. Projects are frequently divided into better manageable components or subprojects. Subprojects are often contracted to an external enterprise or another functional unit in the performing organization.






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






36. A formal - approved document used to define how the project is executed - controlled and monitored. It can either be at a detailed or high level and may contain one or more subsidiary plans.






37. Activities specifically taken by management and team members to help individual team members work together effectively - thereby improving team performance






38. Modifications to the cost estimation prepared for the project






39. Includes all those activities designed to enhance the competencies of the project team members. Training can be formal or informal.






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






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






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






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






44. The state - quality - or sense of being restricted to a given course of action or inaction. An applicable restriction or limitation - either internal or external to a project - which will affect the performance of the project or a process.






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






46. Technique to evaluate the degree to which data about risks is useful for risk management.






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






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






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






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