Agile Method Tailoring in Distributed Enterprises: Product Owner Teams

This paper explores practitioner descriptions of agile method tailoring in large-scale offshore or outsourced enterprise projects. Specifically, tailoring of the product owner role is discussed. The product owner identifies and prioritizes customer requirements. But in globalized projects, the product owner must reconcile large numbers competing business interests and generate prioritized requirements for many development teams. The study comprises 8 international companies in London, Bangalore and Delhi. Interviews with 46 practitioners were conducted between February 2010 and May 2012. A grounded theory approach was used to identify that product owner teams comprise nine roles: Groom, Prioritizer, Release Master, Technical Architect, Governor, Communicator, Traveler, Intermediary and Risk Assessor. These product owner roles arbitrate between conflicting customer requirements, approve release schedules, make architectural design decisions, provide technical governance and disseminate information across teams. Understanding these roles will help agile coaches guide large scale agile teams.

[1]  Oisín Cawley,et al.  "Leagile" software development: An experience report analysis of the application of lean approaches in agile software development , 2012, J. Syst. Softw..

[2]  Venugopal Balijepally,et al.  Are Two Heads Better than One for Software Development? The Productivity Paradox of Pair Programming , 2009, MIS Q..

[3]  Jeff Sutherland,et al.  Distributed Scrum: Agile Project Management with Outsourced Development Teams , 2007, 2007 40th Annual Hawaii International Conference on System Sciences (HICSS'07).

[4]  Ron J. Patton,et al.  Methods for fault diagnosis in rail vehicle traction and braking systems , 1995 .

[5]  Dag I. K. Sjøberg,et al.  Effects of Personality on Pair Programming , 2010, IEEE Transactions on Software Engineering.

[6]  JaatunMartin Gilje,et al.  Agile Software Development , 2002, Comput. Sci. Educ..

[7]  A. Strauss,et al.  The discovery of grounded theory: strategies for qualitative research aldine de gruyter , 1968 .

[8]  Mike Cohn,et al.  Succeeding with Agile: Software Development Using Scrum , 2009 .

[9]  K. Beck,et al.  Extreme Programming Explained , 2002 .

[10]  James Noble,et al.  Developing a grounded theory to explain the practices of self-organizing Agile teams , 2012, Empirical Software Engineering.

[11]  Juliet M. Corbin,et al.  Basics of Qualitative Research (3rd ed.): Techniques and Procedures for Developing Grounded Theory , 2008 .

[12]  Scott W. Ambler,et al.  Disciplined Agile Delivery: A Practitioner's Guide to Agile Software Delivery in the Enterprise , 2012 .

[13]  B MilesMatthew,et al.  Qualitative Data Analysis , 2018, Approaches and Processes of Social Science Research.

[14]  Tore Dybå,et al.  What Do We Know about Agile Software Development? , 2009, IEEE Software.

[15]  Craig Larman,et al.  Scaling Lean & Agile Development: Thinking and Organizational Tools for Large-Scale Scrum , 2008 .

[16]  K. Seers Qualitative data analysis , 2011, Evidence Based Nursing.

[17]  James Noble,et al.  The impact of inadequate customer collaboration on self-organizing Agile teams , 2011, Inf. Softw. Technol..

[18]  Keith C. C. Chan,et al.  The Effect of Pairs in Program Design Tasks , 2008, IEEE Transactions on Software Engineering.

[19]  N. Hoffart Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory , 2000 .

[20]  Dean Leffingwell,et al.  Scaling Software Agility: Best Practices for Large Enterprises (The Agile Software Development Series) , 2007 .

[21]  Claes Wohlin,et al.  Agile Practices in Global Software Engineering - A Systematic Map , 2010, 2010 5th IEEE International Conference on Global Software Engineering.

[22]  Hakan Erdogmus,et al.  Scaling Agile Methods , 2003, IEEE Softw..

[23]  Ken Schwaber,et al.  Agile Project Management with Scrum , 1980 .

[24]  J. Stapleton,et al.  DSDM: Dynamic Systems Development Method , 1999, Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275).

[25]  Hye-Young Paik,et al.  Using Scrum in Global Software Development: A Systematic Literature Review , 2009, 2009 Fourth IEEE International Conference on Global Software Engineering.

[26]  Andraž Cej,et al.  Agile software development with Scrum , 2010 .

[27]  Peng Xu,et al.  Can distributed software development be agile? , 2006, CACM.

[28]  Casper Lassenius,et al.  Using scrum in a globally distributed project: a case study , 2008, Softw. Process. Improv. Pract..

[29]  Casper Lassenius,et al.  Does distance still matter , 2008 .

[30]  James Noble,et al.  Organizing self-organizing teams , 2010, 2010 ACM/IEEE 32nd International Conference on Software Engineering.

[31]  M. Patton,et al.  Qualitative evaluation and research methods , 1992 .

[32]  Oisín Cawley,et al.  Lean/Agile Software Development Methodologies in Regulated Environments - State of the Art , 2010, LESS.

[33]  Mark Lycett,et al.  Examining perceptions of agility in software development practice , 2010, Commun. ACM.

[34]  Julian M. Bass,et al.  A Comparison of Software Development Process Experiences , 2004, XP.