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. One or more numerical or text values that identify characteristics of the work or in some way categorize the schedule activity that allows filtering and ordering of activities within reports






2. Document that provides for common and repeated use - rules - guidelines or characteristics for activities or their results






3. The document that describes the communications needs and expectations for the project; how and in what format information will be communicated; when and where each communication will be made; wan who is responsible for providing each type of communic






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






5. Common way to determine whether a risk is considered low - moderate - or high by combining the two dimensions of a risk: its probability of occurrence and its impact on objectives if it occurs






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






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






8. Person or group that provides financial resources in cash or in kind for the project






9. A histogram - ordered by frequency of occurrence - that shows how many results were generated by each identified cause






10. Collection of schedule activity dependencies that makes up a project schedule network diagram






11. Type of procurement document used to request price quotations from prospective sellers of common or standard products or services






12. Indications that a risk has occurred or is about to occur. also called risk symptoms or warning signs. should be watched or monitored in the risk monitoring and control process.






13. Provision in the project management plan to mitigate cost and or schedule risk. modifier: management reserve (unknown risks) - contingency reserve (known - but unplanned risks)






14. Sum of products - services and results to be provided as a project






15. Logical relationship where completion of work of the successor activity cannot finish until the completion of work of the predecessor activity.






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






17. Launching a process that can result in the authorization of a new project






18. Implementing risk response plans - tracking identified risks - monitoring residual risks - identifying new risks and evaluating risk process throughout the project






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






20. Approved specific version of the detailed scope statement - work breakdown structure (WBS) and its associated WBS dictionary






21. The value of work performed expressed in terms of the approved budget assigned to that work for a schedule activity or work breakdown structure component. ALSO BCWP.






22. Monitoring and recording results of executing the quality activities to assess performance and recommend necessary changes






23. Deliverable oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables






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






25. Person or organization that is actively involved in the project or whose interests may be positively or negatively affected by execution or completion of the project






26. Group of potential causes of risk. such as technical - external - organizational - environmental - project management. a category may include subcategories






27. Hierarchically organized depiction of the project organization arranged so as to relate the work packages to the performing organizational units






28. An estimating technique that uses the values of parameters - such as scope - cost - budget - and duration or measures of scale such as size - weight - and complexity from a previous similar activity as the basis of estimating the same parameter or me






29. Aggregation of the processes - tools - techniques - methodologies - resources and procedures to manage a project






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






31. A short unique numeric or text identification assigned to each schedule activity to differentiate that project activity from other project activities. typically unique within any one project schedule network diagram






32. Float (total float - free float)






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






34. Degree - amount or volume of risk that an organization or individual will withstand






35. Those processes performed to complete the work defined in the project management plan to satisfy project objectives






36. Requests to expand or reduce the project scope - modify policies - processes - plans or procedures - modify costs or budgets - or revise schedules






37. Developing a document that formally authorizes a project or phase and documenting initial requirement that satisfy the stakeholders needs and expectations






38. Risk response planning technique that indicates the project team has decided not to change the project management plan to deal with a risk - or is unable to identify any other suitable response strategy






39. The approved estimate for the project or any work breakdown structure component or any schedule activity






40. Shortening the project schedule duration without reducing the project scope






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






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






43. Structure in which the project manager shares responsibility with the functional managers for assigning priorities and directing the work of persons assigned to the project






44. Risk that arises as a direct result of implementing a risk response






45. Change to project scope. almost always requires an adjustment to the project cost or schedule






46. Management methodology for integrating scope - schedule and resources and for objectively measuring project performance and progress. performance is measured by determining the budgeted cost of work performed (earned value) and comparing it to the ac






47. Aggregating the estimated costs of individual activities or work packages to establish an authorized cost baseline






48. Depiction in a diagram format of the inputs - process actions - and outputs of one or more processes within a system






49. A quantitative assessment of the likely amount or outcome. usually applied to project costs - resources - effort and durations.






50. Compares technical accomplishments during project execution to the project management plan's schedule of planned technical achievements.