Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
skip to main content
research-article

Information needs and presentation in agile software development

Published: 01 October 2023 Publication History
  • Get Citation Alerts
  • Abstract

    Context:

    Agile software companies applying the DevOps approach require collaboration and information sharing between practitioners in various roles to produce value. Adopting new development practices affects how practitioners collaborate, requiring companies to form a closer connection between business strategy and software development. However, the types of information management, sales, and development needed to plan, evaluate features, and reconcile their expectations with each other need to be clarified.

    Objective:

    To support practitioners in collaborating and realizing changes to their practices, we investigated what information is needed and how it should be represented to support different stakeholders in their tasks. Compared to earlier research, we adopted a holistic approach – by including practitioners throughout the development process – to better understand the information needs from a broader viewpoint.

    Method:

    We conducted six workshops and 12 semi-structured interviews at three Finnish small and medium-sized enterprises from different software domains. Thematic analysis was used to identify information-related issues and information and visualization needs for daily tasks. Three themes were constructed as the result of our analysis.

    Results:

    Visual information representation catalyzes stakeholder discussion, and supporting information exchange between stakeholder groups is vital for efficient collaboration in software product development. Additionally, user-centric data collection practices are needed to understand how software products are used and to support practitioners’ daily information needs. We also found that a passive way of representing information, such as a dashboard that would disturb practitioners only when attention is needed, was preferred for daily information needs.

    Conclusion:

    The software engineering community should consider reviewing the information needs of practitioners from a more holistic view to better understand how tooling support can benefit information exchange between stakeholder groups when making product development decisions and how those tools should be built to accommodate different stakeholder views.

    References

    [1]
    Järvinen J., Huomo T., Mikkonen T., Tyrväinen P., From agile software development to mercury business, in: International Conference of Software Business, Springer International Publishing, Springer, Cham, 2014, pp. 58–71,.
    [2]
    Ebert C., Gallardo G., Hernantes J., Serrano N., DevOps, IEEE Softw. 33 (3) (2016) 94–100,.
    [3]
    Hemon A., Lyonnet B., Rowe F., Fitzgerald B., From agile to DevOps: Smart skills and collaborations, Inf. Syst. Front. 22 (4) (2020) 927–945,.
    [4]
    Riungu-Kalliosaari L., Mäkinen S., Lwakatare L.E., Tiihonen J., Männistö T., DevOps adoption benefits and challenges in practice: A case study, in: Product-Focused Software Process Improvement, Springer International Publishing, Cham, 2016, pp. 590–597,.
    [5]
    Fitzgerald B., Stol K.-J., Continuous software engineering: A roadmap and agenda, J. Syst. Softw. 123 (2017) 176–189,.
    [6]
    Lehtola L., Kauppinen M., Vähäniitty J., Komssi M., Linking business and requirements engineering: is solution planning a missing activity in software product companies?, Requir. Eng. 14 (2) (2009) 113–128,.
    [7]
    Klotins E., Gorschek T., Sundelin K., Falk E., Towards cost-benefit evaluation for continuous software engineering activities, Empir. Softw. Eng. 27 (157) (2022),.
    [8]
    Paredes J., Anslow C., Maurer F., Information visualization for agile software development, in: 2014 Second IEEE Working Conference on Software Visualization, 2014, pp. 157–166,.
    [9]
    Cataldo M., Herbsleb J.D., Coordination breakdowns and their impact on development productivity and software failures, IEEE Trans. Softw. Eng. 39 (3) (2013) 343–360,.
    [10]
    Mattila A.-L., Ihantola P., Kilamo T., Luoto A., Nurminen M., Väätäjä H., Software visualization today: Systematic literature review, in: Proceedings of the 20th International Academic Mindtrek Conference, AcademicMindtrek ’16, Association for Computing Machinery, New York, NY, USA, 2016, pp. 262–271,.
    [11]
    Chotisarn N., Merino L., Zheng X., Lonapalawong S., Zhang T., Xu M., Chen W., A systematic literature review of modern software visualization, J. Vis. 23 (4) (2020) 539–558,.
    [12]
    Freeman R.E., The politics of stakeholder theory: Some future directions, Bus. Ethics Q. 4 (4) (1994) 409–421,.
    [13]
    Anderson J.B., Johnnesson R., Understanding Information Transmission, John Wiley & Sons, 2006.
    [14]
    Storey M.-A.D., Čubranić D., German D.M., On the use of visualization to support awareness of human activities in software development: A survey and a framework, in: Proceedings of the 2005 ACM Symposium on Software Visualization, SoftVis ’05, Association for Computing Machinery, New York, NY, USA, 2005, pp. 193–202,.
    [15]
    Maletic J.I., Marcus A., Collard M.L., A task oriented view of software visualization, in: Proceedings First International Workshop on Visualizing Software for Understanding and Analysis, 2002, pp. 32–40,.
    [16]
    Beck K., Beedle M., Van Bennekum A., Cockburn A., Cunningham W., Fowler M., Grenning J., Highsmith J., Hunt A., Jeffries R., et al., Manifesto for agile software development, 2001, URL http://agilemanifesto.org/.
    [17]
    Yilmaz M., O’Connor R.V., Clarke P., Software process improvement and capability determination, Commun. Comput. Inf. Sci. 290 CCIS (2012) 198–209,.
    [18]
    Yilmaz M., O’Connor R.V., Clarke P., Software development roles: A multi-project empirical investigation, ACM SIGSOFT Softw. Eng. Notes 40 (1) (2015) 1–5,.
    [19]
    Palmer S.R., Felsing M., A Practical Guide to Feature-Driven Development, first ed., Pearson Education, 2001.
    [20]
    Beck K., Extreme Programming Explained: Embrace Change, Addison-Wesley Professional, 2000.
    [21]
    Schwaber K., Beedle M., Agile Software Development with Scrum, first ed., Prentice Hall PTR, USA, 2001.
    [22]
    Alqudah M., Razali R., A review of scaling agile methods in large software development, Int. J. Adv. Sci. Eng. Inf. Technol. 6 (6) (2016) 828–837,.
    [23]
    Leffingwell D., Scaling Software Agility: Best Practices for Large Enterprises, Addison-Wesley Professional, 2007.
    [24]
    Larman C., Vodde B., Practices for Scaling Lean & Agile Development: Large, Multisite, and Offshore Product Development with Large-Scale Scrum, first ed., Addison-Wesley Professional, 2010.
    [25]
    Dybå T., Dingsøyr T., Empirical studies of agile software development: A systematic review, Inf. Softw. Technol. 50 (9–10) (2008) 833–859,.
    [26]
    Gustavsson T., Assigned roles for inter-team coordination in large-scale agile development: A literature review, in: Proceedings of the XP2017 Scientific Workshops, XP ’17, Association for Computing Machinery, New York, NY, USA, 2017, pp. 1–5,.
    [27]
    Hoda R., Murugesan L.K., Multi-level agile project management challenges: A self-organizing team perspective, J. Syst. Softw. 117 (2016) 245–257,.
    [28]
    Hoda R., Noble J., Marshall S., Self-organizing roles on agile software development teams, IEEE Trans. Softw. Eng. 39 (3) (2013) 422–444,.
    [29]
    Zhu H., Zhou M., Seguin P., Supporting software development with roles, IEEE Trans. Syst. Man Cybern. - A 36 (6) (2006) 1110–1123,.
    [30]
    Beranek G., Zuser W., Grechenig T., Functional group roles in software engineering teams, in: Proceedings of the 2005 Workshop on Human and Social Factors of Software Engineering, HSSE ’05, Association for Computing Machinery, New York, NY, USA, 2005, pp. 1–7,.
    [31]
    Ye Y., Supporting software development as knowledge-intensive and collaborative activity, in: Proceedings of the 2006 International Workshop on Workshop on Interdisciplinary Software Engineering Research, WISER ’06, Association for Computing Machinery, New York, NY, USA, 2006, pp. 15–22,.
    [32]
    Bouraffa A., Maalej W., Two decades of empirical research on developers’ information needs: A preliminary analysis, in: Proceedings of the IEEE/ACM 42nd International Conference on Software Engineering Workshops, ICSEW ’20, Association for Computing Machinery, New York, NY, USA, 2020, pp. 71–77,.
    [33]
    Hess A., Diebold P., Seyff N., Understanding information needs of agile teams to improve requirements communication, J. Ind. Inf. Integr. 14 (2019) 3–15,.
    [34]
    Cockburn A., Agile software development joins the” would-be” crowd, Cutter IT J. 15 (1) (2002) 6–12.
    [35]
    Pascarella L., Spadini D., Palomba F., Bruntink M., Bacchelli A., Information needs in contemporary code review, Proc. ACM Hum.-Comput. Interact. 2 (CSCW) (2018) 1–27,.
    [36]
    Sutherland A., Venolia G., Can peer code reviews be exploited for later information needs?, in: 2009 31st International Conference on Software Engineering - Companion Volume, 2009, pp. 259–262,.
    [37]
    Kortum F., Klünder J., Karras O., Brunotte W., Schneider K., Which information help agile teams the most? An experience report on the problems and needs, in: 2020 46th Euromicro Conference on Software Engineering and Advanced Applications (SEAA), 2020, pp. 306–313,.
    [38]
    Müller S.C., Fritz T., Stakeholders’ information needs for artifacts and their dependencies in a real world context, in: 2013 IEEE International Conference on Software Maintenance, 2013, pp. 290–299,.
    [39]
    Ko A.J., DeLine R., Venolia G., Information needs in collocated software development teams, in: 29th International Conference on Software Engineering (ICSE’07), 2007, pp. 344–353,.
    [40]
    Omoronyia I., Ferguson J., Roper M., Wood M., A review of awareness in distributed collaborative software engineering, Softw. - Pract. Exp. 40 (12) (2010) 1107–1133,.
    [41]
    Josyula J., Panamgipalli S., Usman M., Britto R., Bin Ali N., Software practitioners’ information needs and sources: A survey study, in: 2018 9th International Workshop on Empirical Software Engineering in Practice (IWESEP), 2018, pp. 1–6,.
    [42]
    LaToza T.D., Myers B.A., Developers ask reachability questions, in: Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1, ICSE ’10, Association for Computing Machinery, New York, NY, USA, 2010, pp. 185–194,.
    [43]
    Ahmad A., Leifler O., Sandahl K., Software professionals’ information needs in continuous integration and delivery, in: Proceedings of the 36th Annual ACM Symposium on Applied Computing, SAC ’21, Association for Computing Machinery, New York, NY, USA, 2021, pp. 1513–1520,.
    [44]
    Buse R.P.L., Zimmermann T., Information needs for software development analytics, in: 2012 34th International Conference on Software Engineering (ICSE), 2012, pp. 987–996,.
    [45]
    Breu S., Premraj R., Sillito J., Zimmermann T., Information needs in bug reports: Improving cooperation between developers and users, in: Proceedings of the 2010 ACM Conference on Computer Supported Cooperative Work, CSCW ’10, Association for Computing Machinery, New York, NY, USA, 2010, pp. 301–310,.
    [46]
    Holz H., Maurer F., Knowledge management support for distributed agile software processes, in: Advances in Learning Software Organizations, Springer, Berlin, Heidelberg, 2003, pp. 60–80,.
    [47]
    Ghobadi S., What drives knowledge sharing in software development teams: A literature review and classification framework, Inf. Manage. 52 (1) (2015) 82–97,.
    [48]
    Roman G.-C., Cox K.C., Program visualization: The art of mapping programs to pictures, in: Proceedings of the 14th International Conference on Software Engineering, ICSE ’92, Association for Computing Machinery, New York, NY, USA, 1992, pp. 412–420,.
    [49]
    Price B.A., Baecker R.M., Small I.S., A principled taxonomy of software visualization, J. Vis. Lang. Comput. 4 (3) (1993) 211–266,.
    [50]
    Gotel O.C., Marchese F.T., Morris S.J., The potential for synergy between information visualization and software engineering visualization, in: 2008 12th International Conference Information Visualisation, 2008, pp. 547–552,.
    [51]
    Diehl S., Software Visualization: Visualizing the Structure, Behaviour, and Evolution of Software, Springer Berlin, Heidelberg, 2007,.
    [52]
    Novais R.L., Torres A., Mendes T.S., Mendonça M., Zazworka N., Software evolution visualization: A systematic mapping study, Inf. Softw. Technol. 55 (11) (2013) 1860–1883,.
    [53]
    Seriai A., Benomar O., Cerat B., Sahraoui H., Validation of software visualization tools: A systematic mapping study, in: 2014 Second IEEE Working Conference on Software Visualization, 2014, pp. 60–69,.
    [54]
    Merino L., Ghafari M., Anslow C., Nierstrasz O., A systematic literature review of software visualization evaluation, J. Syst. Softw. 144 (2018) 165–180,.
    [55]
    Merino L., Ghafari M., Nierstrasz O., Towards actionable visualization for software developers, J. Softw.: Evol. Process 30 (2) (2018),.
    [56]
    Koschke R., Software visualization in software maintenance, reverse engineering, and re-engineering: A research survey, J. Softw. Maint. Evol. 15 (2) (2003) 87–109,.
    [57]
    Gross A., Doerr J., What you need is what you get!: The vision of view-based requirements specifications, in: 2012 20th IEEE International Requirements Engineering Conference (RE), 2012, pp. 171–180,.
    [58]
    Gross A., Doerr J., What do software architects expect from requirements specifications? results of initial explorative studies, in: 2012 First IEEE International Workshop on the Twin Peaks of Requirements and Architecture (TwinPeaks), 2012, pp. 41–45,.
    [59]
    Hess A., Doerr J., Seyff N., How to make use of empirical knowledge about testers’ information needs, in: 2017 IEEE 25th International Requirements Engineering Conference Workshops (REW), 2017, pp. 327–330,.
    [60]
    Jedlitschka A., Juristo N., Rombach D., Reporting experiments to satisfy professionals’ information needs, Empir. Softw. Eng. 19 (6) (2014) 1921–1955,.
    [61]
    Panas T., Epperly T., Quinlan D., Saebjornsen A., Vuduc R., Communicating software architecture using a unified single-view visualization, in: 12th IEEE International Conference on Engineering Complex Computer Systems (ICECCS 2007), 2007, pp. 217–228,.
    [62]
    Kaya A., Dutre S., Stegen J., Jha S.P., Denil J., Stakeholder specific visualisation from heterogeneous modeling tools, in: CEUR Workshop Proceedings, Vol. 2245, 2018, pp. 213–222.
    [63]
    Logre I., Déry-Pinna A.-M., MDE in support of visualization systems design: A multi-staged approach tailored for multiple roles, Proc. ACM Hum.-Comput. Interact. 2 (EICS) (2018),.
    [64]
    Runeson P., Höst M., Guidelines for conducting and reporting case study research in software engineering, Empir. Softw. Eng. 14 (2) (2009) 131–164,.
    [65]
    Braun V., Clarke V., Using thematic analysis in psychology, Qual. Res. Psychol. 3 (2) (2006) 77–101,.
    [66]
    Etikan I., Musa S.A., Alkassim R.S., Comparison of convenience sampling and purposive sampling, Am. J. Theor. Appl. Stat. 5 (1) (2016) 1–4,.
    [67]
    Cohen J., Weighted kappa: Nominal scale agreement provision for scaled disagreement or partial credit, Psychol. Bull. 70 (4) (1968) 213–220,.
    [68]
    Clarke V., Braun V., Thematic analysis: a practical guide, Themat. Anal. (2021) 1–100.
    [69]
    Orlikowski W.J., Baroudi J.J., Studying information technology in organizations: Research approaches and assumptions, Inf. Syst. Res. 2 (1) (1991) 1–28.
    [70]
    Rodríguez P., Urquhart C., Mendes E., A theory of value for value-based feature selection in software engineering, IEEE Trans. Softw. Eng. 48 (2) (2022) 466–484,.
    [71]
    Sauvola T., Lwakatare L.E., Karvonen T., Kuvaja P., Olsson H.H., Bosch J., Oivo M., Towards customer-centric software development: A multiple-case study, in: 2015 41st Euromicro Conference on Software Engineering and Advanced Applications, 2015, pp. 9–17,.
    [72]
    Rodríguez P., Haghighatkhah A., Lwakatare L.E., Teppola S., Suomalainen T., Eskeli J., Karvonen T., Kuvaja P., Verner J.M., Oivo M., Continuous deployment of software intensive products and services: A systematic mapping study, J. Syst. Softw. 123 (2017) 263–291,.
    [73]
    Komssi M., Kauppinen M., Töhönen H., Lehtola L., Davis A.M., Roadmapping problems in practice: value creation from the perspective of the customers, Requir. Eng. 20 (1) (2015) 45–69,.
    [74]
    Creswell J.W., Miller D.L., Determining validity in qualitative inquiry, Theory Into Pract. 39 (3) (2000) 124–130,.
    [75]
    Braun V., Clarke V., One size fits all? What counts as quality practice in (reflexive) thematic analysis?, Qual. Res. Psychol. 18 (3) (2021) 328–352,.

    Recommendations

    Comments

    Information & Contributors

    Information

    Published In

    cover image Information and Software Technology
    Information and Software Technology  Volume 162, Issue C
    Oct 2023
    170 pages

    Publisher

    Butterworth-Heinemann

    United States

    Publication History

    Published: 01 October 2023

    Author Tags

    1. Software engineering
    2. Agile software development
    3. DevOps
    4. Information needs
    5. Visualization

    Qualifiers

    • Research-article

    Contributors

    Other Metrics

    Bibliometrics & Citations

    Bibliometrics

    Article Metrics

    • 0
      Total Citations
    • 0
      Total Downloads
    • Downloads (Last 12 months)0
    • Downloads (Last 6 weeks)0
    Reflects downloads up to 12 Aug 2024

    Other Metrics

    Citations

    View Options

    View options

    Get Access

    Login options

    Media

    Figures

    Other

    Tables

    Share

    Share

    Share this Publication link

    Share on social media