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. A table that links requirements to their origin and traces them throughout the project life cycle






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






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






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






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






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






7. Source of variation that is not inherent in the system - is not predictable - and it intermittent. also referred to as assignable cause.






8. Logical relationship where completion of the successor schedule activity is dependent upon the initiation of the predecessor schedule activity






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






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






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






12. Processes involved in estimating - budgeting - and controlling costs so that the project can be completed within the approved budget






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






14. Judgment provided based upon expertise in an application area - knowledge area - discipline - industry - etc. as appropriate for the activity being performed.






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






16. An imperfection or deficiency in a project component where that component does not meet requirements or specifications and needs to be either repaired or replaced






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






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






19. The right to apply project resources - expend funds - make decisions or give approvals






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






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






22. Float (total float - free float)






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






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






25. Developing an approximation of the monetary resources needed to complete project activities






26. Response to a negative risk that has occurred - workaround is not planned in advance of the occurrence of the risk event






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






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






29. Documents and data on prior project including project files - records - correspondence - closed contracts - and closed projects






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






31. Schedule activity that follows a predecessor activity as determined by their logical relationship






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






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






34. Processes required to track - review and regulate the progress and performance of the project - identify any areas in which changes to the plan are required and initiate the corresponding changes.






35. Logical grouping of project management inputs - tools and techniques and outputs. includes initiating processes - planning processes - executing processes - monitoring and controlling processes and closing processes. NOT project phases






36. Describes how the project management team will implement the performing organizations quality plan.






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






38. Documenting project purchasing decisions - specifying the approach and identifying potential sellers






39. Analytical technique used to determine basic underlying reason that causes a variance or defect or risk






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






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






42. Processes required to manage the timely completion of a project






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






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






45. An artifact that is produced - is quantifiable and can be either an end item in itself or a component item






46. The latest possible point in time that a schedule activity maybe completed based upon schedule network logic - the completion date and any constraints assigned to the schedule activities without violating a schedule constraint or delaying the project






47. Collect project performance data with respect to a plan - produce performance measures and report and disseminate performance information






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






49. A method of estimating a component of work. the work is decomposed into more detail. an estimate is prepared of what is needed to meet the requirements of each of the lower - more detailed pieces of work - and these estimates are then aggregated into






50. A planning technique that subdivides the project scope and project deliverables into smaller - more manageable components - until the project work associated with accomplishing the project scope and providing the deliverables is defined in sufficient