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






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






3. Summary level schedule that identifies the major schedule milestone






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






5. One or more numerical or text values that identify characteristics of the work or in some way categorize the schedule activity that allows filtering and ordering of activities within reports






6. Quantifiable deviation - departure or divergence away from a known baseline or expected value






7. Developing a detailed description of the project and product






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






9. Any item - internal or external - that is required by a process before that process proceeds






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






11. Aggregating the estimated costs of individual activities or work packages to establish an authorized cost baseline






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






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






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






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






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






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






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






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






20. Amount of time that a schedule activity can be delayed without delaying the early start date of any immediately following schedule activities.






21. Action taken to bring a defective or nonconforming component into compliance with requirements or specifications






22. The process of obtaining seller responses - selecting a seller and awarding a contract






23. Collection of projects or programs and other work that are grouped together to facilitate effective management of that work to meet strategic business objectives






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






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






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






27. Provider of products - services or results






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






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






30. Learning gained from the process of performing the project






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






32. Graphical representation of situations showing causal influences - time ordering of events and other relationships among variables and outcomes






33. Cost - time - quality - technical or resource value used as a parameter and which may be included in product specification. crossing the threshold should trigger some action.






34. Identifying and documenting relationships among project activities






35. Person or organization that is actively involved in the project or whose interests may be positively or negatively affected by execution or completion of the project






36. Common way to determine whether a risk is considered low - moderate - or high by combining the two dimensions of a risk: its probability of occurrence and its impact on objectives if it occurs






37. Area of project management defined by its knowledge requirements and described in terms of its component processes - practices - inputs - outputs - tools and techniques






38. Calendar of working days and non-working days that determines those dates on which each specific recourse is idle or can be active






39. Deliverable or project work component at the lowest level of each branch of the work breakdown structure






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






41. Document that specifies in a complete precise verifiable manner the requirements - design behavior or other characteristics of a system component - product - result or service






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






43. Budgeted cost of work scheduled






44. Form of progressive elaboration planning where the work to be accomplished in the near term is planned in detail at a low level of the work breakdown structure - while the work far in the future is planned at a relatively high level of the work break






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






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






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






48. The approved estimate for the project or any work breakdown structure component or any schedule activity






49. Monitoring and recording results of executing the quality activities to assess performance and recommend necessary changes






50. The area on either side of the centerline - or mean - of data plotted on a control chart that meets the customer's requirements for a product or service.