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






2. Process of identifying the specific actions to be performed to produce the project deliverables.






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






4. Checklists are structured tools - usually component specific - used to verify that a set of required steps has been performed and to ensure consistency in frequently performed tasks. These can be developed based on historical information and knowledg






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






6. Project team must measure itself periodically against the expectations of those outside the project.






7. Technique to evaluate the degree to which data about risks is useful for risk management.






8. A deliverable is a unique - tangible and verifiable work/product. Each project phase is marked by the completion of one or more deliverables.






9. A mathematical technique to forecast future outcomes based on historical results. This is performed using run charts.






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






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






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






13. Includes the processes that organize - manage - and lead the project team.






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






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






16. A functional organization has a hierarchy in which every employee has one clear superior. Staff members are grouped by areas of specialization. Functional organizations may still have projects - but the perceived scope of the project is defined by th






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






18. Process of monitoring the status of the project to update project progress and manage changes to the schedule baseline






19. Involves developing a better understanding of the product of the project






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






21. List of risks includes those that pose the greatest threat or present the greatest opportunity to the project together with a measure of their impact.






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






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






24. The process of determining project stakeholders' information needs and defining a communication approach.






25. The process of making relevant information available to project stakeholders in a timely manner - as planned. Performed throughout the entire project life cycle and in all management processes.






26. A group of documented procedure used to apply technical and administrative direction and surveillance to: a) Identify and document the system's functional and physical characteristics; b)Control any changes to such characteristics; c) Record and repo






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






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






29. Provide a structure that ensures a comprehensive process of systematically identifying risks to a consistent level of detail and contributes to the effectiveness and quality of the Identify Risks process. They include categories like technical - exte






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






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






32. Includes all those activities designed to enhance the competencies of the project team members. Training can be formal or informal.






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






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






35. Collection of generally sequential project phases.






36. Describes how the procurement processes (from developing procurement documentation through contract closure) will be managed






37. Dependencies determined by the Project Management Team; involve a relationship between project activities and non-project activities (i.e. - dependencies on issues that are beyond the scope of the project). These dependencies are outside the project






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






39. A formal - approved document used to define how the project is executed - controlled and monitored. It can either be at a detailed or high level and may contain one or more subsidiary plans.






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






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






42. The policies - guidelines - or procedures that govern the recruitment of staff.






43. Policies - guidelines and procedures that can help the project management team with various aspects of organizational planning.






44. A schedule compression technique in which cost and schedule tradeoffs are analyzed to determine how to obtain the greatest amount of compression for the least incremental cost. Crashing only works for activities where additional resources will shorte






45. Documentation resulting from project activities. These files may also maintain records of other projects that are detailed enough to aid in developing cost estimates.






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






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






48. Measuring - examining and testing undertaken to determine whether results conform to requirements; also called reviews - product reviews - audits - and walkthroughs






49. A partially complete document in a predefined format that provides a defined structure for collecting - organizing - and presenting information and data.






50. Risks that arise as a direct result of implementing a risk response.