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. Structured review of the project plans and assumptions - prior project files - contracts - and other information.






2. Documents how requirements will be analyzed - documented - and managed throughout the project






3. Describes how risk management will be structured and performed on the project.






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






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






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






7. Meetings that are regularly scheduled to exchange and analyze information about the project and its performance.






8. Factors that will limit the project management team's options (e.g. - a predefined budget)






9. Complete set of indexed contract documentation - including the closed contract - that is prepared for inclusion with the final project files






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






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






12. Modifications to the cost estimation prepared for the project






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






14. Focused sessions that bring key cross-functional stakeholders together to define product requirements






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






16. A collection of formal (note: not informal) documented procedures - which defines how the documentation and project deliverables will be managed - changed and approved.






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






18. Quantities to be performed for each specific category - and can be used to estimate activity durations






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






20. Features or services that characterize a product - result - or service






21. The process to identify and document project roles - responsibilities - and required skills - report relationships - and create a staffing management plan.






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






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






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






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






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






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






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






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






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






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






32. Seeking to shift the consequences of the risk to a third party together with the ownership for the response.






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






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






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






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






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






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






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






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






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






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






43. Process of estimating the type and quantities of resources like materials - people - equipment - or supplies required to perform each project activity






44. Process of defining and documenting stakeholders' needs to meet the project objectives






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






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






47. In a projectized organization - most of the organization's resources are involved in project work - and Project Managers have a great deal of independence and authority.






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






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






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