From e10d8141534bc412e84f581ceeca158e87ab206c Mon Sep 17 00:00:00 2001 From: Melissa Wen Date: Thu, 4 Jan 2018 16:56:10 -0200 Subject: [PATCH] [oss-2018] Review Practices --- icse2018/content/06-results.tex | 67 +++++++++++++++++++++++++++++++++---------------------------------- 1 file changed, 33 insertions(+), 34 deletions(-) diff --git a/icse2018/content/06-results.tex b/icse2018/content/06-results.tex index d2b1981..883a2e8 100644 --- a/icse2018/content/06-results.tex +++ b/icse2018/content/06-results.tex @@ -22,45 +22,44 @@ in the Table \ref{practices-table}. \hline \textbf{Decision} & \textbf{Practice Explanation} & \textbf{Benefits} \\ \hline \textbf{Project management and communication on the developing platform itself} -& \begin{itemize} \item Migration of project management and communication into +& +\begin{itemize} +\item Migration of project management and communication into the platform under development using its integrated software components Gitlab -and Mailman \end{itemize} & \begin{itemize} \item Confidence in developed code; -\item Transparency and efficiency in communication; \item Easier monitoring and -increase interactions between development team and public servants; \item -Organically documentation and records generation; \end{itemize} \\ \hline -\textbf{Bring together government staff and development team} & \begin{itemize} +and Mailman +\end{itemize} & +\begin{itemize} +\item Confidence in developed code; +\item Transparency and efficiency in communication; +\item Easier monitoring and +increase interactions between development team and public servants; +\item Organically documentation and records generation; \end{itemize} \\ \hline + +\textbf{Bring together government staff and development team} & +\begin{itemize} \item Biweekly gov staff, senior developers and coaches met to planning and review sprint at the UnB headquarters. \item Most of features under development were discussed on Gitlab Issue Tracker. \item Only strategic decisions or bureaucratic issues involve board directors. \item Deploying SPB intermediated -versions in production \end{itemize} & \begin{itemize} -\item Reducing communication misunderstood; \item Empathy between members on -both sides; Meeting expectations of both sides on developing requirements; -\item Improving the understanding of collaborative development by the -government; \item Aligning both side pace to execute project-related -activities; \item -Increasing government confidence for collaborative projects with the -university; \item Motivating teams; \item -Aligning both side pace to execute project-related activities; \item Improving -translation from one development process to the other; \end{itemize} \\ \hline -%\textbf{Continuous Delivery} & -%\item At each release, DevOps members would go to the ministry to assist its -%infrastructure team in deploying. \end{itemize} & \begin{itemize} \item -%Increasing government confidence for collaborative projects with the -%university; \item Motivating teams; \item Transfering of knowledge about DevOps -%and Continuous Deliveries from academia to gov infrastructure team; \item -%Aligning both side pace to execute project-related activities; \item Improving -%translation from one development process to the other; \end{itemize}\\ \hline -\textbf{Divide development team in "component" fronts} & \begin{itemize} \item -The development was divided into four fronts with a certain self-organization -of tasks. \item IT market professionals with recognized experience on each -front were hired to work in person or remotely. \item For each front, there was -at least one senior developer and the role of coach. \item The meta-coach role -was also defined to coordinate tasks between teams. \end{itemize} & -\begin{itemize} \item Helping conciliation of development processes and -decision-making; \item Creating support-points for students, senior developers, -and gov staff; \item Transfering of knowledge from industry and FLOSS community -to both academia and government; \end{itemize}\\ \hline +versions in production \end{itemize} & +\begin{itemize} +\item Reduce communication misunderstood and develop requirements closer to the expectations of both sides; +\item Improve understanding of collaborative development by MPOG staff +\item Increasing government confidence for collaborative projects with the university; +\item Aligning both side pace to execute project-related activities (Empathy between gov and academia side) +\item Improving translation from one development process to the other; +\end{itemize} \\ \hline + +\textbf{Divide development team in "component" fronts} & +\begin{itemize} +\item The development was divided into four fronts with a certain self-organization of tasks. +\item IT market professionals with recognized experience on each front were hired to work in person or remotely. +\item For each front, there was at least one senior developer and the role of coach. +\item The meta-coach role was also defined to coordinate tasks between teams. \end{itemize} & +\begin{itemize} +\item Helping conciliation of development processes and decision-making; +\item Creating support-points for students, senior developers, and gov staff; +\item Transfering of knowledge from industry and FLOSS community to both academia and government; \end{itemize}\\ \hline \end{tabular}% } \caption{Empirical SPB management method and its benefits} -- libgit2 0.21.2