Test your basic knowledge |

Subjects : certifications, capm
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. Projects are frequently divided into better manageable components or subprojects. Subprojects are often contracted to an external enterprise or another functional unit in the performing organization.






2. Process to monitor the status of the project to update the project budget and manage changes to the cost baseline.






3. Describes the processes required to ensure timely and appropriate generation - collection - dissemination and ultimate disposition of project information. It includes identifying stakeholders - planning communication - distributing information - mana






4. Hybrid type of contractual agreements that contain aspects of both cost-reimbursable and fixed- price contracts. Some characteristics: · Open-ended - i.e. - full value of the agreement and the exact quantity of items to be delivered may not be define






5. Activities specifically taken by management and team members to help individual team members work together effectively - thereby improving team performance






6. Dependencies that are contractually required or those inherent in the nature of the work. Often involve physical limitations.






7. Defines the process by which the procurement can be modified. It includes paperwork - tracking systems - dispute resolution procedures - and approval levels necessary for authorizing changes.






8. A documented tabulation of schedule activities that shows the activity description - activity identifier - and a sufficiently detailed scope of work description so project team members understand what work is to be performed.






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






10. The process in which the estimated costs of individual activities or work packages are aggregated to establish an authorized cost baseline.






11. Describes the procurement item in sufficient detail to allow prospective sellers to determine if they are capable of providing the products - services - or results.






12. A hierarchically organized depiction of the project organization arranged so as to relate the work packages to the performing organizational units.






13. Structured method to guide the project team during development of project plan. Standard forms and templates or even complicated simulations may be used.






14. A provision in the project management plan to mitigate cost and/or schedule risk. Often used with a modifier to provide further details on what types of risk are meant to be mitigated.






15. Describes how risk management will be structured and performed on the project.






16. The expected total cost of a schedule activity - a work breakdown structure component - or the project when the defined scope of work will be completed.






17. Process of documenting project purchasing decisions - specifying the approach - and identifying potential sellers.






18. Used to generate - classify - and prioritize product requirements. Some methods used to reach group decisions are: unanimity - majority - plurality - and dictatorship.






19. The process of identifying all people or organizations impacted by the project and documenting relevant information regarding their interests - involvement - and impact on project success.






20. Special category of revised cost estimates to an approved cost baseline.






21. A process of systematically gathering and analyzing quantitative and qualitative information to determine whose interests should be taken into account throughout the project. It identifies the interests - expectations - and influence of the stakehold






22. Factors that limit a buyer's options. E.g. - funds availability






23. Seller prepared documents that describe the seller's ability and willingness to provide the requested product.






24. This is done to take care of risks that were not identified in the risk response plan - or their impact on objectives is greater than expected.






25. Processes and procedures developed for the closing or canceling of projects.






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






27. A documented list of project team members - their project roles - and communication information.






28. Document that formally authorizes a project. Provides project manager with the authority to apply organizational resources to project activities.






29. Charts/ Judgment provided based upon expertise in an application area - knowledge area - discipline - industry - etc. as appropriate for the activity being performed. Such expertise may be provided by any group or person with specialized education -






30. Also called risk symptoms or warning signs - they are indications that a risk has occurred or is about to occur. They may be discovered in the risk identification process and watched in the risk monitoring and control process.






31. Action taken to bring a defective or nonconforming item into compliance with requirements or specifications. It is a frequent cause of project overruns in most application areas.






32. Changing the project management plan to eliminate the threat entirely.






33. Deliverable- oriented grouping of project components that organizes and defines the total scope of the project - work not in the WBS is outside the scope of the project.






34. Predefined approaches to risk analysis and response in some organizations that have to be tailored to a particular project.






35. Forecasts of potential project schedule and cost results listing the possible completion dates or project duration and costs with their associated confidence levels.






36. The work that must be done to deliver a product with the specified features and functions






37. Involves immediate corrective or preventive action as a consequence of quality control measurements.






38. Process of implementing risk response plans - tracking identified risks - monitoring residual risks - identifying new risks - and evaluating risk process effectiveness throughout the project.






39. Special category of revised cost estimates to an approved cost baseline.






40. Modifications to the cost estimation prepared for the project






41. Expectations The process of communicating and working with stakeholders to meet their needs and addressing issues as they occur. Project manager applies appropriate interpersonal skills to manage stakeholder expectations - for example - by building t






42. A calendar of working days and non- working days that determines those dates on which each specific resource is ideal or can be active; typically defines the resource specific holidays and resource availability periods; the calendars that specify whe






43. The planned dates to perform schedule activities and the planned dates for meeting schedule milestones. Includes planned start and finish dates for the project's activities - milestones - work packages - planning packages - and control accounts. This






44. Collection of generally sequential project phases.






45. Integrates scope - cost (or resource) - and schedule measures to help the project management team assess project performance.






46. Reduce the probability and/or consequence of an adverse risk event to be within acceptable threshold limits.






47. Describes the processes required to make the most effective use of the people involved with the project. It includes developing the human resource plan - acquiring the project team - developing the project team - and managing the project team.






48. Group of related projects managed in a coordinated way to obtain control and benefits that are not available if managed individually.






49. Provides a documented basis for making future project decisions and for confirming or developing common understanding of the project scope among the stakeholders






50. A subdivision (fragment) of a project schedule network diagram - used to illustrate or study some potential or proposed schedule condition - such as changes in preferential schedule logic or project scope.