Advertisement

Prioritization of Stakeholder Value Using Metrics

  • Lindsey Brodie
  • Mark Woodman
Conference paper
Part of the Communications in Computer and Information Science book series (CCIS, volume 230)

Abstract

Given the reality of resource constraints, software development always involves prioritization to establish what to implement. Iterative and incremental development methods increase the need to support dynamic prioritization to identify high stakeholder value. In this paper we argue that the current prioritization methods fail to appropriately structure the data for stakeholder value. This problem is often compounded by a failure to handle multiple stakeholder viewpoints. We propose an extension to an existing prioritization method, impact estimation, to move towards better capture of explicit stakeholder value and to cater for multiple stakeholders. A key feature is the use of absolute scale data for stakeholder value. We use a small industry case study to evaluate this new approach. Our findings argue that it provides a better basis for supporting priority decision-making over the implementation choices for requirements and designs.

Keywords

Stakeholder value Impact estimation Requirements prioritization Design prioritization Metrics Value-based software engineering 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Gilb, T.: Competitive Engineering: A Handbook For Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage. In: Brodie, L. (ed.). Butterworth-Heinemann, London (2005) ISBN 0750665076Google Scholar
  2. 2.
    Boehm, B., Port, D., Basili, V.R.: Realizing the Benefits of the CMMI with the CeBASE Method. Systems Engineering (2002)Google Scholar
  3. 3.
    Bourque, P., Dupuis, R. (eds.): SWEBOK: Guide to the Software Engineering Body of Knowledge 2004 Version. IEEE Computer Society, Los Alamitos (2004)Google Scholar
  4. 4.
    Boehm, B.: Value-Based Software Engineering. Software Engineering Notes 28(2) (2003)Google Scholar
  5. 5.
    Sullivan, K.: Introduction to the First Workshop on the Economics of Software and Computation. In: Companion to the Procs. of the 29th International Conf. on Software Engineering. IEEE, Los Alamitos (2007)Google Scholar
  6. 6.
    Larman, C., Basili, V.R.: Iterative and Incremental Development: a Brief History. IEEE Computer 36(6) (2003) Google Scholar
  7. 7.
    Park, J., Port, D., Boehm, B.: Supporting Distributed Collaborative Prioritization for Win-Win Requirements Capture and Negotiation. In: Procs. of the International Third World Multi-Conference on Systemics, Cybernetics and Informatics (SCI 1999). International Institute of Informatics and Systemics (1999) Google Scholar
  8. 8.
    Davis, A.: The Art of Requirements Triage. IEEE Computer 36(3), 42–49 (2003)CrossRefGoogle Scholar
  9. 9.
    Karlsson, J., Ryan, K.: A Cost-Value Approach for Prioritizing Requirements. IEEE Software (1997) Google Scholar
  10. 10.
    Saaty, T.L.: How to Make a Decision: The Analytic Hierarchy Process. European Journal of Operational Research 48, 9–26 (1990)CrossRefzbMATHGoogle Scholar
  11. 11.
    Karlsson, J., Wohlin, C., Regnell, B.: An Evaluation of Methods for Prioritizing Software Requirements. Information and Software Technology (1998)Google Scholar
  12. 12.
    Moisiadis, F.: The Fundamentals of Prioritising Requirements. In: Procs. of the Systems Engineering, Test and Evaluation Conference (2002)Google Scholar
  13. 13.
    Berander, P., Andrews, A.: Requirements Prioritization (ch. 4). In: Aurum, A., Wohlin, C. (eds.) Engineering and Managing Software Requirements. Springer, Heidelberg (2005) ISBN 3540250433Google Scholar
  14. 14.
    Greer, D., Ruhe, G.: Software release planning: an evolutionary and iterative approach. Information and Software Technology 46(4), 243–253 (2004)CrossRefGoogle Scholar
  15. 15.
    Kazman, R., Asundi, J., Klein, M.: Quantifying the Costs and Benefits of Architectural Decisions. In: Procs. of the 23rd International Conference on Software Engineering (ICSE 2001). IEEE, Los Alamitos (2001)Google Scholar
  16. 16.
    Mohamed, A., Ruhe, G., Eberlein, A.: COTS Selection: Past, Present, and Future. In: Procs. of the IEEE Intl. Conf. and Workshops on the Engineering of Computer-Based Systems (ECBS 2007). IEEE, Los Alamitos (2007)Google Scholar
  17. 17.
    Favaro, J.: Managing Requirements for Business Value. IEEE Software (March/April 2002) Google Scholar
  18. 18.
    Sivzattian, S.V.: Requirements as Economic Artifacts: A Portfolio-Based Approach, Ph.D. Thesis. Department of Computing, Imperial College of Science, Technology and Medicine, London (2003) Google Scholar
  19. 19.
    Stapleton, J. (ed.): DSDM: Business Focused Development, 2nd edn. Addison Wesley, Reading (2003)Google Scholar
  20. 20.
    Berander, P.: Evolving Prioritization for Software Product Management. Blekinge Institute of Technology. Doctoral Dissertation Series (2007) Google Scholar
  21. 21.
    Lehtola, L., Kauppinen, M.: Suitability of Requirements Prioritization Methods for Market-driven Software Product Development. In: Software Process Improvement and Practice. Wiley, Chichester (2006)Google Scholar
  22. 22.
    Cohen, L.: Quality Function Deployment: How to Make QFD Work for You. Addison Wesley, Reading (1995)Google Scholar
  23. 23.
    Akao, Y.: QFD: Past, Present, and Future. In: Procs. of the International Symposium on QFD 1997, Linkoping (1997) Google Scholar
  24. 24.
    Bass, L., Ivers, J., Klein, M., Merson, P.: Reasoning Frameworks (CMU/SEI-2005-TR-007). Software Engineering Institute, CMU (2005) Google Scholar
  25. 25.
    Mohamed, A., Ruhe, G., Eberlein, A.: Decision Support for Handling Mismatches between COTS Products and System Requirements. In: Procs. of the COTS-Based Software Systems (ICCBSS 2007) Conf. (2007)Google Scholar
  26. 26.
    Beck, K.: Extreme Programming Explained: Embrace Change. Addison Wesley, Reading (2000)Google Scholar
  27. 27.
    Saliu, O., Ruhe, G.: Supporting Software Release Planning Decisions for Evolving Systems. In: Procs. of the 2005 29th Annual IEEE/NASA Software Engineering Workshop (SEW 2005). IEEE, Los Alamitos (2005)Google Scholar
  28. 28.
    Favaro, J.: Value-Based Management and Agile Methods. In: Marchesi, M., Succi, G. (eds.) XP 2003. LNCS, vol. 2675. Springer, Heidelberg (2003)CrossRefGoogle Scholar
  29. 29.
    Denne, M., Cleland-Huang, J.: Software by Numbers: Low-Risk, High-Return Development, 190 pages. Prentice-Hall, Englewood Cliffs (2004) ISBN 0131407287Google Scholar
  30. 30.
    Ruhe, G., Eberlein, A., Pfahl, D.: Trade-off Analysis for Requirements Selection. International Journal of Software Engineering and Knowledge Engineering 13(4), 345–366 (2003)CrossRefGoogle Scholar
  31. 31.
    Green, P.E., Wind, Y.: New Way to Measure Consumers Judgments. Harvard Business Review (1975)Google Scholar
  32. 32.
    Lehtola, L.: Providing value by prioritizing requirements throughout software product development: State of practice and suitability of prioritization methods. Licentiate thesis, Helsinki University of Technology (2006)Google Scholar
  33. 33.
    Martins, A., Aspinwall, E.: Quality Function Deployment: an empirical study in the UK. Total Quality Management (August 2001) Google Scholar
  34. 34.
    Wohlin, C., Aurum, A.: Criteria for Selecting Software Requirements to Create Product Value: An Industrial Empirical Study. In: Biffl, S., Aurum, A., Boehm, B., Erdogmus, H., Grunbacher, P. (eds.) Value-Based Software Engineering. Springer, Heidelberg (2005)Google Scholar
  35. 35.
    Barney, S., Aurum, A., Wohlin, C.: A product management challenge: Creating software product value through requirements selection. Journal of Systems Architecture (2008) Google Scholar
  36. 36.
    Carlshamre, P., Sandahl, K., Lindvall, M., Regnell, B., Natt och Dag, J.: An Industrial Survey of Requirements Interdependencies in Software Product Release Planning. In: Procs. of the 5th IEEE International Symposium on RE (2001)Google Scholar
  37. 37.
    Firesmith, D.: Prioritizing Requirements. Journal of Object Technology (2004) Google Scholar
  38. 38.
    Gorschek, T., Wohlin, C.: Requirements Abstraction Model. Requirements Engineering 11, 79–101 (2006)CrossRefGoogle Scholar
  39. 39.
    Mead, N.: Requirements Prioritization Introduction. Software Engineering Institute (SEI), Carnegie Mellon University (CMU) (2006) Google Scholar
  40. 40.
    Gilb, T.: Principles of Software Engineering Management. Addison Wesley, Reading (1988) ISBN 0201192462zbMATHGoogle Scholar
  41. 41.
    Brodie, L., Woodman, M.: Towards a Rational Prioritization Process for Incremental and Iterative Systems Engineering. In: Procs. of the 1st International Workshop on Requirements Analysis. Pearson, London (2008)Google Scholar
  42. 42.
    Daniels, J., Werner, P.W., Bahill, A.T.: Quantitative Methods for Tradeoff Analyses. Systems Engineering 4(3) (2001)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2011

Authors and Affiliations

  • Lindsey Brodie
    • 1
  • Mark Woodman
    • 1
  1. 1.School of Engineering and Information SciencesMiddlesex UniversityLondonU.K.

Personalised recommendations