SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
Search
Test your basic knowledge |
Prince2: Project Management In A Controlled Environment2
Start Test
Study First
Subjects
:
certifications
,
prince2
,
business-skills
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. The procedure that ensures that all changes that may affect the project's agreed objectives are identified - assessed and either approved - rejected or deferred.
Approver
Daily Log
Change Control
Authorization
2. The restrictions or limitations that the project is bound by.
Constraints
Authority
Activity
Embedding (Prince2)
3. 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.
Agile Methods
Exploit (risk response)
End Project Report
Accept (Risk Response)
4. A description of how and by whom the project's products will be controlled and protected.
Embedding (Prince2)
Acceptance
Benefit
Configuration Management Strategy
5. Advice from the Project Board to inform all stakeholders and the host sites that the project resources can be disbanded and support services - such as space - equipment and access - demobilized. It should indicate a closure date for costs t the pr
Closure Notification
Change Budget
Exploit (risk response)
Deliverable
6. 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)
Exception
End Stage Report
Embedding (Prince2)
Change Authority
7. 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.
Change Authority
Exception Plan
Exploit (risk response)
Baseline
8. 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.
Enhance (risk response)
Acceptance
Customer
Assurance
9. A progress report of the information gathered at a checkpoint - which is given by a team to the Project Manager and which provides reporting data as defined in the Work Package
Deliverable
Concession
Checkpoint Report
Executive
10. The right to allocate resources and make decisions (applies to project - stage - and team levels)
Constraints
Authority
Baseline
Configuration Item Record
11. 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.
Deliverable
Benefits Review Plan
Assumption
Exception Report
12. 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.
Benefits Tolerance
Configuration Management System
Fallback (risk response)
Cost Tolerance
13. 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
Accept (Risk Response)
Benefit
Configuration Item Record
Cost Tolerance
14. 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
End Stage Report
Acceptance Criteria
Configuration Management
Embedding (Prince2)
15. A team-level - time-driven review of progress.
Approval
Checkpoint
Configuration Management Strategy
Benefits Review Plan
16. 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.
Approver
Closure Notification
Accept (Risk Response)
Baseline Management Product
17. 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
Embedding (Prince2)
Checkpoint Report
Daily Log
Deliverable
18. Technical and administrative activities concerned with the creation - maintenance and controlled change of configuration throughout the life of the product.
Customer
Benefit
Configuration Management
End Project Report
19. A risk response to a threat where the threat either can no longer have an impact or can no longer happen
Avoid (risk response)
Checkpoint Report
Exception Report
Concession
20. A risk response to an opportunity by seizing the opportunity to ensure that it will happen and that the impact will be realized.
Communication Management Strategy
Event-Driven Control
Exploit (risk response)
Contingency
21. The justification for an organizational activity (project) - which typically contains costs - benefits - risks and time scales - and against which continuing viability is tested.
Business Case
Baseline Management Product
Customer
Authority
22. The point at which an authority is granted.
Authorization
Acceptance
Cost Tolerance
Constraints
23. 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'
End Project Report
Benefits Tolerance
Exploit (risk response)
Fallback (risk response)
24. A statement about the quality expected from the project product - captured in the Project Product Description.
25. 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
Daily Log
Customer
End Stage Assessment
Configuration Item
26. This is a review by the Project Board to approve (or reject) an Exception Plan.
Exception Assessment
Constraints
Configuration Management Strategy
Checkpoint
27. 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.
Configuration Item Record
Baseline Management Product
Configuration Item
Customer's Quality Expectations
28. 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.
Configuration Management System
Executive
Accept (Risk Response)
Approval
29. 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
Daily Log
Corporate or Program Standards
Concession
Enhance (risk response)
30. A description of the means and frequency of communication between the project and the project stakeholders.
Event-Driven Control
Communication Management Strategy
Executive
Authorization
31. 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.
Center of Excellence
Constraints
Checkpoint
DSDM Atern
32. 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
Assumption
Center of Excellence
End Stage Report
Benefit
33. A record that describes the status - version and variant of a configuration item - and any details of important relationships between them.
Activity
Configuration Item Record
Benefits Review Plan
Fallback (risk response)
34. 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
Change Budget
Communication Management Strategy
Assurance
Concession
35. The measurable improvement resulting from an outcome perceived as an advantage by one or more stakeholders.
Center of Excellence
Corporate or Program Standards
Exception Plan
Benefit
36. Reference levels against which an entity is monitored and controlled.
Event-Driven Control
Closure Notification
Baseline
Configuration Management Strategy
37. A process - function or task that occurs over time - has recognizable results and is managed. It is usually defined as part of a process or plan.
Configuration Management Strategy
Closure Recommendation
End Stage Report
Activity
38. An off-specification that is accepted by the Project Board without corrective action.
Dis-benefit
Acceptance
Constraints
Concession
39. The formal act of acknowledging that the project has met agreed acceptance criteria and thereby met the requirements of its stakeholders
Benefit
Exploit (risk response)
Baseline
Acceptance
40. 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.
Cost Tolerance
Exploit (risk response)
Center of Excellence
Exception Report
41. A set of actions to resolve a threat to a plan's tolerances or a defect in a product.
Checkpoint Report
Center of Excellence
Corrective Action
Customer
42. A corporate coordinating function for portfolios - programs and projects providing standards - consistency of methods and processes - knowledge management - assurance and training.
Benefits Tolerance
Baseline Management Product
Constraints
Center of Excellence
43. 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.
End Stage Report
Benefits Tolerance
Customer
Corporate or Program Standards
44. The money allocated to the Change Authority available to be spent on authorized requests for change.
Cost Tolerance
Checkpoint Report
DSDM Atern
Change Budget
45. A control that takes place when a specific event occurs. This could be - for example - the end of a stage - the completion of the Project Initiation Documentation - or the creation of an Exception Report - it could also include organizational ev
Exception
Exception Report
Event-Driven Control
Communication Management Strategy
46. The person or group who commissioned the work and will benefit from the end results.
Customer
Exception Assessment
Baseline
Constraints
47. The formal confirmation that a product is complete and meets its requirements (less any concessions) as defined by its Product Description.
Approval
Embedding (Prince2)
Approver
Concession
48. 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'.
Cost Tolerance
Change Control
Accept (Risk Response)
Change Authority
49. 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.
Assurance
Corrective Action
Exception Plan
Benefits Tolerance
50. A report given by the Project Manger to the Project Board - that confirms the handover of all products and provides and updated Business Case and an assessment of how well the project has done against the original Project Initiation Documentation.
End Stage Report
Business Case
End Project Report
Change Authority