SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
|
Email
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. 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.
Accept (Risk Response)
Customer's Quality Expectations
Approver
Change Authority
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
Acceptance
Exploit (risk response)
End Stage Assessment
Closure Notification
3. Reference levels against which an entity is monitored and controlled.
Baseline
Benefits Review Plan
Daily Log
Checkpoint Report
4. 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
Change Control
Exception Report
Concession
Dependencies (plan)
5. The point at which an authority is granted.
Closure Notification
Deliverable
Configuration Management System
Authorization
6. 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.
Dis-benefit
Accept (Risk Response)
Communication Management Strategy
Approver
7. This is a review by the Project Board to approve (or reject) an Exception Plan.
Customer
Change Control
Activity
Exception Assessment
8. The measurable improvement resulting from an outcome perceived as an advantage by one or more stakeholders.
Corporate or Program Standards
Benefit
Dis-benefit
Change Budget
9. 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.
Configuration Management System
DSDM Atern
Corporate or Program Standards
Acceptance Criteria
10. The person or group who commissioned the work and will benefit from the end results.
Acceptance
Avoid (risk response)
Customer
Assurance
11. 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.
Activity
Authority
Benefits Review Plan
Corporate or Program Standards
12. 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)
Center of Excellence
Daily Log
Change Authority
13. A risk response to a threat where the threat either can no longer have an impact or can no longer happen
Business Case
Checkpoint Report
Avoid (risk response)
Checkpoint
14. A statement about the quality expected from the project product - captured in the Project Product Description.
Warning
: Invalid argument supplied for foreach() in
/var/www/html/basicversity.com/show_quiz.php
on line
183
15. 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
Corporate or Program Standards
Benefits Review Plan
Closure Recommendation
16. 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.
Exception Report
Closure Recommendation
Event-Driven Control
Configuration Item
17. 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.
Dependencies (plan)
Enhance (risk response)
Configuration Item
Fallback (risk response)
18. The procedure that ensures that all changes that may affect the project's agreed objectives are identified - assessed and either approved - rejected or deferred.
Cost Tolerance
Change Control
Agile Methods
Exception Assessment
19. A description of how and by whom the project's products will be controlled and protected.
Configuration Management Strategy
Acceptance
Enhance (risk response)
Assumption
20. 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
End Stage Assessment
Activity
Configuration Item
Corporate or Program Standards
21. 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
Event-Driven Control
Corrective Action
Deliverable
Customer
22. A risk response to an opportunity by seizing the opportunity to ensure that it will happen and that the impact will be realized.
Center of Excellence
Constraints
Exploit (risk response)
Avoid (risk response)
23. 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
Deliverable
Acceptance Criteria
Benefits Tolerance
Configuration Management System
24. A type of management product that defines aspects of the project and - once approved - is subject to change control.
Authorization
Baseline Management Product
Customer
Benefits Review Plan
25. 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.
Benefit
Baseline Management Product
Benefits Tolerance
Benefits Review Plan
26. A corporate coordinating function for portfolios - programs and projects providing standards - consistency of methods and processes - knowledge management - assurance and training.
Benefits Review Plan
Closure Recommendation
Daily Log
Center of Excellence
27. 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.
Change Authority
Dependencies (plan)
Closure Recommendation
Exception Report
28. 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
Constraints
Exception Plan
Configuration Item
Executive
29. A team-level - time-driven review of progress.
Change Authority
Concession
Checkpoint
Benefit
30. 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.
Benefits Review Plan
Configuration Item Record
Enhance (risk response)
Closure Recommendation
31. Technical and administrative activities concerned with the creation - maintenance and controlled change of configuration throughout the life of the product.
Accept (Risk Response)
Exception Assessment
Configuration Management
Approval
32. The formal act of acknowledging that the project has met agreed acceptance criteria and thereby met the requirements of its stakeholders
Daily Log
Benefits Tolerance
Acceptance
Change Budget
33. Used to record problems/concerns that can be handled by the Project Manager informally.
Benefits Review Plan
Daily Log
Event-Driven Control
Assumption
34. 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
Customer's Quality Expectations
Constraints
End Stage Assessment
35. 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.
Agile Methods
Event-Driven Control
Embedding (Prince2)
Benefit
36. The formal confirmation that a product is complete and meets its requirements (less any concessions) as defined by its Product Description.
Daily Log
Executive
Approval
Exception
37. The money allocated to the Change Authority available to be spent on authorized requests for change.
Deliverable
Configuration Management System
Approval
Change Budget
38. 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
Closure Recommendation
Contingency
Exception Assessment
Daily Log
39. The restrictions or limitations that the project is bound by.
Exception Assessment
Corrective Action
Constraints
End Project Report
40. 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
Event-Driven Control
End Stage Report
Embedding (Prince2)
Communication Management Strategy
41. 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
Dis-benefit
Change Authority
Acceptance
42. 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.
Center of Excellence
End Stage Report
Fallback (risk response)
Dependencies (plan)
43. 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 Authority
Dependencies (plan)
Constraints
44. An off-specification that is accepted by the Project Board without corrective action.
Checkpoint
Concession
Configuration Item Record
Exception Report
45. The justification for an organizational activity (project) - which typically contains costs - benefits - risks and time scales - and against which continuing viability is tested.
Benefit
DSDM Atern
Business Case
Closure Notification
46. 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.
Exploit (risk response)
End Project Report
Concession
Checkpoint Report
47. A set of actions to resolve a threat to a plan's tolerances or a defect in a product.
Constraints
Daily Log
Corrective Action
Communication Management Strategy
48. 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'
Contingency
Benefits Tolerance
Configuration Item Record
Daily Log
49. 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)
Benefits Review Plan
Exception
Closure Notification
End Project Report
50. 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.
Authorization
Change Control
Configuration Management
Agile Methods