honeyhilt.blogg.se - Situational contexts

#Situational contexts software

Leaders are asked about their least-preferred coworker (LPC), the person with whom they least like to work. According to Fiedler, organizations attempting to achieve group effectiveness through leadership must assess the leader according to an underlying trait, assess the situation faced by the leader, and construct a proper match between the two. 72 This theory is known as the contingency theory of leadership. Fiedler from the University of Washington. One of the earliest, best-known, and most controversial situation-contingent leadership theories was set forth by Fred E. Victor Vroom, Phillip Yetton, and Arthur Jago’s decision tree model also applies. 71 We explore two of the better-known situational theories of leadership, Fred Fiedler’s contingency model and Robert J. These are Fiedler’s contingency theory of leadership, the path-goal theory of leader effectiveness, Hersey and Blanchard’s life cycle theory, cognitive resource theory, the decision tree, and the decision process theory. Several theories have been advanced to address this issue. Contradictory findings such as this lead researchers to ask “Under what conditions are the results positive in nature?” and “When and why are they negative at other times?” Obviously, situational differences and key contingencies are at work. That is, there are times when initiating structure results in performance increases and follower satisfaction, and there are times when the results are just the opposite.

What are the situational perspectives on leadership?Īs early as 1948, Ralph Stogdill stated that “the qualities, characteristics, and skills required in a leader are determined to a large extent by the demands of the situation in which he is to function as a leader.” 70 In addition, it had been observed that two major leader behaviors, initiating structure and consideration, didn’t always lead to equally positive outcomes.

This version of the article has been accepted for publication, after peer review (when applicable) and is subject to Springer Nature’s AM terms of use, but is not the Version of Record and does not reflect post-acceptance improvements, or any corrections.

> School of Science and Technology > Computer Science Communications in Computer and Information Science, vol 1646.

#Situational contexts software

(eds) Systems, Software and Services Process Improvement. In: Yilmaz, M., Clarke, P., Messnarz, R., Wöran, B. Requirements Volatility in Multicultural Situational Contexts. Siakas, E., Rahanu, H., Georgiadou, E., Siakas, K.

Goal 9: Industry, Innovation, and Infrastructure.

The paper concludes with the presentation of the Requirements Cultural Volatility Framework which aims to reveal potential conflicts that may occur in requirements elicitation on a multiplicity of cultural dimensions, The framework proposes actions to be taken in order to address the conflicts and point out expected benefits on each dimension. This paper builds on an extensive literature review demonstrating the importance of raising awareness and understanding of the role of culture and cultural diversity for requirements volatility, as one of the most significant situational factors in the requirements elicitation process, with the aim to improve the whole systems development process as well as the resulting products and services. Research on the situational context in Requirements Engineering (RE) is rather limited, despite the recognized importance of RE and requirements elicitation for improving the quality of the final system and software product. In this paper, we analyse requirements volatility from a situational context angle with the aim to increase understanding of the role of culture and cultural diversity in a multicultural requirements elicitation process. Different approaches in software development, including Agile and DevOps, have addressed requirements volatility by increasing user participation throughout the whole development process. Requirements volatility refers to additions, deletions, and modifications of requirements during the system development life cycle.