Section 6.2 done

4.Project Management/Planning.lyx

@@ -10199,8 +10199,7 @@ Marginal
 
 \begin_layout Plain Layout
 No preventive solutions are available.
- This is not strictly bad.
- news
+ This is not strictly bad news.
 \end_layout
 
 \end_inset
@@ -10365,8 +10364,8 @@ Possible solution
 \begin_inset Text
 
 \begin_layout Plain Layout
-The team is very small (3 people) but homogeneous; if someone leaves or
- gets ill then the remaining team would have serious repercussions
+A sudden illness or termination of a team member may bring several repercussion
+ due to the small size of the group.
 \end_layout
 
 \end_inset
@@ -10393,8 +10392,9 @@ Critical
 \begin_inset Text
 
 \begin_layout Plain Layout
-All team members must be able to cover all development sections and cooperate
- effectively
+The remaining team members must be cooperate effectively and have to be
+ able to continue the development.
+ 
 \end_layout
 
 \end_inset
@@ -10405,9 +10405,9 @@ All team members must be able to cover all development sections and cooperate
 \begin_inset Text
 
 \begin_layout Plain Layout
-No estimations/schedules have been made before this project.
- A lack of experience in this area can lead to serious errors in evaluating
- development time
+No schedules or estimations have been made before this project.
+ Lack of experience in this area can lead to major errors in evaluating
+ development time.
 \end_layout
 
 \end_inset
@@ -10434,7 +10434,7 @@ Critical
 \begin_inset Text
 
 \begin_layout Plain Layout
-Studying previous works on a similar subject can be very helpful in this
+Studying previous works and projects on a similar subject can be very helpful.
 \end_layout
 
 \end_inset
@@ -10445,8 +10445,8 @@ Studying previous works on a similar subject can be very helpful in this
 \begin_inset Text
 
 \begin_layout Plain Layout
-A sudden growth in requirements can lead to a rush to meeting deadlines,
- jeopardizing the overall quality
+A requirements growth can lead to rush meeting deadlines, severely decreasing
+ the overall quality.
 \end_layout
 
 \end_inset
@@ -10473,9 +10473,8 @@ Critical
 \begin_inset Text
 
 \begin_layout Plain Layout
-Thinking with a broader mind on the first stages can be very helpful; however,
- the team should be careful against over-engineering (which can also paralyze
- the development)
+The team has to distinguish over-engineering from actual requirements; furthermo
+re, planning the first stages with a broader can be very helpful.
 \end_layout
 
 \end_inset
@@ -10487,7 +10486,7 @@ Thinking with a broader mind on the first stages can be very helpful; however,
 
 \begin_layout Plain Layout
 Collaboration issues can sometimes be crucial, especially when dealing with
- task divisions
+ task divisions.
 \end_layout
 
 \end_inset
@@ -10514,8 +10513,8 @@ Medium
 \begin_inset Text
 
 \begin_layout Plain Layout
-Meeting often can be a solution, other than explicitly writing whose responsibil
-ity for each task is
+Periodic meetings help the team to be constantly organized and not overwhelmed
+ by tasks.
 \end_layout
 
 \end_inset
@@ -10526,8 +10525,7 @@ ity for each task is
 \begin_inset Text
 
 \begin_layout Plain Layout
-Due to several overlapping tasks the team is involved into, the project
- is very likely to suffer from schedule delays 
+The project may be delayed to multiple overlapping tasks 
 \end_layout
 
 \end_inset
@@ -10554,9 +10552,9 @@ Critical
 \begin_inset Text
 
 \begin_layout Plain Layout
-A strict organization among the team components is fundamental.
- This implies a constant cooperation between developers, in order to squeeze
- even the tiniest time slots available for this project
+A good organization among the team components is fundamental.
+ This leads to a better teamwork which allows to maximize the throughput.
+ 
 \end_layout
 
 \end_inset