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. Describes the procurement item in sufficient detail to allow prospective sellers to determine if they are capable of providing the products - services - or results.






2. Schematic displays of the logical relationships (dependencies) among the project schedule activities; always drawn from left to right to reflect project work chronology






3. Descriptions of which resources will be available at what times and in what patterns necessary for schedule development






4. An uncertain event or condition that - if it occurs - has a positive or negative effect on the project objective.






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






6. Process of developing options and actions to enhance opportunities and to reduce threats to project objectives. Includes the identification and assignment of individuals to take responsibility for each agreed-to and funded risk response.






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






8. Risk Audits examine and document the effectiveness of risk responses in dealing with identified risks and their root causes - as well as the effectiveness of the risk management process.






9. Collection of generally sequential project phases.






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






11. Generally used when considerations like technical approach and technical skills are paramount in source selection






12. Modifications to the cost estimation prepared for the project






13. A formal or informal approach to obtain information from stakeholders by talking to them directly






14. For many procurement items - the procuring organization may elect to either prepare its own independent estimate - or have an estimate of costs prepared by an outside professional estimator - to serve as a benchmark on proposed responses.






15. Process of redefining the cost performance/schedule/performance measurement/technical baseline. If cost variances are severe - re-baselining is needed to provide a realistic measure of performance.






16. 1. Operations do not have any timelines. Projects are temporary and have finite time duration. 2. Operation's objective is usually to sustain the business. Project's objective is to achieve the target and close the project.






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






18. The process of confirming human resource availability and obtaining the team necessary to complete project assignments.






19. Bring together prequalified stakeholders and subject matter experts to learn about their expectations and attitudes about a proposed product - service - or result






20. An accepted action performed to bring projected future project performance in line with the project plan. These actions have to be documented.






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






22. Outcome of activities performed to accomplish the project.






23. Seller is a subcontractor - vendor - or supplier - who will typically manage the work of the project. Buyer is the customer who has outsourced work to the seller.






24. Any modification to the contents of the project plan or the supporting details.






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






26. Description of the product of the project - provides important information about any technical issues or concerns that would need to be considered during procurement planning






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






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






29. Incurred for the exclusive benefit of the project (e.g. - salaries of full-time project staff).






30. Includes the processes required to purchase or acquire products - services - or results needed from outside the project team.






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






32. Considers the characteristics of those prospective staff who are available to join the project team.






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






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






35. It can include correspondence - memos - meeting minutes - and documents describing the project.






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






37. Process of monitoring the status of the project and product scope and managing changes to the scope baseline.






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






39. Features or services that characterize a product - result - or service






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






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






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






43. Repository that provides for collection - maintenance - and analysis of data gathered and used in the risk management process. Use of this database assists risk management throughout the organization and - over time - forms the basis of a risk lesson






44. A method of estimating a component of work. The work is decomposed into more detail. An estimate is prepared of what is needed to meet the requirements of each of the lower - more detailed pieces of work. These estimates are then aggregated into a to






45. Specify lessons that can be learned from each and every project - even from projects which are failures. They need to be documented. Most companies prefer post-implementation meetings and case studies to document Lessons Learned






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






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






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






49. Structured review of the project plans and assumptions - prior project files - contracts - and other information.






50. Technologies or methods to transfer information among project stakeholders.