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. Fixed price contract where the buyer pays the seller a set amount regardless of the sellers costs






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






3. Planning technique used to provide products - services and results that truly reflect customer requirements by translating those customer requirements into the appropriate technical requirements for each phase of project product development






4. Group of related schedule activities aggregated at some summary level and displayed as a single activity (at the summary level)






5. Approximating the number of work periods needed to complete individual activities with estimated resources






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






7. Technique that computes or iterates the project cost or project schedule many times using input values selected at random from probability distributions of possible costs or durations - to calculate a distribution of total project costs or completion






8. Total number of work periods required to complete a schedule activity or work breakdown structure component.






9. Document describing how roles and responsibilities - reporting relationships and staffing management will be addressed and structured for the project






10. A point that is not settled or is under discussion or over which there are opposing views or disagreements






11. Centralized management of one or more portfolios - which includes identifying - prioritizing - authorizing - managing and controlling projects - programs and related work - to achieve specific strategic business objectives






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






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






14. Directing - managing - performing and accomplishing the project work - providing the deliverables and providing work performance information






15. Risk response planning technique associated with threats that seeks to reduce the probability of occurrence or impact of a risk to below an acceptable threshold






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






17. A group of related projects managed in a coordinated way to obtain benefits and control not available from managing them individually.






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






19. Extending or generating parallel schedule network paths from the same node in a project schedule network diagram. characterized by schedule activity with more than one successor activity






20. Number of labor units required to complete a schedule activity or work breakdown structure component






21. System of practices - techniques - procedures and rules used by those who work in a discipline






22. Budgeted cost of work scheduled






23. Project schedule compression that changes network logic to overlap phases that would normally be done in sequence






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






25. Approved integrated scope-schedule-cost plan for the project work against which project execution is compared to measure and manage performance






26. A condition or situation favorable to the project - a positive set of circumstances - a positive set of events - a risk that will have a positive impact.






27. Identifying all people or organizations impacted by the project and documenting relevant information regarding their interest - involvement and impact on project success






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






29. Provider of products - services or results






30. Subsystem of overall project management system. collection of formal documented procedures that defines how project work will be authorized to ensure that the work is done by the identified organization - at the right time and in the proper sequence.






31. Logical relationship where initiation of work of the successor activity depends on the completion of work of the predecessor activity






32. The aggregate of things used by an organization in any undertaking such as equipment - apparatus - tools - machinery - gear - material.






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






34. Document that graphically depicts the project team members and their interrelationships for a specific project






35. Structure in which the project manager has full authority to assign priorities - apply resources and direct the work of persons assigned to the project






36. Members of the project team who are directly involved in project management activities






37. Information gathering technique examines the project from the perspective of each projects strengths - weaknesses - opportunities - and threats to increase the breadth of the risks considered by risk management






38. The enterprise whose personnel are directly involved in doing the work of the project






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






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






41. Schedule network diagramming technique in which schedule activities are represented by boxes or nodes. schedule activities are graphically linked by one or more logical relationships to show the sequence in which the activities are performed






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






43. Any of all process related assets - from any or all of the organizations involved in the project that are or can be used to influence the project's success. these process assets include formal or informal plans - policies - procedures and guidelines.






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






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






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






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






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






49. Documenting the actions necessary to define - prepare - integrate and coordinate all subsidiary plans






50. Subdivision (fragment) of a project schedule network diagram - usually representing a subproject or work package.