bibliography.bib
3.63 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
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
@article{anthopoulos2016government,
title={Why e-government projects fail? An analysis of the Healthcare. gov website},
author={Anthopoulos, Leonidas and Reddick, Christopher G and Giannakidou, Irene and Mavridis, Nikolaos},
journal={Government Information Quarterly},
volume={33},
number={1},
pages={161--173},
year={2016},
publisher={Elsevier}
}
@article{goldfinch2007pessimism,
ISSN={00333352, 15406210},
URL={http://www.jstor.org/stable/4624644},
abstract={The majority of information systems developments are unsuccessful. The larger the development, the more likely it will be unsuccessful. Despite the persistence of this problem for decades and the expenditure of vast sums of money, computer failure has received surprisingly little attention in the public administration literature. This article outlines the problems of enthusiasm and the problems of control, as well as the overwhelming complexity, that make the failure of large developments almost inevitable. Rather than the positive view found in much of the public administration literature, the author suggests a pessimism when it comes to information systems development. Aims for information technology should be modest ones, and in many cases, the risks, uncertainties, and probability of failure mean that new investments in technology are not justified. The author argues for a public official as a recalcitrant, suspicious, and skeptical adopter of IT.},
author={Shaun Goldfinch},
journal={Public Administration Review},
number={5},
pages={917-929},
publisher={[American Society for Public Administration, Wiley]},
title={Pessimism, Computer Failure, and Information Systems Development in the Public Sector},
volume={67},
year={2007}
}
@article{mcilroy1968software,
title={Software Engineering: Report on a conference sponsored by the NATO Science Committee},
author={McIlroy, MD},
year={1968},
publisher={NATO Scientific Affairs Division}
}
@article{dybaa2008empirical,
title={Empirical studies of agile software development: A systematic review},
author={Dyb{\aa}, Tore and Dings{\o}yr, Torgeir},
journal={Information and software technology},
volume={50},
number={9},
pages={833--859},
year={2008},
publisher={Elsevier}
}
@inproceedings{de2016using,
title={Using scrum in outsourced government projects: An action research},
author={de Sousa, Thatiany Lima and Venson, Elaine and da Costa Figueiredo, Rejane Maria and Kosloski, Ricardo Ajax and Junior, Luiz Carlos Miyadaira Ribeiro},
booktitle={System Sciences (HICSS), 2016 49th Hawaii International Conference on},
pages={5447--5456},
year={2016},
organization={IEEE}
}
@inproceedings{melo2010adoccao,
title={Ado{\c{c}}{\~a}o de m{\'e}todos {\'a}geis em uma Institui{\c{c}}{\~a}o P{\'u}blica de grande porte-um estudo de caso},
author={Melo, Claudia de O and Ferreira, Gisele RM},
booktitle={Workshop Brasileiro de M{\'e}todos {\'A}geis (Agile Brasil 2010). Centro de Eventos da PUCRS (CEPUC), Porto Alegre},
year={2010}
}
@inproceedings{alleman2003making,
title={Making agile development work in a government contracting environment-measuring velocity with earned value},
author={Alleman, Glen B and Henderson, Michael and Seggelke, Ray},
booktitle={Agile Development Conference, 2003. ADC 2003. Proceedings of the},
pages={114--119},
year={2003},
organization={IEEE}
}
@inproceedings{anderson2005stretching,
title={Stretching agile to fit CMMI level 3-the story of creating MSF for CMMI/spl reg/process improvement at Microsoft corporation},
author={Anderson, David J},
booktitle={Agile Conference, 2005. Proceedings},
pages={193--201},
year={2005},
organization={IEEE}
}