minor improvements

Paulo Meireles
1 parent 86fc201f
Showing 1 changed file with 17 additions and 16 deletions Show diff stats
opensym2017/content/07-process.tex
@@ -7,17 +7,17 @@ software engineering (from 4th semester or upper).  Since the students could
 not dedicate many hours per week to the project, they always had the
 flexibility to negotiate their work schedule during the semester in
 order to not harm their classes and coursework. Their daily work routine
-in the project included programming and devops tasks.
+in the project included programming and DevOps tasks.
 The development of SPB project required a vast experience and background that
 usually undergraduate students do not have yet. For this reason, a few senior
-developers have joined to the project to help with the more difficult issues and to transfer
-knowledge to the students. Their main task was to provide solutions for complex
-problems, in other words, they worked as developers. As these professionals
-are very skillful and the project could not fund a full time work for them,
-some of them worked partially on the project. In addition, they lived in a
-different states spread around Brazil which led much of the communication to be
-online.
+developers have joined to the project to help with the more difficult issues
+and to transfer knowledge to the students. Their main task was to provide
+solutions for complex problems, in other words, they worked as developers. As
+these professionals are very skillful and the project could not fund a full
+time work for them, some of them worked partially on the project. In addition,
+they lived in a different states spread around Brazil which led much of the
+communication to be online.
 In short, our work process was based on open and collaborative software
 development practices. The development process was defined based on the
@@ -93,20 +93,21 @@ 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
-handouts with tmate, IRC, and mailing lists. When one student had to
+handouts with tmate tool, IRC, and mailing lists. When one student had to
 work in pair with a senior, normally, they used Google hangout for
 communication and they shared a terminal session with tmate which allow
 them to share the same terminal, with both typing and seeing the screen.
 For questions and fast discussion, we used IRC. For general
 notification, we used the mailing lists.
-For managing the project we used the SPB Portal itself; first to
-validate it by ourselves, and also because it had all the required
-tools. We basically created one wiki page per release Gitlab, one
-milestone per sprint, and one or more issues for addressing each
-feature. With this approach we achieved two important goals: keeping all
-the management as close possible to to the source codem, and tracking
-every feature developed during the project.
+For managing the project we used the SPB Portal itself; first to validate it by
+ourselves, and also because it had all the required tools. We basically created
+one wiki page per release in the SPB Gitlab instance with a mapping among
+strategical, tactical, and operational views. In a practical point of view, one
+milestone per user history (feature), and one or more issues for addressing
+each feature. With this approach we achieved two important goals: keeping all
+the management as close possible to to the source code, and tracking every
+feature developed during the project.
 \subsection{High-level project management and reporting}