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. Seller prepared documents that describe the seller's ability and willingness to provide the requested product.






2. Factors which - for planning purposes - are considered to be true - real or certain.






3. The process to develop an approximation (estimate) of the monetary resources needed to complete project activities.






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






5. Clarify the structure - requirements and other terms of the purchases so that mutual agreement can be reached prior to signing the contract.






6. Risks that remain after planned responses have been implemented - as well as those that have been deliberately accepted.






7. Complete set of indexed contract documentation - including the closed contract - that is prepared for inclusion with the final project files






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






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






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






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






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






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






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






15. The expected cost needed to complete all the remaining work for a schedule activity - work break down structure component - or the project.






16. Used to rate or score seller proposals






17. Process of defining and documenting stakeholders' needs to meet the project objectives






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






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






20. Process of developing a detailed description of the project and product






21. Factors that - for planning purposes - will be considered true - real or certain.






22. An analytical technique used to determine the basic underlying reason that causes a variance or a defect or a risk. Root cause may underlie more than one variance or defect or risk. Root cause analysis is done as part of corrective action - Helps ide






23. An estimating technique that uses the values of parameters - such as scope - cost - budget - and duration or measure of scale such as size - weight - and complexity - from a previous - similar activity as the basis for estimating the same parameter o






24. Process of managing procurement relationships - monitoring contract performance - ad making changes and corrections as needed.






25. Costs allocated to the project by the performing organization as a cost of doing business (e.g. - salaries of corporate executives). Usually calculated as a percentage of direct costs.






26. Seeking to shift the consequences of the risk to a third party together with the ownership for the response.






27. Describes the need - justification - requirements - and current boundaries for the project.






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






29. Project team accepts the risk - i.e. team decides not to change the project plan to deal with the risk - or is unable to identify any other suitable response strategy.






30. The document that describes the communication needs and expectations for the project; how and in what format information will be communicated; when and where each communication will be made; and who is responsible for providing each type of communica






31. Charts that are used to show positions and relationships in a graphical format.






32. Organize and summarize the information gathered - and present the results of any analysis as compared to the performance measurement baseline. Reports should provide status and progress of the project at the required level of detail.






33. Process of estimating the type and quantities of resources like materials - people - equipment - or supplies required to perform each project activity






34. The process to identify and document project roles - responsibilities - and required skills - report relationships - and create a staffing management plan.






35. Activities that assist in developing/enhancing the ability of team members to work together effectively and contribute to the success of the project team. It improves the people skills - technical competencies - and overall team environment and proje






36. It consists of tools and techniques used to gather - integrate and disseminate the outputs of project management processes. Supports all aspects of the project from initiating through closing - and can include both manual and automated systems.






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






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






39. It includes the processes required to ensure timely and appropriate generation - collection - dissemination - storage - retrieval - and ultimate disposition of project information.






40. Allow for non-sequential activities (e.g. Loops or Conditional Branches); e.g. - GERT(Graphical Evaluation and Review Technique) and System Dynamics






41. Meetings held to assess project status and/or progress.






42. Responses to emerging risks that was previously unidentified or accepted. These were not planned in advance of the occurrence of the risk event.






43. Activities should have a coding structure to allow sorting and/or extractions based on different attributes assigned to the activities.






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






45. Calculates the theoretical early start and finish dates - and late start and finish dates - for all activities without regard to any resource limitations. This is done by performing a forward and backward pass analysis through the schedule network.






46. Mutually binding legal agreement that obligates the seller to provide the specified products - services - or results - and obligates the buyer to compensate the seller.






47. An authorized time-phased budget at completion (BAC) used to measure - monitor - and control overall cost performance on the project. Developed as a summation of the approved budgets by time period and is typically displayed in the form of an S-curve






48. A method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it.






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






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