Nothing Special   »   [go: up one dir, main page]

skip to main content
10.1109/ICSE.2019.00036acmconferencesArticle/Chapter ViewAbstractPublication PagesicseConference Proceedingsconference-collections
research-article

The product backlog

Published: 25 May 2019 Publication History

Abstract

Context: One of the most common artifacts in contemporary software projects is a product backlog comprising user stories, bugs, chores or other work items. However, little research has investigated how the backlog is generated or the precise role it plays in a project.
Objective: The purpose of this paper is to determine what is a product backlog, what is its role, and how does it emerge?
Method: Following Constructivist Grounded Theory, we conducted a two-year, five-month participant-observation study of eight software development projects at Pivotal, a large, international software company. We interviewed 56 software engineers, product designers, and product managers. We conducted a survey of 27 product designers. We alternated between analysis and theoretical sampling until achieving theoretical saturation.
Results: We observed 13 practices and 6 obstacles related to product backlog generation.
Limitations: Grounded Theory does not support statistical generalization. While the proposed theory of product backlogs appears widely applicable, organizations with different software development cultures may use different practices.
Conclusion: The product backlog is simultaneously a model of work to be done and a boundary object that helps bridge the gap between the processes of generating user stories and realizing them in working code. It emerges from sensemaking (the team making sense of the project context) and coevolution (a cognitive process where the team simultaneously refines its understanding of the problematic context and fledgling solution concepts).

References

[1]
P. Checkland, Systems Thinking, Systems Practice. Chichester, UK: Wiley, 1999.
[2]
S. Lichtenstein and P. Slovic, The Construction of Preference. Cambridge, UK: Cambridge University Press, Aug. 2006.
[3]
N. Maiden, S. Jones, K. Karlsen, R. Neill, K. Zachos, and A. Milne, "Requirements engineering as creative problem solving: a research agenda for idea finding," in Proceedings of the 18th IEEE International Requirements Engineering Conference. IEEE, 2010, pp. 57--66.
[4]
D. H. Jonassen, "Instructional design models for well-structured and III-structured problem-solving learning outcomes," Educational Technology Research and Development, vol. 45, no. 1, pp. 65--94, 1997.
[5]
K. Charmaz, Constructing Grounded Theory. SAGE Publications, 2014.
[6]
T. Sedano, P. Ralph, and C. Péraire, "Sustainable software development through overlapping pair rotation," in Proceedings of the International Symposium on Empirical Software Engineering and Measurement International Conference on Software Engineering, ser. ESEM, 2016.
[7]
T. Sedano, "Practice and perception of team code ownership," in Proceedings of the 20th International Conference on Evaluation and Assessment in Software Engineering, ser. EASE. ACM, 2016.
[8]
T. Sedano, "Software development waste," in Proceedings of the 2017 International Conference on Software Engineering, ser. ICSE '17. IEEE, 2017.
[9]
K. Beck and C. Andres, Extreme Programming Explained: Embrace Change (2nd Edition). Addison-Wesley Professional, 2004.
[10]
T. Sedano, "Sustainable software development: Evolving extreme programming," Ph.D. dissertation, Carnegie Mellon University, 2017.
[11]
B. Glaser, Theoretical Sensitivity: Advances in the Methodology of Grounded Theory. Sociology Press, 1978.
[12]
B. Glaser, Doing Grounded Theory: Issues and Discussions. Sociology Press, 1998.
[13]
T. Sedano, P. Ralph, and C. Péraire, "Lessons learned from an extended participant observation grounded theory study," in Proceedings of the 5th International Workshop on Conducting Empirical Studies in Industry, ser. CESI '17. IEEE, 2017.
[14]
J. Thomson. Trust and balanced teams. {Online}. Available: https://medium.com/product-labs/trust-and-balanced-teams-919456ad57cf
[15]
B. Fitzgerald and K.-J. Stol, "Continuous software engineering: A roadmap and agenda," Journal of Systems and Software, vol. 123, no. C, pp. 176--189, Jan. 2017.
[16]
S. Madsen and L. Nielsen, "Exploring Persona-Scenarios - Using Storytelling to Create Design Ideas," in Human Work Interaction Design: Usability in Social, Cultural and Organizational Contexts. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010, pp. 57--66.
[17]
M. Farleo. Personas vs proto-personas. {Online}. Available: https://newmediadenver.com/personas-vs-proto-personas
[18]
M. Seaman. The right number of user interviews. {Online}. Available: https://medium.com/@mitchelseaman/the-right-number-of-user-interviews-de11c7815d9
[19]
J. Kawakita, Hassouhou-Souzousei kaihatsu no tame ni - A way of thinking that developes creativity. Chuokoron-Shinsha, 1967.
[20]
A. Alliance. (2017) Role-feature-reason. {Online}. Available: https://www.agilealliance.org/glossary/role-feature/
[21]
M. Wynne and A. Hellesoy, The Cucumber Book: Behaviour-Driven Development for Testers and Developers. Pragmatic Bookshelf, 2012.
[22]
N. Cross, "Design cognition: results from protocol and other empirical studies of design activity," in Design knowing and learning: Cognition in design education, C. Eastman, W. Newstetter, and M. McCracken, Eds. Oxford, UK: Elsevier Science, 2001, pp. 79--103.
[23]
N. Cross, K. Dorst, and N. Roozenburg, Research in Design Thinking. Delft University Press, 1992.
[24]
P. Ralph and Y. Wand, "A Proposal for a Formal Definition of the Design Concept," in Design Requirements Engineering: A Ten-Year Perspective, K. Lyytinen, P. Loucopoulos, J. Mylopoulos, and W. Robinson, Eds. Cleveland, OH, USA: Springer-Verlag, Jun. 2009, pp. 103--136.
[25]
D. A. Schön, The reflective practitioner: how professionals think in action. USA: Basic Books, 1983.
[26]
P. Ralph and R. Mohanani, "Is requirements engineering inherently counterproductive?" in Proceedings of the 5th International Workshop on the Twin Peaks of Requirements and Architecture, Florence, Italy, May 2015, pp. 20--23.
[27]
P. J. Silvia, B. P. Winterstein, J. T. Willse, C. M. Barona, J. T. Cram, K. I. Hess, J. L. Martinez, and C. A. Richard, "Assessing creativity with divergent thinking tasks: Exploring the reliability and validity of new subjective scoring methods." Psychology of Aesthetics, Creativity, and the Arts, vol. 2, no. 2, p. 68, 2008.
[28]
S. L. Star and J. R. Griesemer, "Institutional Ecology, 'Translations' and Boundary Objects: Amateurs and Professionals in Berkeley's Museum of Vertebrate Zoology, 1907--39," Social Studies of Science, vol. 19, no. 3, pp. 387--420, 1989.
[29]
B. A. Bechky, "Sharing meaning across occupational communities: The transformation of understanding on a production floor," Organization Science, vol. 14, no. 3, pp. 312--330, 2003. {Online}. Available
[30]
S. L. Star, "This is Not a Boundary Object: Reflections on the Origin of a Concept," Science, Technology, & Human Values, vol. 35, no. 5, pp. 601--617, 2010.
[31]
K. E. Weick, K. M. Sutcliffe, and D. Obstfeld, "Organizing and the Process of Sensemaking," Organization Science, vol. 16, no. 4, pp. 409--421, 2005.
[32]
P. Ralph, "The Sensemaking-coevolution-implementation theory of software design," Science of Computer Programming, vol. 101, pp. 21--41, 2015.
[33]
H. Aldrich and D. Herker, "Boundary spanning roles and organization structure," Academy of management review, vol. 2, no. 2, pp. 217--230, 1977.
[34]
M. L. Tushman and T. J. Scanlan, "Boundary spanning individuals: Their role in information transfer and their antecedents," Academy of management journal, vol. 24, no. 2, pp. 289--305, 1981.
[35]
J. W. Creswell and D. L. Miller, "Determining validity in qualitative inquiry," Theory Into Practice, vol. 39, no. 3, 2000.
[36]
J. Kolko, "Abductive thinking and sensemaking: The drivers of design synthesis," Design Issues, vol. 26, no. 1, pp. 15--28, 2010.
[37]
P. Ralph, "Software engineering process theory: A multi-method comparison of Sensemaking-Coevolution-Implementation Theory and Function-Behavior-Structure Theory," Information and Software Technology, vol. 70, pp. 232--250, 2016.
[38]
N. Levina, "Collaborating on Multiparty Information Systems Development Projects: A Collective Reflection-in-Action View," Information Systems Research, vol. 16, no. 2, pp. 109--130, 2005.
[39]
K. Schwaber, "SCRUM Development Process," in Business Object Design and Implementation: OOPSLA Workshop Proceedings October, Austin, Texas, J. Sutherland, D. Patel, C. Casanave, J. Miller, and G. Hollowell, Eds., London, UK, 1997.
[40]
K. Schwaber and J. Sutherland. (2015) Scrum guide. {Online}. Available: http://www.scrumguides.org/
[41]
S. Ambler. (2010) Agile best practice: Prioritized requirements. {Online}. Available: http://agilemodeling.com/essays/prioritizedRequirements.htm
[42]
A. Silva, A. Silva, T. Araújo, R. Willamy, F. Ramos, A. Costa, M. Perkusich, and E. Dilorenzo, "Ordering the product backlog in agile software development projects: A systematic literature review," in Proceedings of the 29th International Conference on Software Engineering & Knowledge Engineering, SEKE 2017, Pittsburg, USA, 07 2017.
[43]
Z. Racheva, M. Daneva, A. Herrmann, and R. J. Wieringa, "A conceptual model and process for client-driven agile requirements prioritization," in Research Challenges in Information Science (RCIS), 2010 Fourth International Conference on. IEEE, 2010, pp. 287--298.
[44]
P. Ralph, "Toward Methodological Guidelines for Process Theories and Taxonomies in Software Engineering," IEEE Transactions on Software Engineering, 2018.
[45]
N. Bolloju, S. Alter, A. Gupta, S. Gupta, and S. Jain, "Improving scrum user stories and product backlog using work system snapshots," in Proceedings of the Americas Conference on Information Systems. Boston, USA: AIS, 2017.
[46]
K. Schwaber and M. Beedle, Agile Software Development with Scrum. Prentice Hall, 2001.
[47]
K. Schwaber, Agile Project Management with Scrum. Microsoft Press, 2004.
[48]
D. M. Russell, M. J. Stefik, P. Pirolli, and S. K. Card, "The cost structure of sensemaking," in Proceedings of the INTERACT '93 and CHI '93 Conference on Human Factors in Computing Systems, ser. CHI '93. New York, NY, USA: ACM, 1993, pp. 269--276. {Online}. Available
[49]
B. Martin and B. Hanington, Universal Methods of Design: 100 Ways to Research Complex Problems, Develop Innovative Ideas, and Design Effective Solutions. Rockport Publishers, 2012.
[50]
A. Seffah and E. Metzker, "The obstacles and myths of usability and software engineering," Commun. ACM, vol. 47, no. 12, pp. 71--76, Dec. 2004. {Online}. Available
[51]
M. Brhel, H. Meth, A. Maedche, and K. Werder, "Exploring principles of user-centered agile software development: A literature review, systematic review paper," Information and Software Technology, vol. 61, no. C, pp. 163--181, May 2015. {Online}. Available
[52]
D. Salah, R. F. Paige, and P. Cairns, "A systematic literature review for agile development processes and user centred design integration," in Proceedings of the 18th International Conference on Evaluation and Assessment in Software Engineering, ser. EASE '14. New York, NY, USA: ACM, 2014, pp. 5:1--5:10. {Online}. Available
[53]
C. Salvador, A. Nakasone, and J. A. Pow-Sang, "A systematic review of usability techniques in agile methodologies," in Proceedings of the 7th Euro American Conference on Telematics and Information Systems, ser. EATIS '14. New York, NY, USA: ACM, 2014, pp. 17:1--17:6. {Online}. Available
[54]
A. Garcia, T. Da Silva, and M. Silveira, "Artifacts for agile user-centered design: A systematic mapping," in Hawaii International Conference on System Sciences, 01 2017.
[55]
L. Miller, "Case study of customer input for a successful product," in Proceedings of Agile 2005. IEEE, 2005, pp. 225--234.
[56]
D. Sy, "Adapting usability investigations for agile user-centered design," J. Usability Studies, vol. 2, no. 3, pp. 112--132, May 2007. {Online}. Available: http://dl.acm.org/citation.cfm?id=2835547.2835549
[57]
K. Albrecht. (2015) Dual track agile: Focusing on customer value. {Online}. Available: https://medium.com/kevin-on-code/dual-track-agile-focusing-on-customer-value-a2e39312585b
[58]
J. De Litchenberg. (2017) Dual-track agile: Why messy leads to innovation. {Online}. Available: https://www.mindtheproduct.com/2017/04/dual-track-agile-messy-leads-innovation/

Cited By

View all
  • (2024)Software Development Waste amidst COVID-19 Pandemic: An Industry StudyProceedings of the 17th Innovations in Software Engineering Conference10.1145/3641399.3641417(1-5)Online publication date: 22-Feb-2024
  • (2024)Automated Derivation of UML Sequence Diagrams from User Stories: Unleashing the Power of Generative AI vs. a Rule-Based ApproachProceedings of the ACM/IEEE 27th International Conference on Model Driven Engineering Languages and Systems10.1145/3640310.3674081(138-148)Online publication date: 22-Sep-2024
  • (2024)"Do You Want Me to Participate or Not?": Investigating the Accessibility of Software Development Meetings for Blind and Low Vision ProfessionalsProceedings of the 2024 CHI Conference on Human Factors in Computing Systems10.1145/3613904.3642130(1-17)Online publication date: 11-May-2024
  • Show More Cited By

Recommendations

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image ACM Conferences
ICSE '19: Proceedings of the 41st International Conference on Software Engineering
May 2019
1318 pages

Sponsors

Publisher

IEEE Press

Publication History

Published: 25 May 2019

Check for updates

Badges

Author Tags

  1. design thinking
  2. dual-track agile
  3. extreme programming
  4. feature engineering
  5. lean
  6. product backlog
  7. scrum
  8. user stories
  9. user-centered design

Qualifiers

  • Research-article

Conference

ICSE '19
Sponsor:

Acceptance Rates

Overall Acceptance Rate 276 of 1,856 submissions, 15%

Upcoming Conference

ICSE 2025

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)23
  • Downloads (Last 6 weeks)2
Reflects downloads up to 28 Nov 2024

Other Metrics

Citations

Cited By

View all
  • (2024)Software Development Waste amidst COVID-19 Pandemic: An Industry StudyProceedings of the 17th Innovations in Software Engineering Conference10.1145/3641399.3641417(1-5)Online publication date: 22-Feb-2024
  • (2024)Automated Derivation of UML Sequence Diagrams from User Stories: Unleashing the Power of Generative AI vs. a Rule-Based ApproachProceedings of the ACM/IEEE 27th International Conference on Model Driven Engineering Languages and Systems10.1145/3640310.3674081(138-148)Online publication date: 22-Sep-2024
  • (2024)"Do You Want Me to Participate or Not?": Investigating the Accessibility of Software Development Meetings for Blind and Low Vision ProfessionalsProceedings of the 2024 CHI Conference on Human Factors in Computing Systems10.1145/3613904.3642130(1-17)Online publication date: 11-May-2024
  • (2024)Co-Creation in Fully Remote Software TeamsProceedings of the IEEE/ACM 46th International Conference on Software Engineering10.1145/3597503.3623297(1-12)Online publication date: 20-May-2024
  • (2024)Product managers in software startupsInformation and Software Technology10.1016/j.infsof.2024.107516174:COnline publication date: 1-Oct-2024
  • (2023)Distributed Scrum: A Case Meta-analysisACM Computing Surveys10.1145/362651956:4(1-37)Online publication date: 10-Nov-2023
  • (2023)Product backlog optimization technique in agile software development using clustering algorithmMultimedia Tools and Applications10.1007/s11042-023-15406-w82:30(46695-46715)Online publication date: 1-Dec-2023
  • (2022)Towards reliable agile iterative planning via predicting documentation changes of work itemsProceedings of the 19th International Conference on Mining Software Repositories10.1145/3524842.3528445(35-47)Online publication date: 23-May-2022
  • (2022)Paving the way to a software-supported requirements prioritization in distributed scrum projectsProceedings of the 5th International Workshop on Software-intensive Business: Towards Sustainable Software Business10.1145/3524614.3528633(51-58)Online publication date: 18-May-2022
  • (2022)Blurring boundariesInformation and Software Technology10.1016/j.infsof.2021.106670140:COnline publication date: 22-Apr-2022
  • Show More Cited By

View Options

Login options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media