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. Document that graphically depicts the project team members and their interrelationships for a specific project






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






3. Schematic display of the logical relationships among the project schedule activities. drawn from left to right.






4. Communicating and working with stakeholders to meet their needs and address issues as they occur






5. Processes concerned with conducting risk management planning - identification - analysis - responses and monitoring and control on a project






6. Specific type of management activity that contributes to the execution of a process and that may employ one or more techniques and tools






7. An organizational placement strategy where the project team members are physically located close to one another in order to improve communication - working relationships and productivity






8. Work that must be performed to deliver a product - service or result with the specified features and functions






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






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






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






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






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






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






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






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






17. Work breakdown structure component below the control account with known work content but without detailed schedule activities.






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






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






20. A change request that has been processed through the integrated change control process and approved






21. Fixed date imposed on a schedule activity or schedule milestone. usually - start no earlier than - finish no later than






22. Processes required to ensure that the project includes all the work required and only the work required to complete the project successfully






23. An estimating technique that uses a statistical relationship between historical data and other variables (sq. foot in construction - lines of code in software development) to calculate an estimate for activity parameters such as scope - cost - budget






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






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






26. Developing options and actions to enhance opportunities and to reduce threats to project objectives






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






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






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






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






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






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






33. Documented direction to perform an activity that can reduce the probability of negative consequences associated with project risks






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






35. Group of persons with a shared objective who fulfill their roles with little or no time spent meeting fact to face.






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






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






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






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






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






41. Processes that organize and manage the project team






42. Deliverable or project work component at the lowest level of each branch of the work breakdown structure






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






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






45. Significant point or event in the project






46. A category of projects that have common components significant in such projects - but are not needed or present in all projects. application areas are usually defined in terms of either the product or the type of customer or industry sector






47. Any item - internal or external - that is required by a process before that process proceeds






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






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






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