Analysis of Stakeholder/ Value Dependency Patterns and Process Implications: A Controlled Experiment

Keywords Analysis of Stakeholder/ Value Dependency Patterns and Process Implications: A Controlled Experiment

As happens with many software projects in
practice, we often just had real clients and did not
have real user and real maintainer representatives. As
an alternative, students were instructed to role play
client, user, and maintainer, which created an
opportunity to assess the effectiveness of using role
players to represent actual stakeholders. We will
compare the results between real-client and role-play
client. If the results show a strong correlation, it will
provide some confidence for accepting results from
role-play users and role-play maintainers.

To make sure that the experiment is under
control, in this step we teach students how to roleplay:
A challenge in this experiment is to identify
role players who are able to prioritize from the
perspective of other stakeholders. We suggested to
teams to identify role players based on who best
understands the type of stakeholder. For example, the
person who works on the operational concept could
be a good candidate to role play user. We also
provided some value proposition hints for the role
players to consider. For example, the role play client
may consider on time, within budget, functions are
correctly implemented, and are interoperable with
existing system, etc.

Date published
Document type
technical white paper
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
File MIME type Size (KB) Language Download
usc-csse-2009-520.pdf application/pdf   251.32 KB English DOWNLOAD!
File attachments

Different classes of information system stakeholders depend on different values to be successful. Understanding stakeholders’ value dependencies is critical for developing software intensive systems. However, there is no universal one-size-fits-all stakeholder/ value metric that can be applied for a given system. This paper presents an analysis of major classes of stakeholders’ value priorities using the win-win prioritization results from 16 real-client graduate software engineering course projects. Findings from this controlled experiment further verify and extend the hypotheses that “different stakeholders have different value
propositions”, bridge the value understanding gaps among different stakeholders, beneficial for further reasoning about stakeholders’ utility functions and for providing process guidance for software projects involving various classes of stakeholders.

Visit also