04-case.tex
2.78 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
\section{The Case Study}
\label{sec:case}
The project to evolve the Brazilian Public Software Portal
\cite{meirelles2017spb} was a partnership between government and academia held
between 2014 and 2016. To solve maintenance problems and fill
design-reality gaps in the portal, the Ministry of Planning (MPOG) joined the
University of Brasília (UnB) and the University of São Paulo (USP) to develop a
platform with features and technologies novelties in the government context.
%TODO: - Ainda não se falou de ferramentas integradas. Deve ser apresentado o novo SPB (de forma simples e direta como fizemos no IEEE) para se entender a complexidade do projeto/caso
The academic team carried out development activities in the Advanced Laboratory
of Production, Research and Innovation in Software Engineering (LAPPIS) of UnB. The
project management and development process in this laboratory is usually
executed adopting free software practices and agile approach. For this project, a total of 42 undergraduate students, two MSc
students and two coordinator-professors participated in the development team.
Six IT professionals were also hired as senior developers due their vast
experiences in Front-end/UX or in one of the softwares integrated to the
platform.
The government team was composed of a director, a coordinator, and two IT
analysts from a department of MPOG. Although it was responsible for the
execution of this collaboration project, this department generally does not
execute development of ministry's software. This department is responsible for
contracting and homologating software development services and follows
traditional management approaches, such as the RUP.
These two aforementioned teams
periodically met in person for the purpose of managing the project progress. These meetings initially only took place at the
ministry's headquarters to discuss strategic/political and technical goals.
These meetings were held monthly with the presence of two UnB professors, the
executive-secretary of the Presidency (project supporter) and all MPOG members
responsible for the project. The management of the development team was
concentrated in the academia side. The workflow was organized in Redmine in
biweekly sprints and 4-month releases, with intermediate deliveries hosted in
university environment. However, with the progress of the project, this format
proved to be inefficient. Conflicts between the internal management processes
and differences in pace and goals of each institution were compromising the
platform development.
In this case study, we focus on analyzing the dynamics between government and
academia for collaborative development. We aim to map the practices adopted in
the project management and development process to harmonize the cultural and
organizational differences of the institutions involved.