Identifying Challenges and a Research Agenda for Flow in Software Project Management

Abstract

Flow and its associated tools and metrics are increasingly being reported as an approach used to achieve continuous deployment of software and delivery of value in software development projects. Yet, the extant literature on flow tools to date is rather limited. Also, what does exist tends to largely focus on the generic version of flow, rather than any rigorous examination of its use in the turbulent and constantly changing ‘real world’ environment within which it is applied. This study draws on a longitudinal case to identify the challenges of implementing flow and to provide a research agenda for flow project management.

Keywords

flow Kanban project management software development

Get full access to this article

View all access options for this article.

References

Ambler

(2014). 2014 agile adoption survey. Retrieved from http://www.ambysoft.com/surveys/agileJanuary2014.html

Anderson

(2010). The Kanban principles. Seattle, WA: Blue Hole Press.

Anderson

(2013). Lean software development. Seattle, WA: Lean Kanban University (LKU).

Anderson

Concas

Lunesu

M. I.

Marchesi

Zhang

(2011, May). Studying lean-kanban approach using software process simulation. In Sillitti

Hazzan

Bache

Albaladejo

(Eds.), International conference on agile software development (pp. 12–26). Berlin: Springer.

Anderson

Roock

(2011). An agile evolution: Why Kanban is catching on in Germany and around the world. Cutter IT Journal, 24(3), 6.

Arditi

Tokdemir

O. B.

Suh

(2001). Effect of learning on line-of-balance scheduling. International Journal of Project Management, 19(5), 265–277.

Arditi

Tokdemir

O. B.

Suh

(2002). Challenges in line-of-balance scheduling. Journal of Construction Engineering and Management, 128(6), 545–556.

Bang

S. K.

Chung

Choh

Dupius

(2013, October 10–12). A grounded theory analysis of modern web applications: Knowledge, skills, and abilities for DevOps. Proceedings of the 2nd annual Conference on Research in Information Technology, Orlando, FL. Retrieved from https://dl.acm.org/citation.cfm?doid=2512209.2512229

Benbasat

Goldstein

D. K.

Mead

(1987). The case research strategy in studies of information systems. MIS Quarterly, 11(3), 369–386.

10.

Birkeland

J. O.

(2010). From a timebox tangle to a more flexible flow. In Sillitti

Martin

Wang

Whitworth

(Eds.), International conference on agile software development (pp. 325–334). Berlin: Springer.

11.

Cawley

Wang

Richardson

(2013). Lean software development–what exactly are we talking about? Lean Enterprise Software and Systems, 167, 16–31.

12.

Choudhury

Sabherwal

(2003). Portfolios of control in outsourced software development projects. Information Systems Research, 14(3), 291–314.

13.

Chua

Lim

W.-K.

Soh

Sia

S. K.

(2012). Enacting clan control in complex IT projects: A social capital perspective. MIS Quarterly, 36(2), 577–600.

14.

Cocco

Mannaro

Concas

Marchesi

(2011). Simulating Kanban and Scrum vs. Waterfall with system dynamics. In Sillitti

Hazzan

Bache

Albaladejo

(Eds.), International conference on agile software development (pp. 117–131). Berlin: Springer.

15.

Conboy

(2009). Agility from first principles: Reconstructing the concept of agility in information systems development. Information Systems Research, 20(3), 329–354.

16.

Conboy

(2010). Project failure en masse: A study of loose budgetary control in ISD projects. European Journal of Information Systems, 19, 273–287.

17.

Concas

Lunesu

M. I.

Marchesi

Zhang

(2013). Simulation of software maintenance process, with and without a work-in-process limit. Journal of Software: Evolution and Process, 25(12), 1225–1248.

18.

Csikszentmihalyi

(1975). Beyond boredom and anxiety (Vol. 721). San Francisco, CA: Jossey-Bass.

19.

Csikszentmihalyi

Kleiber

D. A.

(1991). Leisure and self-actualization. In Driver

O. L.

Brown

P. J.

Peterson

G. L.

(Eds.), Benefits of leisure (pp. 99–102). State College, PA: Venture Publishing.

20.

Dennehy

Conboy

(2017). Going with the flow: An activity theory analysis of flow techniques in software development. Journal of Systems and Software, 133(2017), 160–173.

21.

Denzin

N. K.

Lincoln

Y. S.

(Eds.). (2011). The Sage handbook of qualitative research. London, England: Sage Publications.

22.

Drummond

(2011). MIS and illusions of control: An analysis of the risks of risk management. Journal of Information Technology, 26(4), 259–267.

23.

Dybå

Dingsøyr

(2008). Empirical studies of agile software development: A systematic review. Information and Software Technology, 50(9–10), 833–859.

24.

Ebert

Abrahamsson

Oza

(2012). Lean software development. IEEE Software, 29(5), 22–25.

25.

Eisenhardt

K. M.

(1989). Building theories from case study research. The Academy of Management Review, 14(4), 532–550.

26.

Fichman

R. G.

Kemerer

C. F.

(1997). The assimilation of software process innovations: An organizational learning perspective. Management Science, 43(10), 1345–1363.

27.

Fitzgerald

Russo

N. L.

Stolterman

(2002). Information systems development: Methods in action. New York, NY: McGraw-Hill.

28.

Fitzgerald

Stol

K.-J.

(2015). Continuous software engineering: A roadmap and agenda. Journal of Systems and Software, 123(2017), 176–189.

29.

Gallivan

M. J.

(2001). Organizational adoption and assimilation of complex technological innovations: Development and application of a new framework. ACM SIGMIS Database, 32(3), 51–85.

30.

Glaser

B. G.

Strauss

(1967). The discovery of ground theory. New York, NY: Aldine de Grutyer.

31.

Harris

M. L.

Collins

R. W.

Hevner

A. R.

(2009). Control of flexible software development under uncertainty. Information Systems Research, 20(3), 400–419.

32.

Hinchey

Fitzgerald

Donnellan

Margaria

(2016). Innovation potential of software technologies in the context of Horizon 2020. Retrieved from http://www.lero.ie/sites/default/files/DGConnect.pdf

33.

Ikonen

(2010). Leadership in Kanban software development projects: A quasi-controlled experiment. In Abrahamsson

Oza

(Eds.), Lean enterprise software and systems (pp. 85–98). Berlin: Springer.

34.

Ikonen

Kettunen

Oza

Abrahamsson

(2010). Exploring the sources of waste in Kanban software development projects. In 36th EUROMICRO conference on Software Engineering and Advanced Applications (SEAA 2010) (pp. 376–381). Los Alamitos, CA: IEEE Computer Society.

35.

Ikonen

Pirinen

Fagerholm

Kettunen

Abrahamsson

(2011). On the impact of Kanban on software project work: An empirical case study investigation (pp. 305–314). In IEEE International Conference on Engineering of Complex Computer Systems (ICECCS), Las Vegas, Nevada. doi:10.1109/ICECCS.2011.37

36.

Khurum

Petersen

Gorschek

(2014). Extending value stream mapping through waste definition beyond customer perspective. Journal of Software: Evolution and Process, 26(12), 1074–1105.

37.

Kirsch

L. J.

Sambamurthy

D. G.

Purvis

R. L.

(2002). Controlling information systems development projects: The view from the client. Management Science, 48(4), 484–498.

38.

Kirsch

L. J.

(1997). Portfolios of control modes and IS project management. Information Systems Research, 8(3), 215–239.

39.

Kitchenham

Pretorius

Budgen

Brereton

O. P.

Turner

Niazi

Linkman

(2010). Systematic literature reviews in software engineering—A tertiary study. Information and Software Technology, 52(8), 792–805.

40.

Kitchenham

B. A.

Pfleeger

S. L.

Pickard

L. M.

Jones

P. W.

Hoaglin

D. C.

El Emam

Rosenberg

(2002). Preliminary guidelines for empirical research in software engineering. IEEE Transactions on Software Engineering, 28(8), 721–734.

41.

Klipp

(2011). Getting started with Kanban. Kanbanery. Retrieved from https://morebetterlabs.kanbanery.com/ebook/GettingStartedWithKanban.pdf

42.

Kniberg

Skarin

(2010). Kanban and Scrum-making the most of both. Retrieved from https://www.infoq.com/minibooks/kanban-scrum-minibook

43.

Law

E. L. C.

Lárusdóttir

M. K.

(2015). Whose experience do we care about? Analysis of the fitness of scrum and Kanban to user experience. International Journal of Human-Computer Interaction, 31(9), 584–602.

44.

Leopold

Kaltenecker

(2015). Kanban change leadership. Hoboken, NJ: John Wiley & Sons. Retrieved from https://www-wiley-com-s.web.bisu.edu.cn/en-us/Kanban+Change+Leadership%3A+Creating+a+Culture+of+Continuous+Improvement-p-9781119019701

45.

Lyytinen

Rose

G. M.

(2006). Information system development agility as organizational learning. European Journal of Information Systems, 15(2), 183–199.

46.

Maxwell

(1992). Understanding and validity in qualitative research. Harvard Educational Review, 62(3), 279–301.

47.

Mahnic

(2015). From Scrum to Kanban: Introducing lean principles to a software engineering capstone course. International Journal of Engineering Education, 31(4), 1106–1116.

48.

Middleton

Joyce

(2012). Lean software management: BBC worldwide case study. IEEE Transactions on Engineering Management, 5 9(1), 20–32. doi:10.1109/TEM.2010.2081675; Retrieved from https://pure.qub.ac.uk/ws/files/724967/Lean%20Software%20Management%20BBC%20Worldwide%20Case%20Study%20Feb%202011.pdf

49.

Miles

M. B.

Huberman

A. M.

(1984). Qualitative data analysis. Beverly Hills, CA: Sage Publications.

50.

Mujtaba

Feldt

Petersen

(2010). Waste and lead time reduction in a software product customization process with value stream maps. 21st Australian Software Engineering Conference (ASWEC), IEEE Computer Society. Retrieved from http://www.diva-portal.org/smash/record.jsf?pid=diva2%3A835552&dswid=-2813

51.

Naylor

J. B.

Naim

M. M.

Berry

(1999). Leagility: Integrating the lean and agile manufacturing paradigms in the total supply chain. International Journal of Production Economics, 62(1–2), 107–118.

52.

Nikitina

Kajko-Mattsson

(2011). Developer-driven big-bang process transition from Scrum to Kanban (pp. 159–168). Waikiki, Honolulu, HI: Proceedings of the 2011 International Conference on Software and Systems Process.

53.

Nord

R. L.

Ozkaya

Sangwan

R. S.

(2012). Making architecture visible to improve flow management in lean software development. IEEE Software, 29(5), 33–39.

54.

Ohno

(1988). Toyota production system: Beyond large-scale production. Boca Raton, FL: CRC Press.

55.

Olerup

(1991). Design approaches: A comparative study of information system design and architectural design. The Computer Journal, 34(3), 215–224.

56.

Oppenheim

(1992). Questionnaire design, interviewing and attitude measurement. Pinter, London, 4(5), 371–382.

57.

Orlikowski

W. J.

(1993). CASE tools as organizational change: Investigating incremental and radical changes in systems development. MIS Quarterly, 17(3), 309–340.

58.

Petersen

(2011). Is lean agile and agile lean? A comparison between two software development paradigms. Modern Software Engineering Concepts and Practices: Advanced Approaches, 1, 19–46. doi:10.4018/978-1-60960-215-4.ch002

59.

Petersen

Roos

Nyström

Runeson

(2014). Early identification of bottlenecks in very large scale system of systems software development. Journal of Software: Evolution and Process, 26(12), 1150–1171.

60.

Petersen

Wohlin

(2009). Context in industrial software engineering research (pp. 401–404). Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement, IEEE Computer Society, Washington, DC.

61.

Petersen

Wohlin

(2011). Measuring the flow in lean software development. Software: Practice and Experience, 41(9), 975–996.

62.

Ply

J. K.

Moore

J. E.

Williams

C. K.

Thatcher

J. B.

(2012). Is employee attitudes and perceptions at varying levels of software process maturity. MIS Quarterly, 36(2), 601–624.

63.

Polk

(2011). Agile and Kanban in coordination (pp. 263–268). Proceedings of the Agile Conference, Salt Lake City, UT. doi:10.1109/AGILE.2011.10

64.

Poppendieck

(2011). Principles of lean thinking. IT Management Select, 18(1), 1–7. Retrieved from http://www.sel.unsl.edu.ar/ApuntesMaes/Anteriores/MetodologiasAgiles/LeanThinking.pdf

65.

Poppendieck

Cusumano

M. A.

(2012). Lean software development: A tutorial. IEEE Software, 29(5), 26–32.

66.

Poppendieck

(2013). The lean mindset: Ask the right questions. London, England: Pearson Education.

67.

Power

(2014). Definition of ready: An experience report from teams at Cisco. In Cantone

Marchesi

(Eds.), Agile processes in software engineering and extreme programming. XP 2014. Lecture notes in business information processing (Vol. 179, pp. 234–241). Rome, Italy: Springer Science + Business Media. doi:10.1007/978-3-319-06862-6_25

68.

Power

Conboy

(2015). A metric-based approach to managing architecture-related impediments in product development flow: An industry case study from Cisco. In Antonia

Bertolino

(Ed.), Proceedings of the second international workshop on software architecture and metrics (pp. 15–21). Florence, Italy: IEEE Press.

69.

Reinertsen

D. G.

(2009). The principles of product development flow: Second generation lean product development. Redondo Beach, CA: Celeritas.

70.

Remenyi

Williams

(1995). Some aspects of methodology for research in information systems. Journal of Information Technology, 10(3), 191–201.

71.

Robinson

Segal

Sharp

(2007). Ethnographically-informed empirical studies of software practice. Information and Software Technology, 49(6), 540–551.

72.

Rubin

(2005). Qualitative interviewing: The art of hearing data. Thousand Oaks, CA: Sage Publications.

73.

Runeson

Höst

(2009). Guidelines for conducting and reporting case study research in software engineering. Empirical Software Engineering, 14(2), 131–164.

74.

Rutherford

Shannon

Judson

Kidd

(2010). From chaos to Kanban, via scrum (pp. 344–352). In Sillitti

Martin

Wang

Whitworth

(Eds.), International conference on agile software development. Berlin: Springer.

75.

Senapathi

Middleton

Evans

(2011). Factors affecting effectiveness of agile usage–Insights from the BBC worldwide case study (pp. 132–145). In Sillitti

Hazzan

Bache

Albaladejo

(Eds.), International conference on agile software development. Berlin: Springer.

76.

Shinkle

C. M.

(2009). Applying the Dreyfus model of skill acquisition to the adoption of Kanban systems at Software Engineering Professionals (SEP) (pp. 186–191). Agile Conference, AGILE’09, Chicago, IL. doi:10.1109/AGILE.2009.25

77.

Sjøberg

D. I.

Johnsen

Solberg

(2012). Quantifying the effect of using Kanban versus scrum: A case study. IEEE Software, 29(5), 47–53.

78.

Stake

(2000). Case studies in handbook of qualitative research. Thousand Oaks, CA: Sage Publications.

79.

Standish Group. (2015). Standish CHAOS report. Retrieved from https://www.projectsmart.co.uk/white-papers/chaos-report.pdf. Accessed September 6 2018.

80.

Stray

V. G.

Moe

N. B.

Dingsøyr

(2011). Challenges to teamwork: A multiple case study of two agile teams. In: Sillitti

Hazzan

Bache

Albaladejo

(Eds.), International conference on agile software development (pp. 146–161). Berlin: Springer.

81.

Towill

Christopher

(2002). The supply chain strategy conundrum: To be lean or agile or to be lean and agile? International Journal of Logistics, 5(3), 299–309.

82.

VersionOne. (2016). What is Kanban? Retrieved from https://www.versionone.com/what-is-kanban/

83.

Wastell

Newman

(1993). The behavioral dynamics of information system development: A stress perspective. Accounting, Management and Information Technologies, 3(2), 121–148.

84.

Wengraf

(2001). Qualitative research interviewing: Biographic narrative and semi-structured methods. Thousand Oaks, CA: Sage Publications.

85.

Wiener

Remus

Heumann

Mähring

(2015). The effective promotion of informal control in information systems offshoring projects. European Journal of Information Systems, 24(6), 569–587.

86.

Womack

J. P.

Jones

D. T.

(2010). Lean thinking: Banish waste and create wealth in your corporation. New York, NY: Simon & Schuster.

87.

Womack

J. P.

Jones

D. T.

Roos

(1990). How lean production can change the world. New York Times Magazine, 13(23), 20–38.

88.

Yin

R. K.

(2009). Case study research: Design and methods (applied social research methods). London, England and Singapore: Sage Publications.