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






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. A calendar of working days and non- working days that determines those dates on which each specific resource is ideal or can be active; typically defines the resource specific holidays and resource availability periods; the calendars that specify whe






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






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






6. A subdivision (fragment) of a project schedule network diagram - used to illustrate or study some potential or proposed schedule condition - such as changes in preferential schedule logic or project scope.






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






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






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






10. The process of collecting and distributing performance information - including status reports - progress measurements - and forecasts to stakeholders.






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






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






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






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






15. A management control point where the resource plans - scope - schedule and actual cost are integrated and compared to earned value for performance measurement.






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






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






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






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






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






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






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






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






24. The work that must be done to deliver a product with the specified features and functions






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






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






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






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






29. Projects are frequently divided into better manageable components or subprojects. Subprojects are often contracted to an external enterprise or another functional unit in the performing organization.






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






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






32. Process of defining how to conduct risk management activities for a project.






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






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






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






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






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






38. Deliverable- oriented grouping of project components that organizes and defines the total scope of the project - work not in the WBS is outside the scope of the project.






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






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






41. Defines what kinds of competencies are required from what kind of individuals or groups and in what time frames.






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






43. Process of formalizing acceptance of the completed project deliverables






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






45. Risks that remain after planned responses have been implemented - as well as those that have been deliberately accepted.






46. A provision in the project management plan to mitigate cost and/or schedule risk. Often used with a modifier to provide further details on what types of risk are meant to be mitigated.






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






48. A modification of a logical relationship that allows an acceleration of the successor activity. A negative lead is equivalent to a positive lag.






49. A process of systematically gathering and analyzing quantitative and qualitative information to determine whose interests should be taken into account throughout the project. It identifies the interests - expectations - and influence of the stakehold






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