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. Any numbering system used to uniquely identify each component of the work breakdown structure






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






3. Reserve






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






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






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






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






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






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






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






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






12. Project schedule network diagram drawn in such a way that the position and length of the schedule activity represents its duration. bar chart that includes schedule network logic






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






14. Organizational body or entity assigned various responsibilities related to the centralized and coordinated management of those projects under its domain.






15. Analytical technique that uses mathematical models to forecast future outcomes based on historical results. it is a method of determining the variance from a baseline parameter by using prior progress reporting periods data and projecting how much th






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






17. Inclusive term - describes the sum of knowledge within the profession of project management. includes proven traditional practices that are widely applied and innovative practices that are emerging.






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






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






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






22. Implementing risk response plans - tracking identified risks - monitoring residual risks - identifying new risks and evaluating risk process throughout the project






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






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






25. Hierarchal structure of resources by resource category and resource type used in resource leveling schedules and to develop resource limited schedules and which may be used to identify and analyze project human resource management






26. Partially complete document in a predefined format that provides a defined structure for collecting - organizing and presenting information and data






27. Collection of logically related project activities - usually culminating in the completion of a major deliverable. project phase is a component of the project life cycle






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






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






30. Buyer pays the seller a set amount (as defined by the contract) and the seller can earn an additional amount if the seller meets defined performance criteria






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






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. Request for proposal - but may have a narrower or more specific meaning






34. The value of work performed expressed in terms of the approved budget assigned to that work for a schedule activity or work breakdown structure component. ALSO BCWP.






35. A short unique numeric or text identification assigned to each schedule activity to differentiate that project activity from other project activities. typically unique within any one project schedule network diagram






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. Tracking team member performance - providing feedback - resolving issues and managing changes to optimize project performance






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






39. The enterprise whose personnel are directly involved in doing the work of the project






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






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






43. Making relevant information available to project stakeholders






44. Condition or capability that must be met or possessed by a system - product - service result or component to satisfy a contract - standard - specification or other formally imposed document.






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






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






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






48. Application of knowledge - skills - tools and techniques to project activities to meet the project requirements






49. Launching a process that can result in the authorization of a new project






50. Planning technique used to provide products - services and results that truly reflect customer requirements by translating those customer requirements into the appropriate technical requirements for each phase of project product development