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 quantitative assessment of the likely amount or outcome. usually applied to project costs - resources - effort and durations.






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






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






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. Partially complete document in a predefined format that provides a defined structure for collecting - organizing and presenting information and data






6. Those processes performed to complete the work defined in the project management plan to satisfy project objectives






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






8. The earliest point in time on which the uncompleted portions of a schedule activity can start - based on the schedule network logic - the data date and any schedule constraints.






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






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






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






12. A technique that explores the accuracy of assumptions and identifies risks to the project from inaccuracy - inconsistency - or incompleteness of assumptions






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






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






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






16. Smaller portion of the overall project created when a project is subdivided by their logical relationship






17. Output from performing project management processes and activities. results include outcomes and documents.






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






19. Graphic display of cumulative costs - labor - hours - percentage of work or other quantities - plotted against time. used to depict planned value - earned value and active costs.






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






21. Float (total float - free float)






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






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






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






25. Narrative description of products - services or results






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






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






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






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






30. Provider of products - services or results






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






32. Determining which risks may affect the project and documenting their characteristics






33. Sum of products - services and results to be provided as a project






34. Documents utilized in bid and proposal activities - which include the buyer's invitation for bid - invitation for negotiations - request for information - request for quotation - request for proposal and sellers responses






35. Logical relationship where initiation of the work of the successor schedule activity depends upon the initiation of the work of the predecessor schedule activity






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






37. Adding features and functionality (project scope) without addressing the effects on time - costs - and resources or without customer approval






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






39. Defined function to be performed by a project team member






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






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






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






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






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






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






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






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






49. Extending or generating parallel schedule network paths from the same node in a project schedule network diagram. characterized by schedule activity with more than one successor activity






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