Reverse Definitions Flashcards
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 that it remains tolerable.
Accept ( risk Response)
The formal act of acknowledging that the project has met agreed acceptance criteria and thereby met the requirements of its stakeholders.
Acceptance
A prioritized list of criteria that the project product must meet before the customer will accept, i.e. measurable definitions of the attributes required for the set of products to be acceptable to key stakeholders.
Acceptance criteria
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
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 Method
The formal confirmation that a product is complete and meets its requirements ( less and concessions ) as defined by its Product Description.
Approval
The person or group ( e.g. Project Board) who is identified and qualified and authorized to approve a ( management or specialist) product as being complete and fit for purpose.
Approver
A statement that is taken as being true for true 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 change or turn out not to be true , there will need to be considerable replanning.
Assumption
All the systematic actions necessary to provide confidence that the target ( system, process, organization, programme, project, outcome, benefit, capability, product output, deliverable) is appropriate. Appropriateness might be defined subjectively or objectively in different circumstances, The Implication is that assurance will have a level of independence from that which is being assured. See also Project Assurance and Quality Assurance.
Assurance
The right to allocate resources and make decisions ( applies to project, stages and team levels)
Authority
The point at witch an authority is granted.
Authorization
A risk response to a threat where the threat either can no longer have an impact or can no longer happen
Avoid ( Risk Response )
Reference levels against which an entity is monitored and controlled
Baseline
The measurable improvement resulting from an outcome perceived as an advantage by one or more stakeholders
Benefit
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 programme level.
Benefit Review Plan
The permissible deviation in the expected benefits that is allowed before the deviation need to be escalated to the next level of management. Benefits tolerance is documented in Business Case. See also Tolerance.
Benefits Tolerance
The justification for an organization activity ( project ), which typically contains costs, benefits, risks and timescales, and against which continuing viability is tested.
Business Case
A corporate coordinating function for portfolios, programmes and projects providing standards, consistency of methods and processes, knowledge management, assurance and training
Centre of Excellence
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 that budget.
Change Authority
The money allocated to the Change Authority available to be spent on authorized requests for change.
Change Budget
The procedure that ensures that all changes that may affect the project´s agree objectives are identified, assessed, and either approved, rejected, deferred.
Change Control
A team level, time driven, review of progress
Checkpoint
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.
Checkpoint Report
Advice form 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 to be charged to the project.
Closure Notification
A recommendation prepared by the project manager for the project board to send a project closure notification when the board is satisfied that the project can be closed.
Closure Recommendation
A description of the means and frequency of communication between the project and the project´s stakeholders.
Communication Management
An off-specification that is accepted by the project board without corrective action
Concession
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
A record that describes the status, version, and variant of a configuration item, and details of important relationships between them
Configuration Item Record
Technical and administrative activities concerned with the creation, maintenance and controlled change of configuration through the life of a product
Configuration Management
A description of how and by whom the project´s products will be controlled and protected
Configuration Management Strategy
The set of processes, tools and database that are used to manage configuration data. Typically a project will use configuration management system of either the customer or supplier organization.
Configuration Management System
The restrictions or limitations that the project is bound by.
Constraints
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 risk responses ( including the fallback response that is contingent on the risk occurring)
Contingency
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, Risk management strategy) and the project controls.
Corporate or Program standards
A set of actions to resolve a threat to a plan´s tolerance or a defect in a product.
Corrective Action
The permissible deviation in an 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
The person or group who commissioned the work and will benefit from the end results.
Customer
A statement about the quality expected from the project product, captured in the Project Product Description
Customer´s quality expectations
Used to record problems/concerns that can be handled by the Project Manager Informally
Daily Log
A specialist product that is handed over to a user(s).
Deliverable
The relationship between products or activities
Dependencies can be internal or externals.
Internal dependencies are those under the control of the Project Manager.
External dependencies are those outside the control of the Project Manager.
Dependencies (plan)
An outcome that is perceived as negative by one or more stakeholders. It is a actual consequence of an activity whereas, by definition, a risk has some uncertainty about whether it will materialize.
Dis-benefit
An agile project 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
DSDM Atern
What an organization needs to do to adopt PRINCE2 as its corporate project management method. It differentiates form Tailoring, which defines what a project needs to do to apply the method to a specific project environment.
Embedding (PRINCE2)
A report given by the Project Manager to the Project Board that confirms the handover of al products and provides an updated Business Case and an assessment of how well the project has done against the original Project Initiation Document.
End project Report
There review by the project board and project manager at the End Stage Report to decide whether to approve the next Stage Plan. According to the size and criticality of the project, the review may be formal or informal. The authority to proceed should be documented as a formal record.
End Stage Assessment
A report given by the Project Manager to the Project Board a 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
A risk response to an opportunity where proactive actions are taken to enhance both probability of the event occurring and the impact of the event it should occur.
Enhance ( risk response )
A control that takes place when a specific event occurs.
This could be, for example, the end of a stage, the completition of the Project Initiation documents, or the creation of an Exception Report.
It could also include organization events that may affect the project, such as the end of the financial year.
Event driven control
A situation where it can be forecasted 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
A review by the Project Board to approve ( or reject ) and Exception plan
Exception assessment
A plan that often follow an Exception Report, For a Stage Plan exception it covers the period form the present to the end of the current stage. Of the exception were at project level, the project plan would be replaced.
Exception Plan
A description of the exception situation , its impact, options, recommendation and impact of the recommendation. This report is prepared by the Project Manager for the Project Board.
Exception Report
The single individual with overall responsibility for ensuring that a project meets its objectives and delivers the project benefits. This individual should ensure that the project maintains its business focus, that it has clear authority, and that the work, including risks, is actively managed. The Executive is the chair of the Project board. He or she represents the customer and is responsible for the Business Case.
Executive
A risk response to an opportunity by seizing the opportunity to ensure that it will happen and that the impact will be realized.
Exploit ( risk response )
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.
Fallback ( risk response)
Recommended actions related to unfinished work, ongoing issues and risks, and any other activates needed to take a product to the next phase of its life. These are summarized an included in the End Stage Report ( for phased handover ) and End Project Report.
Follow-on action recommendations
The ongoing activity of maintaining a sound system of internal control by which the directors and officers of an organization ensure that effective management systems, including financial monitoring and control systems, have been put in place to protect assets, earning capacity and the reputation of the organization.
Governance (Corporate)
Those areas of corporate governance that are specifically related to project activities Effective governance of project management ensures that an organization´s project portfolio is aligned to the organization´s objectives, is delivered efficiently and is sustainable.
Governance (project)
The transfer of ownership of a set of products to the respective user(s). The set of product is known as release. There may be more than one handover in the life of a project ( phased delivery), The final handover takes place in the Closing a Project process.
Handover
A time-driven report from the Project Manager to the Project Board on stage progress.
Highlight Report
A site where project work is being undertaken ( for example, an office or a construction site)
Host Site
The result of a particular threat or opportunity actually occurring , or the anticipation of such as a result.
Impact ( of risk)
The exposure arising from a specific risk before any action has been taken to manage it
Inherent risk
The period form when the Project Board authorizes initiation to when they authorize the project ( or decide not to go ahead with the project ).
The detailed planning and establishment of the project management infrastructure is covered by the Initiating a Project Process.
Initiation Stage
A relevant event that has happened ,was not planned, and requires management action. It can be any concern, query, request for change, suggestion or off specification raised during a project. Project issues can be about anything to do with the project.
Issue
A register used to capture and maintain information on all the issues that are being managed formally. The Issue Register should be monitored by the Project Manager on a regular basis.
Issue Register
A report containing the description, impact assessment and recommendation for a request for change , off specification or a problem/concern. It is only created for those issues that need to be handled formally.
Issue Report
An informal repository for lessons that apply to this project of future projects.
Lessons Log
A report that documents any lessons that can be usefully applied to other projects.
The purpose of the report is to provoke action so that the positive lessons from a project become embedded in the organization´s way of working and that the organization is able to avoid the negative lessons on future projects.
Lessons Report
Informal repositories managed by the Project Manager that do not require any agreement by the Project Board on their format and composition.
Logs
PRINCE2 has two logs
The Daily LOG
The Lessons Log.
A product that will be required as part of managing the project, and establishing and maintaining quality (e.g, Highlight report, end stage report). The management product stay constant, whatever the type of project and can be used as described, or with any relevant modifications, for all projects.
Management Product
There are three types of management products
Baselines, records and report
The section of a project that the Project Manager is managing on behalf of the Project Board at any one time, at the end of which the project Board will wish to review progress to date, state of the project plan, business case, risks, and the next stage plan in order to decide whether to continue with the project.
Management Stage