The purpose of this study is to provide understanding of project governance practices in agile projects. A systematic review of the previous agile literature is conducted to identify and categorize agile project governance practices, which are synthesized in a six-dimensional framework. The study contributes to the literature by contrasting traditional and agile project governance practices and by identifying new practices emerging in agile projects, while also noting remaining gaps in knowledge. The implications of this study enable managers to identify and apply feasible governance practices that can support better agile project performance.
AholaT.RuuskaI.ArttoK.KujalaJ. (2014). What is project governance and what are its origins?International Journal of Project Management, 32(8), 1321–1332.
2.
AndersenE. S. (2015). Illuminating the role of the project owner. International Journal of Managing Projects in Business, 5(1), 67–85.
3.
AugustineS.PayneB.SencindiverF.WoodcockS. (2005). Agile project management: Steering from the edges. Communications of the ACM, 48(12), 85–89.
4.
BatraD. (2009). Modified agile practices for outsourced software projects. Communications of the ACM, 52(9), 143–148.
Ben-DavidA.GelbardR.MilsteinI. (2012). Supplier ranking by multi-alternative proposal analysis for agile projects. International Journal of Project Management, 30(6), 723–730.
7.
BergerH. (2007). Agile development in a bureaucratic arena—A case study experience. International Journal of Information Management, 27(6), 386–396.
8.
BergerH.Beynon-DaviesP. (2009). The utility of rapid application development in large-scale, complex projects. Information Systems Journal, 19(6), 549–570.
9.
BiesenthalC.WildenR. (2014). Multi-level project governance: Trends and opportunities. International Journal of Project Management, 32(8), 1291–1308.
10.
BjarnasonE.UnterkalmsteinerM.BorgM.EngstromE. (2016). A multi-case study of agile requirements engineering and the use of test cases as requirements. Information and Software Technology, 77, 61–79.
11.
BjarnasonE.WnukK.RegnellB. (2012). Are you biting off more than you can chew? A case study on causes and effects of overscoping in large-scale software engineering. Information and Software Technology, 54(10), 1107–1124.
12.
ChiocchioF. (2015). Defining project teams: A review of conceptual underpinnings. In ChiocchioF.KellowayE. K.HobbsB. (Eds.), The psychology and management of project teams (1st ed., pp. 40–73). New York, NY: Oxford University Press.
13.
ChowT.CaoD.-B. (2008). A survey study of critical success factors in agile software projects. Journal of Systems and Software, 81(6), 961–971.
14.
ConboyK. (2009). Agility from first principles: Reconstructing the concept of agility in information systems development. Information Systems Research, 20(3), 329–354.
15.
ConboyK.MorganL. (2010). Future research in agile systems development: Applying open innovation principles within the agile organisation. In DingsoyrT.DybaT.MoeN. B. (Eds.), Agile software development: Current research and future directions (pp. 223–235). New York, NY: Springer Science & Business Media.
16.
ConboyK.MorganL. (2011). Beyond the customer: Opening the agile systems development process. Information and Software Technology, 53(5), 535–542.
17.
ConfortoE. C.AmaralD. C. (2010). Evaluating an agile method for planning and controlling innovative projects. Project Management Journal, 41(2), 73–80.
18.
ConfortoE. C.AmaralD. C.da SilvaS. L.Di FelippoA.KamikawachiD. S. L. (2016). The agility construct on project management theory. International Journal of Project Management, 34(4), 660–674.
19.
ConfortoE. C.RebentischE.AmaralD. C. (2014a). Project management agility global survey (Massachusetts Institute of Technology, Consortium for Engineering Program Excellence—CEPE). Cambridge, MA: Massachusetts Institute of Technology.
20.
ConfortoE. C.SalumF.AmaralD. C.da SilvaS. L.de AlmeidaL. F. (2014b). Can agile project management be adopted by industries other than software development?Project Management Journal, 45(3), 21–34.
21.
DanevaM.van der VeenE.AmritC.GhaisasS.SikkelK.KumarR.…WieringaR. (2013). Agile requirements prioritization in large-scale outsourced system projects: An empirical study. Journal of Systems and Software, 86(5), 1333–1353.
22.
DavisJ. H.SchoormanF. D.DonaldsonL. (1997). Towards a stewardship theory of management. Academy of Management Review, 22(1), 20–47.
23.
DoveR. (1999). Knowledge management, response ability, and the agile enterprise. Journal of Knowledge Management, 3(1), 18–35.
24.
DruryM.ConboyK.PowerK. (2012). Obstacles to decision making in agile software development teams. Journal of Systems and Software, 85(6), 1239–1254.
25.
Drury-GroganM. L. (2014). Performance on agile teams: Relating iteration objectives and critical decisions to project management success factors. Information and Software Technology, 56(5), 506–515.
26.
DybåT.DingsøyrT. (2008). Empirical studies of agile software development: A systematic review. Information and Software Technology, 50(9), 833–859.
27.
EisenhardtK. M. (1989). Agency theory: An assessment and review. Academy of Management Review, 14(1), 57–74.
28.
GandomaniT. J.NafchiM. Z. (2015). An empirically-developed framework for agile transition and adoption: A grounded theory approach. Journal of Systems and Software, 107, 204–219.
29.
GarlandR. (2009). Project governance: A practical guide to effective project decision making. London, England: Kogan Page Publishers.
30.
GhobadiS.MathiassenL. (2016). Perceived barriers to effective knowledge sharing in agile software teams. Information Systems Journal, 26(2), 95–125.
31.
GregorS. (2006). The nature of theory in information systems. MIS Quarterly, 30(3), 611–642.
32.
GuoF.Chang-RichardsY.WilkinsonS.LiT. C. (2014). Effects of project governance structures on the management of risks in major infrastructure projects: A comparative analysis. International Journal of Project Management, 32(5), 815–826.
33.
GustavssonT. K.HallinA. (2014). Rethinking dichotomization: A critical perspective on the use of “hard” and “soft” in project management research. International Journal of Project Management, 32(4), 568–577.
34.
HeikkilaV. T.PaasivaaraM.RautiainenK.LasseniusC.ToivolaT.JarvinenJ. (2015). Operational release planning in large-scale Scrum with multiple stakeholders—A longitudinal case study at F-secure corporation. Information and Software Technology, 57, 116–140.
35.
HeraviA.CoffeyV.TrigunarsyahB. (2015). Evaluating the level of stakeholder involvement during the project planning processes of building projects. International Journal of Project Management, 33(5), 985–997.
HobbsB.PetitY. (2017). Agile methods on large projects in large organizations. Project Management Journal, 48(3), 3–19.
38.
HodaR.MurugesanL. K. (2016). Multi-level agile project management challenges: A self-organizing team perspective. Journal of Systems and Software, 117, 245–257.
39.
HodaR.NobleJ.MarshallS. (2011). The impact of inadequate customer collaboration on self-organizing agile teams. Information and Software Technology, 53(5), 521–534.
40.
JahrM. (2014). A hybrid approach to quantitative software project scheduling within agile frameworks. Project Management Journal, 45(3), 35–45.
41.
JanssenM.van der VoortH. (2016). Adaptive governance: Towards a stable, accountable and responsive government. Government Information Quarterly, 33(1), 1–5.
42.
JorgensenM. (2016). A survey on the characteristics of projects with success in delivering client benefits. Information and Software Technology, 78, 83–94.
43.
JoslinR.MüllerR. (2016). The impact of project methodologies on project success in different project environments. International Journal of Managing Projects in Business, 9(2), 364–388.
44.
KaiserM. G.El ArbiF.AhlemannF. (2015). Successful project portfolio management beyond project selection techniques: Understanding the role of structural alignment. International Journal of Project Management, 33(1), 126–139.
45.
KockA.HeisingW.GemündenH. G. (2016). A contingency approach on the impact of front-end success on project portfolio success. Project Management Journal, 47(2), 115–129.
46.
KujalaJ.AaltonenK.GotchevaN.PekuriA. (2016, June1–4). Key dimensions of project network governance and implications for safety in nuclear industry projects. A research paper presented at the EURAM 2016 annual conference, Paris, France.
47.
LahdenperäP. (2012). Making sense of the multi-party contractual arrangements of project partnering, project alliancing and integrated project delivery. Construction Management and Economics, 30(1), 57–79.
48.
MarupingL. M.VenkateshV.AgarwalR. (2009a). A control theory perspective on agile methodology use and changing user requirements. Information Systems Research, 20(3), 377–399.
49.
MarupingL. M.ZhangX.VenkateshV. (2009b). Role of collective ownership and coding standards in coordinating expertise in software project teams. European Journal of Information Systems, 18(4), 355–371.
50.
McAvoyJ.ButlerT. (2007). The impact of the Abilene Paradox on double-loop learning in an agile team. Information and Software Technology, 49(6), 552–563.
51.
McAvoyJ.ButlerT. (2009). The role of project management in ineffective decision making within agile software development projects. European Journal of Information Systems, 18(4), 372–383.
52.
McGrathS. K.WhittyS. J. (2015). Redefining governance: From confusion to certainty and clarity. International Journal of Managing Projects in Business, 8(4), 755–787.
53.
MirandaE.BourqueP. (2010). Agile monitoring using the line of balance. Journal of Systems and Software, 83(7), 1205–1215.
54.
MisraS. C.KumarV.KumarU. (2009). Identifying some important success factors in adopting agile software development practices. Journal of Systems and Software, 82(11), 1869–1890.
55.
MoeN. B.AurumA.DybaT. (2012). Challenges of shared decision-making: A multiple case study of agile software development. Information and Software Technology, 54(8), 853–865.
56.
MoeN. B.DingsoyrT.DybaT. (2010). A teamwork model for understanding an agile team: A case study of a Scrum project. Information and Software Technology, 52(5), 480–491.
57.
MorrisP. W. G.HoughG. H. (1987). The anatomy of major projects: A study of the reality of project management. Chichester, England: John Wiley & Sons.
MüllerR.LecoeuvreL. (2014). Operationalizing governance categories of projects. International Journal of Project Management, 32(8), 1346–1357.
60.
MüllerR.MartinsuoM. (2015). The impact of relational norms on information technology project success and its moderation through project governance. International Journal of Managing Projects in Business, 8(1), 154–176.
61.
MüllerR.PemselS.ShaoJ. (2014). Organizational enablers for governance and governmentality of projects: A literature review. International Journal of Project Management, 32(8), 1309–1320.
62.
MüllerR.PemselS.ShaoJ. (2015). Organizational enablers for project governance and governmentality in project-based organizations. International Journal of Project Management, 33(4), 839–851.
63.
MüllerR.ZhaiL.WangA.ShaoJ. (2016). A framework for governance of projects: Governmentality, governance structure and projectification. International Journal of Project Management, 34(6), 957–969.
64.
NerurS.MahapatraR.MangalarajG. (2005). Challenges of migrating to agile methodologies. Communications of the ACM, 48(5), 72–78.
65.
NuottilaJ.AaltonenK.KujalaJ. (2016). Challenges of adopting agile methods in a public organization. International Journal of Information Systems and Project Management, 4(3), 65–85.
66.
NurdianiI.BorstlerJ.FrickerS. A. (2016). The impacts of agile and lean practices on project constraints: A tertiary study. Journal of Systems and Software, 119, 162–183.
67.
PerssonJ. S.MathiassenL.AaenI. (2012). Agile distributed software development: Enacting control through media and context. Information Systems Journal, 22(6), 411–433.
68.
PintoJ. K. (2014). Project management, governance, and the normalization of deviance. International Journal of Project Management, 32(3), 376–387.
69.
Project Management Institute. (2013). A guide to the project management body of knowledge (PMBOK® guide) – Fifth edition. Newtown Square, PA: Author.
70.
RameshB.CaoL.BaskervilleR. (2010). Agile requirements engineering practices and challenges: An empirical study. Information Systems Journal, 20(5), 449–480.
71.
RameshB.MohanK.CaoL. (2012). Ambidexterity in agile distributed development: An empirical investigation. Information Systems Research, 23(2), 323–339.
72.
ReveT.LevittR. E. (1984). Organization and governance in construction. International Journal of Project Management, 2(1), 17–25.
73.
RivardS. (2014). The ions of theory construction. MIS Quarterly, 38(2), iii–xiv.
74.
RoweF. (2014). What literature review is not: Diversity, boundaries and recommendations. European Journal of Information Systems, 23(3), 241–255.
75.
SamsetK.VoldenG. H. (2016). Front-end definition of projects: Ten paradoxes and some reflections regarding project management and project governance. International Journal of Project Management, 34(2), 297–313.
76.
SandersonJ. (2012). Risk, uncertainty and governance in megaprojects: A critical discussion of alternative explanations. International Journal of Project Management, 30(4), 432–443.
SerradorP.PintoJ. K. (2015). Does agile work? A quantitative analysis of agile project success. International Journal of Project Management, 33(5), 1040–1051.
80.
SheffieldJ.LemetayerJ. (2013). Factors associated with the software development agility of successful projects. International Journal of Project Management, 31(3), 459–472.
81.
ShrivastavaS. V.RathodU. (2015). Categorization of risk factors for distributed agile projects. Information and Software Technology, 58, 373–387.
82.
StankovicD.NikolicV.DjordjevicM.CaoD.-B. (2013). A survey study of critical success factors in agile software projects in former Yugoslavia IT companies. Journal of Systems and Software, 86(6), 1663–1678.
83.
StettinaC. J.HorzJ. (2015). Agile portfolio management: An empirical perspective on the practice in use. International Journal of Project Management, 33(1), 140–152.
84.
StrodeD. E.HuffS. L.HopeB.LinkS. (2012). Coordination in co-located agile software development projects. Journal of Systems and Software, 85(6), 1222–1238.
85.
TengsheA.NobleS. (2007). Establishing the agile PMO: Managing variability across projects and portfolios. In MaurerF.DaviesR.MelnikG.PolliceG. (Eds.), AGILE 2007, proceedings (pp. 188–193). Washington, DC: IEEE.
86.
TessemB. (2014). Individual empowerment of agile and non-agile software developers in small teams. Information and Software Technology, 56(8), 873–889.
87.
TessemB.MaurerF. (2007). Job satisfaction and motivation in a large agile team. In ConcasG.DamianiE.ScottoM.SucciG. (Eds.), Agile processes in software engineering and extreme programming (pp. 54–61). Heidelberg, Germany: Springer.
88.
TooE. G.WeaverP. (2013). The management of project management: A conceptual framework for project governance. International Journal of Project Management, 32(8), 1382–1394.
89.
Torrecilla-SalinasC. J.SedenoJ.EscalonaM. J.MejiasM. (2015). Estimating, planning and managing agile web development projects under a value-based perspective. Information and Software Technology, 61, 124–144.
90.
TranfieldD.DenyerD.SmartP. (2003). Towards a methodology for developing evidence-informed management knowledge by means of systematic review. British Journal of Management, 14, 207–222.
91.
TrkmanM.MendlingJ.KrisperM. (2016). Using business process models to better understand the dependencies among user stories. Information and Software Technology, 71, 58–76.
92.
TurnerJ. R. (2006). Towards a theory of project management: The nature of the project governance and project management. International Journal of Project Management, 24(2), 93–95.
93.
UngerB. N.GemündenH. G.AubryM. (2012). The three roles of a project portfolio management office: Their impact on portfolio management execution and success. International Journal of Project Management, 30(5), 608–620.
94.
van OosterhoutM.WaartsE.van HillegersbergJ. (2006). Change factors requiring agility and implications for IT. European Journal of Information Systems, 15(2), 132–145.
95.
van ValkenhoefG.TervonenT.de BrockB.PostmusD. (2011). Quantitative release planning in extreme programming. Information and Software Technology, 53(11), 1227–1235.
96.
van WaardenburgG.van VlietH. (2013). When agile meets the enterprise. Information and Software Technology, 55(12), 2154–2171.
97.
VlietlandJ.Van SolingenR.Van VlietH. (2016). Aligning codependent Scrum teams to enable fast business value delivery: A governance framework and set of intervention actions. Journal of Systems and Software, 113, 418–429.
98.
Wale-KoladeA. Y. (2015). Integrating usability work into a large inter-organisational agile development project: Tactics developed by usability designers. Journal of Systems and Software, 100, 54–66.
99.
WebsterJ.WatsonR. T. (2002). Analyzing the past to prepare for the future: Writing a literature review. MIS Quarterly, 26(2), xiii–xxiii.
100.
WinchG. M. (2014). Three domains of project organising. International Journal of Project Management, 32(5), 721–731.
101.
ZwikaelO.SmyrkJ. (2015). Project governance: Balancing control and trust in dealing with risk. International Journal of Project Management, 33(4), 852–862.
