Test your basic knowledge |

Prince2: Project Management In A Controlled Environment2

Instructions:
  • Answer 50 questions in 20 minutes. 2 minutes extra for reading the instructions.
  • 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 risk response to a threat by putting in place a fallback plan for the actions that will be taken to reduce the impact of the threat should the risk occur.






2. The review by the Project Board and Project Manager of the End Stage Report to decide whether to approve the Stage Plan. According to the size and criticality of the project - the review may be formal or informal. The authority to process should be






3. The permissible deviation in a plan's cost that is allowed before the deviation needs to be escalated to the next level of management. Cost tolerance is documented in the respective plan. See also 'tolerance'.






4. The measurable improvement resulting from an outcome perceived as an advantage by one or more stakeholders.






5. The permissible deviation in the expected benefit that is allowed before the deviation needs to be escalated to the next level of management. Benefits tolerance is documented in the Business Case . See also 'tolerance'






6. A person or group to which the Project Board may delegate responsibility for the consideration of requests for change or off-specifications. The Change Authority may be given a change budget and can approve changes within the budget.






7. An outcome that is perceived as negative by one or more stakeholders. It is an actual consequence of an activity whereas - by definition - a risk has some uncertainty about whether it will materialize.






8. A description of how and by whom the project's products will be controlled and protected.






9. A report given by the Project Manager to the Project Board at the end of each management stage of the project. This provides information about the project performance during the stage and the project status at stage end.






10. These are over-arching standards that the project must adhere to. They will influence the four project strategies ( Communication Management Strategy - Configuration Management Strategy - Quality Management Strategy and the Risk Management Strategy






11. The person or group (e.g. a Project Board) who is identified and authorized to approve a (management or specialist) product as being complete and fit for purpose.






12. A tangible or intangible object produced as a result of the project that is intended to be delivered to a customer (either internal or external). A deliverable could be a report - a document - a server upgrade or any other building block of an over






13. A description of the exception situation - its impact - options - recommendations and impact of the recommendation. This report is prepared by the Project Manager for the Project Board.






14. This is plan that often follows an Exception Report. For a Stage Plan exception - it covers the period from the present to the end of the current stage - if the exception were at project level - the Project Plan would be replaced.






15. The single individual with overall responsibility that the project meets its objectives and delivers the projected benefits. This individual should ensure that the project maintains its business focus - that it has clear authority - and that the wo






16. Technical and administrative activities concerned with the creation - maintenance and controlled change of configuration throughout the life of the product.






17. An agile delivery framework developed and owned by the DSDM consortium. Atern uses a time-boxed and iterative approach to product development and is compatible with Prince2.






18. The formal confirmation that a product is complete and meets its requirements (less any concessions) as defined by its Product Description.






19. A record that describes the status - version and variant of a configuration item - and any details of important relationships between them.






20. The formal act of acknowledging that the project has met agreed acceptance criteria and thereby met the requirements of its stakeholders






21. Reference levels against which an entity is monitored and controlled.






22. All the systematic necessary to provide confidence that the target (system - process - organization - program - project - outcome - benefit - capability - product output - deliverable) is appropriate. Appropriateness might be defined subject






23. A set of actions to resolve a threat to a plan's tolerances or a defect in a product.






24. A type of management product that defines aspects of the project and - once approved - is subject to change control.






25. A team-level - time-driven review of progress.






26. An off-specification that is accepted by the Project Board without corrective action.






27. The procedure that ensures that all changes that may affect the project's agreed objectives are identified - assessed and either approved - rejected or deferred.






28. A statement that is taken as being true for the purposes of planning - but which could change later. An assumption is made where some facts are not yet known or decided - and is usually reserved for matters of such significance that - if they chan






29. An entity that is subject to configuration management. The entity may be a component of a product - a product - or a set of products in a release.






30. Principally - software development methods that apply the project approach of using short time-boxed iterations where products are incrementally developed. Prince2 is compatible with agile principles.






31. What an organization needs to do to adopt Prince2 as its corporate project management method. See also - in contrast - 'tailoring' - which defines what a project needs to do to apply the method to a specific project environment.






32. A prioritized list of criteria that the project product must meet before the customer will accept it - i.e. measurable definitions of the attributes required for the set of products to be acceptable to key stakeholders






33. The right to allocate resources and make decisions (applies to project - stage - and team levels)






34. A recommendation prepared by the Project Manager for the Project Board to send as a project closure notification when the board is satisfied that the project can be closed.






35. This is a review by the Project Board to approve (or reject) an Exception Plan.






36. A risk response to an opportunity where proactive actions are taken to enhance both the probability of the event occurring and the impact of the event should it occur.






37. A situation where it can be forecast that there will be a deviation beyond the tolerance levels agreed between Project Manager and Project Board (or between Project Board and corporate or program management)






38. A description of the means and frequency of communication between the project and the project stakeholders.






39. Used to record problems/concerns that can be handled by the Project Manager informally.






40. The relationship between products or activities. For example - the development of Product C cannot start until Products A and B have been completed. Dependencies can be internal or external. Internal dependencies are those under the control of the P






41. Something that is held in reserve typically to handle time and cost variances - or risks. Prince2 does not advocate the use of contingency because estimating variances are managed by setting tolerances - and risks are managed through appropriate ri






42. A risk response to an opportunity by seizing the opportunity to ensure that it will happen and that the impact will be realized.






43. The money allocated to the Change Authority available to be spent on authorized requests for change.






44. The point at which an authority is granted.






45. The person or group who commissioned the work and will benefit from the end results.






46. A statement about the quality expected from the project product - captured in the Project Product Description.


47. The justification for an organizational activity (project) - which typically contains costs - benefits - risks and time scales - and against which continuing viability is tested.






48. A risk response to a threat where a conscious and deliberate decision is taken to retain the threat - having discerned that it is more economical to do so than to attempt a risk response action. The threat should continue to be monitored to ensure t






49. The set of processes - tools and databases that are used to manage configuration data. Typically - a project will use the configuration management system of either the customer or supplier organization.






50. A plan that defines how and when a measurement of the achievement of the project's benefits can be made. If the project is being managed within a program - this information may be created and maintained at the program level.