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. Technologies or methods to transfer information among project stakeholders.






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






3. Any numbering system used to uniquely identify each component of the work breakdown structure.






4. Technique that explores the validity of assumptions basing on which every identified project risk is conceived and developed. It identifies risks to the project from inaccuracy - instability - inconsistency - or incompleteness of assumptions.






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






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






7. It is used to identify stakeholders that can provide information on detailed project and product requirements. It contains the following information regarding the identified stakeholders: identification information (name - designation - location - co






8. An organizational placement strategy where the project team members are physically located close to one another in order to improve communication - working relationships - and productivity.






9. Terms used when the source selection decision will be based on price






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






11. A project is a temporary endeavor undertaken to create a unique product - service - or result






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






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






14. It compares cost performance over time - schedule activities or work packages overrunning and under running the budget - and estimated funds needed to complete work in progress.






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






16. Lists or files maintained with information on prospective sellers. These lists will generally have information on relevant past experience and other characteristics of the prospective sellers






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






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






19. Process of identifying and documenting relationships among the project activities. Sequencing can be performed by using project management software or by using manual or automated techniques.






20. Includes the processes that help to estimate - budget - and control costs - so that the project can be completed within the approved budget.






21. Records of previous project results that can be used to identify risks.






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






23. Formal and informal policies that are required for project plan development. Organizational policies include quality management - personnel administration and financial controls.






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






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






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






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






28. Documents the characteristics of the product - result - or service which the project is undertaken to create.






29. Precedence Diagramming Method (PDM) includes four types of dependencies or relationships between activities: 1. Finish to Start; 2. Finish to Finish; 3. Start to Finish; 4. Start to Start






30. A general management technique used to determine whether a particular work can be accomplished by the project team or must be purchased from outside sources.






31. A structured review of the seller's progress to deliver project scope and quality - within cost and on schedule - as compared to the contract.






32. An estimating technique that uses a statistical relationship between historical data and other variables to calculate an estimate for activity parameters - such as scope - cost - budget - and duration. An example for the cost parameter is multiplying






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






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






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






36. Describes the processes required to ensure that the various elements of the project are properly coordinated. It includes developing the project plan - managing the execution of the project plan - monitoring & controlling work - integrating the chang






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






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






39. Describes the processes required to ensure that the project satisfies the needs for which it is undertaken. It includes quality planning - performing quality assurance and control.






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






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






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






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






44. Involves setting a fixed total price for a defined product or service to be provided.






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. Processes and procedures developed for the closing or canceling of projects.






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






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






49. Documented direction for executing the project work to bring expected future performance of the project work in line with the project management plan.






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