diff --git a/opensym2017/content/04-process.tex b/opensym2017/content/04-process.tex
index ae30570..a25dffb 100644
--- a/opensym2017/content/04-process.tex
+++ b/opensym2017/content/04-process.tex
@@ -82,7 +82,14 @@ We defined some level of meeting granularity to avoid to generate overheads to
 the developers. We had a strategical and validating meeting with MPOG (the
 former once in a month and the latter each 15th day), release plaining with the
 entire team (one per month), and finally a sprint planning (one each 15th day).
-Figure X is a diagram that represents our meeting organization.
+Figure \ref{fig:meeting} is a diagram that represents our meeting organization.
+
+\begin{figure}[hbt]
+  \centering
+    \includegraphics[width=\linewidth]{figures/meeting_flows.png}
+  \caption{Meetings cycles}
+  \label{fig:meeting}
+\end{figure}
 
 In the strategical meeting we usually defined the priorities and new features
 with MPOG (we always had to negotiate next steps with them). Normally the
@@ -124,3 +131,27 @@ Notice that this workflow gave to us and to the MPOG a full traceability from
 high view of the feature to the low view (code). This provided a way to MPOG
 validated all worked done and proof the concept that work with open source
 project can give a proper view to them check.
+
+\subsection{Tools for communication and management}
+
+Our team had many people worked together, and most of the seniors worked in a
+different city remotely. Also, we tried to keep our work completely clear to
+the Brazilian government and citizens interested in follow the project. To
+handle those cases, we used a set of tools to communication and other to manage
+the project.
+
+For communication between member in different places, we used: google-talk with
+tmate, IRC, and mailing-list. When one student had to work in pair with a
+senior, normally, they used google-hangout for communication and they shared a
+session with tmate which allow them to share the same terminal. For questions
+and fast discussion, we used IRC. For general notification, we used the
+mailing-list.
+
+For managing the project we used the SPB Portal to validate it by ourselves and
+because it had all the required tools. We basically create one wiki page per
+release in Gitlab, one milestone per sprint, and one or more issues for address
+one user history. With this approach we achieve two important things: keep all
+the management close to the source code and tracked every feature developed by
+the project.
+
+% Ainda falta adicionar a parte da visita dos seniors e o turno sagrado
diff --git a/opensym2017/content/05-architecture.tex b/opensym2017/content/05-architecture.tex
index 69f0dff..4b0a81e 100644
--- a/opensym2017/content/05-architecture.tex
+++ b/opensym2017/content/05-architecture.tex
@@ -2,7 +2,7 @@
 \label{sec:architecture}
 
 At the point of view of the architecture, two main requirements was brought by
-the Brazilian Federal Government for the new platform were:
+the Brazilian Federal Government for the new platform:
 
 \begin{enumerate}
   \item \textit{Integrate existing FOSS systems}, with minimal differences from
@@ -81,7 +81,11 @@ functionality of each application, a search in the SPB portal might
 return content from any of the applications, be it web pages, mailing
 list posts, or source code.
 
-%TODO: deixar coeso daqui para baixo
+% Falar do devops
+\subsection{Deploy}
+
+The SPB platform was deployed in 7 virtual machines with different functions,
+as we can see in Figure \ref{fig:architecture2}.
 
 \begin{figure*}[hbt]
   \centering
@@ -90,11 +94,6 @@ list posts, or source code.
   \label{fig:architecture2}
 \end{figure*}
 
-\subsection{Deploy}
-
-In real, the SPB platform was deployed in 7 virtual machines with different functions,
-as we can see in Figure \ref{fig:architecture2}.
-
 The \textit{reverseproxy} handles the HTTP requests and redirects them to the
 \textit{integration}, the \textit{email} sends and receives e-mails on behalf
 of the platform and the \textit{monitor} keeps the entire environment tracked.
diff --git a/opensym2017/figures/meeting_flows.png b/opensym2017/figures/meeting_flows.png
new file mode 100644
index 0000000..47eb269
Binary files /dev/null and b/opensym2017/figures/meeting_flows.png differ
--
libgit2 0.21.2