diff --git a/Notes/Literature/PRINCE2.md b/Notes/Literature/PRINCE2.md
index 6a30207..463a860 100644
--- a/Notes/Literature/PRINCE2.md
+++ b/Notes/Literature/PRINCE2.md
@@ -20,7 +20,7 @@ Six aspects of [[Project performance|project performance]]:
 - *Time* - when will the project be finished ?
 - *Cost* - what is the cost and the return of investment
 - *Quality* - usable software that passes quality checks and is usable
-- *Scope* - the scope must be clear for all stakeholder through the [[PPD]]
+- *Scope* - the scope must be clear for all [[Stakeholder|stakeholders]] through the [[PPD]]
 - *Benefits* - benefits must be known, agreed upon and measurable
 - *Risk* - risk must be manageable
 # Project definition
@@ -77,8 +77,32 @@ The purpose of tailoring is to:
 - Ensure that the project method is project’s environment into account. (i.e., if working in a financial environment, then align it with the existing management structure).
 - Ensure with the project board that the project’s controls are based on the project’s scale, complexity, importance, capability, and risk.
 # Themes
-
+[[Themes]] are knowledge areas, a part of the project that should be continually addressed. Each theme provides knowledge on a specific area of project management such as business case, planning, quality, risk, etc. They should be tailored to the needs of the project depending on their gravity given the needs:
+- Business case: Why? ROI? Benefits?
+- Organization: Who? Responsibilities?
+- Quality: Level of quality for each product characteristic?
+- Plans: How? How much? When? What (Product description)?
+- Risk: What if X happens?
+- Change: How to deal with changes requests and issues?
+- Progress: Where are we now compared to the plan, show progress
+## Theme 1 - [[Business case]]
+This theme should provide information to help make better decisions regarding the business case to judge weather it's: 
+- Desirable: Determine if the output is really required by the users
+- Viable: Is it technically possible to deliver this product?
+- Achievable: Is it possible to deliver the future benefits?
+At every moment during the project, [[Continued business justification]] states that the business case should be valid, which this theme documents and in order to assess as such.
+## Theme 2 - [[Organisation]]
+This theme aims to help define the project's structure of accountability and responsibilities. A PRINCE2 Project should:
+- Have correct business, user, and supplier representation
+- Have defined responsibilities for directing, managing, and delivering the project
+- Have regular reviews (end of each stage) of the project to check that all is on track
+- Have a good communication flow to and from stakeholders
+So, each project needs to have direction, management, control, and communication.
+[[Stakeholder]]: A stakeholder is any person or group that can be affected by the project or can affect the project. This includes the project team, potential users and other persons external to the project as well as those who may be negatively affected.
+## Theme 3 - [[Quality]]
+This theme 
 
 ---
+
 # References
 - https://prince2.wiki/extras/what-is-prince2/
\ No newline at end of file