Kennisconsult

 - project brief
 - project brief

Verklaring die het doel, de kosten, tijd en prestatie-eisen, en beperkingen voor een project beschrijft. Het voorstel wordt voorafgaand aan het project gemaakt tijdens het proces Starting up a Project en het wordt gebruikt tijdens het proces Initiating a Project om de Project Initiation Documentation en de componenten daarvan te maken. Het wordt vervangen door de Project Initiation Documentation en niet bijgehouden.
Bron: http://www.prince-officialsite.com/InternationalActivities/TranslatedGlossaries.aspx
"© Crown copyright 20XX. All rights reserved. Material is reproduced with the permission of the Office of Government Commerce under delegated authority from the Controller of HMSO."


A major document typically prepared as the basis for an executive management go/no-go decision at an executive control point. Following a go decision, the document becomes the baseline or control basis for the project control cycle.
Source: Max Wideman.com
Copyright: Wideman Comparative Glossary of Common Project Management Terms v3.1 is copyright by R. Max Wideman, March 2002.

A document submitted with a capital appropriation request for the implementation of a project. A good project brief should include at a minimum: An introduction or executive summary A general statement of business aims and objectives associated with the project A statement of project scope The economic and technical approach adopted Justification, alternatives, areas of uncertainty and risk Regulatory approvals and requirements Preliminary design sketches, block diagrams, standards project Master Schedule Procurement Plan project estimate and proposed capital appropriation request Other resources required from the sponsoring organization e.g. land, space, staff, etc. Financial statement and economic projections Cash flow projection Quality, schedule and cost controls project team organization
Source: Max Wideman.com
Copyright: Wideman Comparative Glossary of Common Project Management Terms v3.1 is copyright by R. Max Wideman, March 2002.

Statement that describes the purpose, cost, time and performance requirements, and constraints for a project. It is created pre-project during the Starting up a Project process and is used during the Initiating a Project process to create the Project Initiation Documentation and its components. It is superseded by the Project Initiation Documentation and not maintained.
source: http://www.prince-officialsite.com/InternationalActivities/TranslatedGlossaries.aspx
"© Crown copyright 20XX. All rights reserved. Material is reproduced with the permission of the Office of Government Commerce under delegated authority from the Controller of HMSO."

• Management (management) >> * - management >> Projectmanagement (project management) >> Informatie (information)
• Management (management) >> * - management >> Projectmanagement (project management) >> Prince2 (Prince2)