A Conceptual Model of Client-driven Agile Requirements Prioritization: Results of a Case Study

Z. Racheva, Maia Daneva, Andrea Herrmann

    Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

    20 Citations (Scopus)
    54 Downloads (Pure)

    Abstract

    ABSTRACT Requirements (re)prioritization is an essential mechanism of agile development approaches to maximize the value for the clients and to accommodate changing requirements. Yet, in the agile Requirements Engineering (RE) literature, very little is known about how agile (re)prioritization happens in practice. Conceptual models about this process are missing, which, in turn, makes it difficult for both practitioners and researchers to reason about requirements decision-making at inter-iteration time. We did a multiple case study on agile requirements prioritization methods to yield a conceptual model for understanding the inter-iteration prioritization process. The model is derived by using interview data from practitioners in 8 development organizations. Such a model makes explicit the concepts that are used tacitly in the agile requirements prioritization practice and can be used for structuring future empirical investigations about this topic, and for analyzing, supporting, and improving the process in real-life projects.
    Original languageEnglish
    Title of host publicationESEM '10 Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement
    EditorsG. Succi, M. Morisio, N. Nagappan
    Place of PublicationNew York
    PublisherAssociation for Computing Machinery (ACM)
    Number of pages4
    ISBN (Print)978-1-4503-0039-1
    DOIs
    Publication statusPublished - Sep 2010
    Event4th ACM-IEEE International Symposium on Empirical Software Engineering and Measurement 2010 - Bolzano-Bozen, Italy
    Duration: 15 Sep 201017 Sep 2010
    Conference number: 4

    Conference

    Conference4th ACM-IEEE International Symposium on Empirical Software Engineering and Measurement 2010
    Abbreviated titleESEM 2010
    CountryItaly
    CityBolzano-Bozen
    Period15/09/1017/09/10

    Fingerprint

    Requirements engineering
    Decision making

    Keywords

    • IR-72800
    • METIS-271006
    • Agile development
    • SCS-Services
    • Requirements Prioritization
    • EWI-18350
    • inter-iteration decision-making process
    • Case Study

    Cite this

    Racheva, Z., Daneva, M., & Herrmann, A. (2010). A Conceptual Model of Client-driven Agile Requirements Prioritization: Results of a Case Study. In G. Succi, M. Morisio, & N. Nagappan (Eds.), ESEM '10 Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement [39] New York: Association for Computing Machinery (ACM). https://doi.org/10.1145/1852786.1852837
    Racheva, Z. ; Daneva, Maia ; Herrmann, Andrea. / A Conceptual Model of Client-driven Agile Requirements Prioritization: Results of a Case Study. ESEM '10 Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement. editor / G. Succi ; M. Morisio ; N. Nagappan. New York : Association for Computing Machinery (ACM), 2010.
    @inproceedings{b65b5c8166a34430870f5715c7107cb8,
    title = "A Conceptual Model of Client-driven Agile Requirements Prioritization: Results of a Case Study",
    abstract = "ABSTRACT Requirements (re)prioritization is an essential mechanism of agile development approaches to maximize the value for the clients and to accommodate changing requirements. Yet, in the agile Requirements Engineering (RE) literature, very little is known about how agile (re)prioritization happens in practice. Conceptual models about this process are missing, which, in turn, makes it difficult for both practitioners and researchers to reason about requirements decision-making at inter-iteration time. We did a multiple case study on agile requirements prioritization methods to yield a conceptual model for understanding the inter-iteration prioritization process. The model is derived by using interview data from practitioners in 8 development organizations. Such a model makes explicit the concepts that are used tacitly in the agile requirements prioritization practice and can be used for structuring future empirical investigations about this topic, and for analyzing, supporting, and improving the process in real-life projects.",
    keywords = "IR-72800, METIS-271006, Agile development, SCS-Services, Requirements Prioritization, EWI-18350, inter-iteration decision-making process, Case Study",
    author = "Z. Racheva and Maia Daneva and Andrea Herrmann",
    note = "eemcs-eprint-18350",
    year = "2010",
    month = "9",
    doi = "10.1145/1852786.1852837",
    language = "English",
    isbn = "978-1-4503-0039-1",
    editor = "G. Succi and M. Morisio and N. Nagappan",
    booktitle = "ESEM '10 Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement",
    publisher = "Association for Computing Machinery (ACM)",
    address = "United States",

    }

    Racheva, Z, Daneva, M & Herrmann, A 2010, A Conceptual Model of Client-driven Agile Requirements Prioritization: Results of a Case Study. in G Succi, M Morisio & N Nagappan (eds), ESEM '10 Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement., 39, Association for Computing Machinery (ACM), New York, 4th ACM-IEEE International Symposium on Empirical Software Engineering and Measurement 2010, Bolzano-Bozen, Italy, 15/09/10. https://doi.org/10.1145/1852786.1852837

    A Conceptual Model of Client-driven Agile Requirements Prioritization: Results of a Case Study. / Racheva, Z.; Daneva, Maia; Herrmann, Andrea.

    ESEM '10 Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement. ed. / G. Succi; M. Morisio; N. Nagappan. New York : Association for Computing Machinery (ACM), 2010. 39.

    Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

    TY - GEN

    T1 - A Conceptual Model of Client-driven Agile Requirements Prioritization: Results of a Case Study

    AU - Racheva, Z.

    AU - Daneva, Maia

    AU - Herrmann, Andrea

    N1 - eemcs-eprint-18350

    PY - 2010/9

    Y1 - 2010/9

    N2 - ABSTRACT Requirements (re)prioritization is an essential mechanism of agile development approaches to maximize the value for the clients and to accommodate changing requirements. Yet, in the agile Requirements Engineering (RE) literature, very little is known about how agile (re)prioritization happens in practice. Conceptual models about this process are missing, which, in turn, makes it difficult for both practitioners and researchers to reason about requirements decision-making at inter-iteration time. We did a multiple case study on agile requirements prioritization methods to yield a conceptual model for understanding the inter-iteration prioritization process. The model is derived by using interview data from practitioners in 8 development organizations. Such a model makes explicit the concepts that are used tacitly in the agile requirements prioritization practice and can be used for structuring future empirical investigations about this topic, and for analyzing, supporting, and improving the process in real-life projects.

    AB - ABSTRACT Requirements (re)prioritization is an essential mechanism of agile development approaches to maximize the value for the clients and to accommodate changing requirements. Yet, in the agile Requirements Engineering (RE) literature, very little is known about how agile (re)prioritization happens in practice. Conceptual models about this process are missing, which, in turn, makes it difficult for both practitioners and researchers to reason about requirements decision-making at inter-iteration time. We did a multiple case study on agile requirements prioritization methods to yield a conceptual model for understanding the inter-iteration prioritization process. The model is derived by using interview data from practitioners in 8 development organizations. Such a model makes explicit the concepts that are used tacitly in the agile requirements prioritization practice and can be used for structuring future empirical investigations about this topic, and for analyzing, supporting, and improving the process in real-life projects.

    KW - IR-72800

    KW - METIS-271006

    KW - Agile development

    KW - SCS-Services

    KW - Requirements Prioritization

    KW - EWI-18350

    KW - inter-iteration decision-making process

    KW - Case Study

    U2 - 10.1145/1852786.1852837

    DO - 10.1145/1852786.1852837

    M3 - Conference contribution

    SN - 978-1-4503-0039-1

    BT - ESEM '10 Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement

    A2 - Succi, G.

    A2 - Morisio, M.

    A2 - Nagappan, N.

    PB - Association for Computing Machinery (ACM)

    CY - New York

    ER -

    Racheva Z, Daneva M, Herrmann A. A Conceptual Model of Client-driven Agile Requirements Prioritization: Results of a Case Study. In Succi G, Morisio M, Nagappan N, editors, ESEM '10 Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement. New York: Association for Computing Machinery (ACM). 2010. 39 https://doi.org/10.1145/1852786.1852837