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






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






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






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






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






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






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






8. It shortens the project schedule without changing the project scope - in order to meet schedule constraints - imposed dates - or other schedule objectives. -. This technique includes crashing and fast tracking.






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






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






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






12. The process of analyzing activity sequences - durations - resource requirements - and schedule constrains to create the project schedule






13. Charts/ 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 -






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






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






16. Describes the processes required to ensure timely completion of the project. It includes defining activities - sequencing activities - estimating activity resources - estimating activity durations - developing the schedule - and controlling the sched






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






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






19. Estimating or predicting future project status and progress based on knowledge and information available at the time of forecasting.






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






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






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






23. Probability that a risk will occur.






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






25. Process of formalizing acceptance of the completed project deliverables






26. A general data gathering and creativity technique that can be used to identify risks - ideas - or solutions to issues by using a group of team members or subject matter experts which data can be addressed later in Perform qualitative and quantitative






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






28. Collection of generally sequential project phases.






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






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






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






33. Process of obtaining seller responses - selecting a seller - and awarding a contract






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






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






36. The process of approximating the number of work periods needed to complete individual activities with estimated resources






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






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






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






40. The conclusion of a project phase is marked by a review of both key deliverables and project performance till date to determine if the project should continue into its next phase and detect and correct errors cost-effectively. These phase end reviews






41. Allows for probabilistic treatment of both network logic and activity duration estimates






42. Systematic process of planning - identifying - analyzing - responding - and monitoring and controlling project risk. It increases the probability and impact of positive events - and decrease the probability and impact of negative events in the projec






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. Refers to the centralized management of one or more portfolios to achieve strategic business objectives. Portfolio management ensures that the portfolios are reviewed to ascertain that resources are allocated as per priority and the allocation is con






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






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






47. Process of assessing and combining the impact and the likelihood of identified risks. Prioritizes risks according to their potential effect on project objectives for further analysis or action.






48. Describes how individual requirements meet the business need for the project.






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






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