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






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






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






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






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






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






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






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






9. Approved modifications to the project schedule that are used to manage the project






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






11. A -specific version of the schedule model used to compare actual results to the plan to determine if preventive or corrective action is needed to meet the project objectives.






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






13. Defines the procedures by which project scope can be changed; includes paperwork - tracking systems and approval levels necessary for authorizing changes.






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






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






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






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






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






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






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






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






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






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






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






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






26. The document that sets out the format and establishes the activities and criteria for planning - structuring - and controlling the project costs. The cost management plan is contained in - or is a subsidiary plan of - the project management plan.






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






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






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






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






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






32. Broader view of Project Cost Management - whereby other than project costs - we consider the effect of project decisions on the cost of using the project's product.






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






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






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






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






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






38. The document that sets out the format and establishes the activities and criteria for planning - structuring - and controlling the project costs. The cost management plan is contained in - or is a subsidiary plan of - the project management plan.






39. Describes the processes concerned with identifying - analyzing - and responding to project risk. It includes planning risk management - identifying risks - performing qualitative risk analysis - performing quantitative risk analysis - planning risk r






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






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






42. Process of formally authorizing a new project or the next phase of an existing project; links the project to the ongoing work of the performing organization






43. A schedule compression technique in which phases or activities normally performed in sequence are performed in parallel. Fast tracking often results in rework and increased risk. Fast tracking only works if activities can be overlapped to shorten the






44. Describes how project scope will be managed and how scope changes will be integrated into the project. It should also include an assessment of the expected stability of the project scope






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






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






47. A modification of a logical relationship that directs a delay in the successor activity.






48. Any modification to the agreed upon project scope as defined by the approved WBS






49. If the performing organization does not have a formal contracting group - then the project team will have to supply both the resources and expertise to support procurement activities






50. A formal procedure for authorizing project work to ensure that work is done by the identified organization at the right time and in proper sequence.