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. Organizational body or entity assigned various responsibilities related to the centralized and coordinated management of those projects under its domain.






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






3. Hierarchically organized depiction of the identified project risks arranged by risk category and subcategory that identifies the various areas and causes of potential risks.






4. A condition or situation favorable to the project - a positive set of circumstances - a positive set of events - a risk that will have a positive impact.






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






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






7. Processes that organize and manage the project team






8. Any of all external environmental factors and internal organizational environmental factors that surround or influence the projects success. these factors are from any or all of the enterprises involved in the project and include organizational cultu






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






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






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






12. Performed to defined a new project or a new phase of an existing project by obtaining authorization to start the project or phase






13. Identifying the specific actions to be performed to produce the project deliverables






14. Process of numerically analyzing the effect of identified risks on overall project objectives






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






16. Hierarchal organization where each employee has one clear superior and staff are grouped by areas of specialization and managed by a person with expertise in that area.






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






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






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






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






21. Structure in which the project manager shares responsibility with the functional managers for assigning priorities and directing the work of persons assigned to the project






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






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






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






25. The time in calendar units between the actual start date of the schedule activity and either the data date of the project schedule if the schedule activity is in progress or the actual finish date if the schedule activity is complete






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






27. Analysis. a statistical technique that calculates the average outcome when the future includes scenarios that may or may not happen. used in decision tree analysis.






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






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






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






31. A general data gathering and creativity technique that can be used to identify risks - ideas or solutions to issues by using a group of team members or subject matter experts






32. Those processes performed to finalize all activities across all project management process groups to formally close the project or phase






33. Centralized coordinated management of a program to achieve the program's strategic objectives and benefits






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






35. Point in time that work was scheduled to start on a schedule activity. called planned start date.






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






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






38. Float (total float - free float)






39. Risk that arises as a direct result of implementing a risk response






40. A formally constituted group of stakeholders responsible for reviewing - evaluating - approving - delaying or rejecting changes to a project - with all the decisions and recommendations being recorded






41. Any continuous series of schedule activities connected with logical relationships in a project schedule network diagram






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






43. Quantitative risk analysis and modeling technique used to determine which risks have the most potential impact on the project. typical display of results is in the form of a tornado diagram






44. Permission and direction to begin work on a specific schedule activity or work package or control account. sanctions project work to ensure that the work is done by the identified organization - at the right time - and in the proper sequence






45. Tracking team member performance - providing feedback - resolving issues and managing changes to optimize project performance






46. Point in time that work was scheduled to finish on a schedule activity. called planned finish date






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






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






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






50. Category or rank used to distinguish items that have the same functional use but do not share the same requirements for quality