vault backup: 2023-09-15 11:51:16
This commit is contained in:
@@ -1,5 +1,7 @@
|
||||
---
|
||||
tags:
|
||||
tags:
|
||||
- prince2
|
||||
- company
|
||||
relates-to: "[[Starting my own game company]]"
|
||||
note: literature
|
||||
---
|
||||
@@ -10,7 +12,7 @@ Can be used on any project of any size
|
||||
- [[Continued business justification]] - the WHY of the business and long term value
|
||||
- [[Defined organisation structure]] - Ownership of people so they know what is expected of them
|
||||
- [[Product-based planning]] - product-first, good descriptions and breakdown structure
|
||||
- [[Stage division]] - divide the project into manageable phases
|
||||
- [[Stage]] - divide the project into manageable phases
|
||||
- Tailorable
|
||||
# Project variables
|
||||
Six aspects of [[Project performance|project performance]]:
|
||||
@@ -30,7 +32,13 @@ A project is a temporary organization that is created for the purpose of deliver
|
||||
The project must have a business case that shows that the project is value for money, i.e. there must be a reason to start and continue the project with a clear return on investment.
|
||||
> “Does the project have business justification?” = “Does the project have a valid business case?”
|
||||
|
||||
The [[Business case document|business case document]]
|
||||
The [[Business case document|business case document]] should feature:
|
||||
- full business case
|
||||
- why the project should be done
|
||||
- costs
|
||||
- expected benefits
|
||||
- timescales
|
||||
It should be checked regularly at least at each [[Stage|stage]] of the project.
|
||||
|
||||
|
||||
---
|
||||
|
||||
Reference in New Issue
Block a user