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. Someone with management authority over an organizational unit within a functional organization.






2. Analyzing activity sequences - durations - resource requirements and schedule constraints to create the project schedule






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






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






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






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






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






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






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






10. Type of procurement document whereby the buyer requests a potential seller to provide various pieces of information related to a product or service or seller capability






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






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






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






14. Any unique and verifiable product - result - or capability to perform a service that must be produced to complete a process - phase or project.






15. Document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organization resources to the project activities






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






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






18. Reserve






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






20. A mutually binding agreement that obligates the seller to provide the specified product or service or result and obligates the buyer to pay for it






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






22. Processes and activities needed to identify - define - combine - unify and coordinate the various processes and project management activities within the project management process groups






23. Schedule activity that determines when the logical successor activity can begin or end






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






25. Modification of a logical relationship that directs a delay in the successor activity. activity with a 10 day lag - cannot start until 10 days after an activity is finished






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






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






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. Documents and data on prior project including project files - records - correspondence - closed contracts - and closed projects






30. Technique for estimating that applies a weighted average of optimistic - pessimistic and most likely estimates when there is uncertainty with the individual activity estimates






31. Documents and presentations that provide organized and summarized work performance information - earned value management parameters and calculations - and analyses of project work progress and status






32. Something tangible used in performing an activity to produce a product or result






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






34. Document containing the results of the qualitative risk analysis - quantitative risk analysis and risk response planning. details all identified risks including description - category - cause - probability of occurring - impact on objectives - propos






35. Significant point or event in the project






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






37. Project model that translates the uncertainties specified at a detailed level into the potential impact on objectives that are expressed at the level of the total project. Monte Carlo Analysis






38. Area of project management defined by its knowledge requirements and described in terms of its component processes - practices - inputs - outputs - tools and techniques






39. Application of knowledge - skills - tools and techniques to project activities to meet the project requirements






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






41. Store of historical information and lessons learned about both the outcomes of previous project selection decisions and previous project performance






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






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






44. Uncertain event or condition that has a positive or negative effect on projects objectives






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






46. Describes each component in the work breakdown structure (WBS). for each WBS component - the WBS dictionary includes a brief definition of the scope of statement of work - defined deliverables - a list of associated activities and list of milestones.






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






48. Approach to optimize project life cycle costs - save time - increase profits - improve quality - expand market share - solve problems - and use resources more effectively






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






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