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






2. Processes and activities of the performing organization that determine quality policies - objectives and responsibilities so that the project will satisfy the needs for which it was undertaken






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






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






5. Describes when and how human resource requirements will be met






6. Making relevant information available to project stakeholders






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






8. Total costs actually incurred and recorded in accomplishing work performed during a given time period for a schedule activity or work breakdown structure component. actual cost can sometimes be direct labor hours alone - direct costs alone - or all c






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






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






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






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






13. A request - demand or assertion of rights by a seller against a buyer or vice versa for consideration - compensation - or payment under the terms of a legally binding contract (such as for a disputed change)






14. The degree to which a set of inherent characteristics fulfills requirements






15. One of the defining points of a schedule network; a junction point joined to some or all of the other dependency lines






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






17. Subdivision of a phase






18. Analytical technique that uses three cost or duration estimates to represent optimistic - most likely and pessimistic scenarios.






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






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






21. Defined systematic procedure employed by a human resource to perform an activity to produce a product or result or deliver a service that may employ one or more tools






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






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






24. An approved plan for a project - plus or minus approved changes. it is compared to actual performance to determine if performance is within acceptable variance thresholds. generally refers to the current baseline - but may refer to the original or so






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






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






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






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






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






30. The expected total cost of a schedule activity - a work breakdown structure component or the project when the defined scope of work will be completed. Calculated based on performance to date or estimated by the project team based on other factors






31. Analytical technique to determine the essential features and relationships of components in the project management plan to establish a reserve for the schedule duration - budget - estimated cost or funds for a project






32. Reviewing all change requests - approving changes - and managing changes to the deliverables - organizational process assets - project documents and project management plan






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






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






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






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






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






38. Structure that relates the project organizational breakdown structure to the work breakdown structure to help ensure that each component of the project scope of work is assigned to a person or team






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






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






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






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






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






44. Features and functions that characterize a product - service or result






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






46. Modification that allows an acceleration of the successor activity.






47. Examining or measuring to verify whether an activity - component - product - result of service conforms to specified requirements.






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






49. Processes to purchase or acquire the products - services or results needed from outside the project team to perform the work






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