Commit 256c999d2a324b5befbe57b2cded351ef8f2e661

Authored by Paulo Meireles
2 parents 20cf0ae0 b981946b

Merge branch 'master' of softwarepublico.gov.br:softwarepublico/articles

Showing 1 changed file with 3 additions and 1 deletions   Show diff stats
opensym2017/content/07-process.tex
... ... @@ -6,10 +6,12 @@ Since the students could not dedicate many hours per week to the project, they a
6 6  
7 7 The development of SPB project required a vast experience and background that usually undergraduate students do not have yet. For this reason, some senior developers have joined to the project to help with hard issues and to transfer knowledge to the students. Their main task was to provide solutions for complex problems, in other words, they worked as a developer. 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 made via Internet.
8 8  
  9 +In short our work process was based on open and collaborative software development practices. The development process was defined based on the adaptation of different agile and FOSS communities practices, highlighting the high degree of automation resulting from DevOps practices. Thus, the work process was executed in a cadenced and continuous way.
  10 +
9 11 Finally, the last group of actors of this project was composed of employees
10 12 formally working for the Brazilian Government, in the Ministery of Planning,
11 13 development and Management (MPOG is the Brazilian acronyms). All the project
12   -decisions, validations, and scope definitions were made by them. As can be
  14 +decisions, validations, and scope definitions were made by them. In this way we developed software product increments, releases, aligned with business strategic objectives. As can be
13 15 seen, the project had many kinds of profiles that had to be organized and
14 16 synchronized.
15 17  
... ...