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. Processes required to manage the timely completion of a project






2. Identifying and documenting relationships among project activities






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






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






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






6. Identifying and documenting project roles - responsibilities - and required skills - reporting relationships and creating a staffing management plan.






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






8. An entry in the work breakdown structure that can be at any level






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






10. Document used to record and describe or denote selected items identified during execution of a process or activity






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






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






13. Those criteria - including performance requirements and essential conditions which must be met before project deliverables are accepted






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






15. Expected cost needed to complete all the remaining work for a schedule activity - work breakdown structure component or project.






16. List of project team members - their project roles and communication information






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






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






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






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






21. Collection of projects or programs and other work that are grouped together to facilitate effective management of that work to meet strategic business objectives






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






23. Model used in conjunction with manual methods or project management software to perform schedule network analysis to generate the project schedule for use in managing the executing or a project






24. Action taken to bring a defective or nonconforming component into compliance with requirements or specifications






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






26. Determining project stakeholder information needs and defining a communication approach






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






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






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






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






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






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






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






34. Collection of generally sequential project phases whose name and number are determined by the control needs of the organization involved in the project






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






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






37. Narrative description of the project scope - including major deliverables - project assumptions - project constraints and a description of work that provides a documented basis for making future project decisions and for confirming or developing a co






38. The process of finalizing all activities across all of the project management process groups to formally complete the project or phase






39. Temporary endeavor undertaken to create a unique product - service or result






40. Something toward which work is to be directed - a strategic position to be attained - or a purpose to be achieved - a result to be obtained - a product to produced or a service to be performed






41. A component of work performed during the course of a project






42. The date up to or through which the project's reporting system has provided actual status and accomplishments. also called as-of date and time-now date.






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






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






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






46. Document describing how project risk management will be structured and performed on the project. contains the list of project risks - the results of risk analysis and risk responses






47. The smallest unit of time used in scheduling a project. calendar units are generally in hours - days - or weeks - but can also be in quarters years - months - shifts - or even minutes






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






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






50. Summary level schedule that identifies the major schedule milestone