Test your basic knowledge |

Comptia Project + Project Management

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. A request - demand or assertion of rights by a seller against a buyer or vice versa for consideration - compensation - or payment under the terms of a legally binding contract (such as for a disputed change)






2. Analytical procedure in which each potential failure mode in every component of a product is analyzed to determine its effect on the reliability of that component and - by itself or in combination with other possible failure modes - on the reliabilit






3. Quantifiable deviation - departure or divergence away from a known baseline or expected value






4. Risk that remains after risk responses have been implemented






5. Total amount of time that a schedule activity maybe delayed from its early start date without delaying the project finish date or violating a schedule constraint.






6. Buyer pays the seller a set amount (as defined by the contract) and the seller can earn an additional amount if the seller meets defined performance criteria






7. Collection of generally sequential - non overlapping product phases whose name and number are determined by the manufacturing and control needs of the organization.






8. The earliest point in time on which the uncompleted portions of a schedule activity (or the project) can finish - based on the schedule network logic - the data date and any schedule constraints.






9. Describes how the project management team will implement the performing organizations quality plan.






10. Process of numerically analyzing the effect of identified risks on overall project objectives






11. The area on either side of the centerline - or mean - of data plotted on a control chart that meets the customer's requirements for a product or service.






12. Risk response planning technique for a threat that creates changes to the project management plan that are meant to either eliminate the risk or to protect the project objectives from its impact.






13. Modification that allows an acceleration of the successor activity.






14. Someone with management authority over an organizational unit within a functional organization.






15. Processes required to ensure timely and appropriate generation - collection - distribution - storage - retrieval - and ultimate disposition of project information






16. Condition or situation unfavorable to the project - a negative set of circumstances - a negative set of events - a risk that will have a negative impact on a project objective if it occurs - or a possibility for negative changes






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






18. Document that describes how the project scope will be defined - developed and verified and how the work breakdown structure will be created and defined and that provides guidance on how the project scope will be managed and controlled by the project






19. Estimate of the amount of work that has been completed on an activity or a work breakdown structure component






20. Type of procurement document used to request proposals from prospective sellers of products or services.






21. Form of progressive elaboration planning where the work to be accomplished in the near term is planned in detail at a low level of the work breakdown structure - while the work far in the future is planned at a relatively high level of the work break






22. Graphical representation of situations showing causal influences - time ordering of events and other relationships among variables and outcomes






23. Identifying - documenting - approving or rejecting and controlling changes to the project baselines






24. Multiple attributes associated with each schedule activity that can be included within the activity list. activity attributes include activity codes - predecessor activities - successor activities - logical relationships - leads and lags - resource r






25. The amount of funds - budget - or time needed above the estimate to reduce the risk of overruns of project objectives to a level acceptance to the organization






26. The calculation of late finish dates and late start dates for uncompleted portions of all schedule activities. determined by working backward through the schedule network logic from the projects end date






27. Planned dates for performing schedule activities and planned dates for meeting schedule milestones






28. Document that describes how procurement processes from developing procurement documentation through contract closure will be managed






29. Quantitative risk analysis and modeling technique used to determine which risks have the most potential impact on the project. typical display of results is in the form of a tornado diagram






30. Performing the work defined in the project management plan to achieve the project's objectives






31. Summary level project schedule that identifies the major deliverables and work breakdown structure components and key schedule milestones






32. Calendar of working days or shifts that establishes those dates on which schedule activities are worked and nonworking days that determine those dates on which schedule activities are idle






33. Tracking team member performance - providing feedback - resolving issues and managing changes to optimize project performance






34. Describes when and how human resource requirements will be met






35. Continuously improving and detailing a plan as more detailed and specific information and more accurate estimates become available as the project progresses and thereby producing more accurate and complete plans that result from the successive iterat






36. Identifying quality requirements and/or standards for the project and product and documenting how the project will demonstrate compliance






37. Document that establishes criteria and activities for developing and controlling the project schedule






38. Assumptions are factors that - for planning purposes - are considered to be true - real - or certain without proof or demonstration






39. Bar chart showing the amount of time that a resource is scheduled to work over a series of time periods.






40. A documented tabulation of schedule activities that shows the activity description - activity identifier - and a sufficiently detailed scope of work description so project team members understand what work is to be performed






41. Estimate or prediction of conditions and events in the projects future based on information and knowledge available at the time of the forecast. information is based on the project's past performance and expected future performance






42. Those processes performed to finalize all activities across all project management process groups to formally close the project or phase






43. Identifying early and late start dates as well as early and late finish dates for the uncompleted portions of project schedule activities






44. A product - result or service generated by a process






45. Calculation of the early start and early finish dates for the uncompleted portions of all network activities






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






47. Collection of logically related project activities - usually culminating in the completion of a major deliverable. project phase is a component of the project life cycle






48. The process of managing procurement relationships - monitoring contract performance - and making changes and corrections as needed






49. Process which generates hundreds or thousands of probable performance outcomes based on probability distributions for cost and schedule on individual tasks. the outcomes are used to generate a probability distribution for a project as a whole.






50. Request for proposal - but may have a narrower or more specific meaning