diff --git a/4.Project Management/Planning.lyx b/4.Project Management/Planning.lyx
index f8afe3c..99c0d6f 100644
--- a/4.Project Management/Planning.lyx	
+++ b/4.Project Management/Planning.lyx	
@@ -672,6 +672,20 @@ http://csse.usc.edu/csse/research/COCOMOII/cocomo2000.0/CII_modelman2000.0.pdf
 \end_inset
 
 
+\end_layout
+
+\begin_layout Enumerate
+CCM Maturity Questionnaire 
+\begin_inset Foot
+status open
+
+\begin_layout Plain Layout
+http://resources.sei.cmu.edu/asset_files/SpecialReport/1994_003_001_16265.pdf
+\end_layout
+
+\end_inset
+
+ 
 \end_layout
 
 \begin_layout Standard
@@ -3590,7 +3604,7 @@ In this section we will talk about COCOMO R II Scale Drivers.
 \begin_inset Quotes eld
 \end_inset
 
-scale factor
+Scale Factor
 \begin_inset Quotes erd
 \end_inset
 
@@ -4337,8 +4351,8 @@ PREC
 
 \begin_layout Standard
 Precedentedness.
- This driver reflects the previous experience that developers have in this
- field.
+ This driver reflects the previous experience that developers have in the
+ development of large scale projects.
  Actually, this is our first experience, so we think the best value for
  our team is Low.
  
@@ -4350,9 +4364,11 @@ FLEX
 
 \begin_layout Standard
 Development flexibility.
- This driver will change due to our flexibility degree in the development.
- Our schedule is quite strict, so we choose Low for this project.
- 
+ This driver reflects the degree of flexibility in the development process
+ with respect to the external specication and requirements.
+ Since on side there are very strict requirements on the functionalities
+ but on the other no specific technology was specified to be used, this
+ value will be Low.
 \end_layout
 
 \begin_layout Paragraph
@@ -4362,9 +4378,9 @@ RESL
 \begin_layout Standard
 Risk resolution.
  It reflects the extension of risk analysis.
- A very low value means we have done a little analysis, high means a complete
+ A Very Low value means we have done a poor analysis, High means a complete
  risk analysis.
- We choose High because we did a detailed analysis (Chapter 5).
+ We choose High because we did a detailed analysis (Chapter 6).
  
 \end_layout
 
@@ -4374,9 +4390,8 @@ TEAM 5
 
 \begin_layout Standard
 Team cohesion.
- This value is correlated to how well the development team know each other.
- In this case we are a very cooperative team, so Very high value is our
- choice.
+ This value is an indicator of how well the development team know each other.
+ In this case we are a very cooperative team, so we choose a Very High value.
 \end_layout
 
 \begin_layout Paragraph
@@ -4386,7 +4401,7 @@ PMAT
 \begin_layout Standard
 Process maturity.
  This parameter reflects the process maturity of the organizazion.
- In partic- ular, this parameter has been choosen according to a weighted
+ In particular, this parameter has been choosen according to a weighted
  average of “Yes” answers to CMM Maturity Questionnaire.
  In our case we have chosen High (CMM Level 3).
 \end_layout