219,029 research outputs found
Recommended from our members
The Impact of Feedback on the Motivation of Software Engineers
This research investigates how feedback affects the motivation of software engineers and develops a model of feedback in software engineering. Motivation has been reported as having an impact on software engineersā productivity, the quality of the software they produce, the overall success of a software development project, and on the retention of software engineers. Findings from the last 30 years of research investigating motivation in software engineering have identified several factors that influence the motivation of software engineers, but the impact of each individual factor remains unclear. Feedback was identified as a factor affecting motivation by several studies investigating motivation in software engineering. Several theories of motivation exist which identify factors affecting motivation and models of how motivation is affected. Feedback is identified as a factor in four theories of motivation. In 2008 a systematic literature review identified that the majority of previous studies investigating motivation in software engineering were not grounded in motivation theory. This suggests that the majority of previous research investigating motivation in software engineering has not adequately considered theories of motivation and their relevance in software engineering.
This research explored the importance of feedback and the effect of the characteristics of feedback on the motivation of software engineers, collecting their thoughts, perceptions, reflections and reactions to feedback using a range of different research methods. The research began with a preliminary study investigating how software engineers perceived feedback, and if the characteristics they identified were comparable to those identified in other disciplines, notably clinical education. Further studies followed by investigating feedback in software engineering, the short-term impact of received feedback, and the effect of the āsourceā and āmediumā feedback characteristics.
The findings of the preliminary study were that software engineers identified characteristics of feedback comparable to those found in clinical education, which gave a basis for further studies. Software engineers reported that feedback was the most common method of tracking their individual progress in a software project. A diary study collecting instances of feedback reported by software engineers found that positive feedback typically increased the engineersā job satisfaction, and that negative feedback typically led to a change in their behaviour.
Building on the earlier findings of this research, a scenario study and an online survey combining both scenarios and questions investigated the effect of the source and medium feedback characteristics. The findings of the four studies identified that the feedback recipientās values and perceptions of the feedback source, and any preference they had to the medium used to send the feedback, affected the impact of received feedback. The findings suggested that the feedback software engineers report as the most valuable is not the same as feedback reported as having the most impact. The findings suggest that in software engineering, theories of motivation do not adequately consider the impact of the characteristics of feedback and the effect of different forms of feedback on motivation.
A model of feedback in software engineering was identified by combining the findings of the four empirical studies and relevant literature. The model captures how feedback is experienced by software engineers. Software engineers perceive the characteristics of the received feedback, which provides information that is used to make several assessments about the feedback. Each engineerās individual value set influences their assessments, and their current state of mind / mood / emotions affect the engineerās perceptions, assessments, and individual value set. The assessments of the feedback then result in the impact of the received feedback, which can have an effect on the engineerās attitude, behaviour, motivation, performance, job satisfaction, and feelings
Rethinking Productivity in Software Engineering
Get the most out of this foundational reference and improve the productivity of your software teams. This open access book collects the wisdom of the 2017 "Dagstuhl" seminar on productivity in software engineering, a meeting of community leaders, who came together with the goal of rethinking traditional definitions and measures of productivity. The results of their work, Rethinking Productivity in Software Engineering, includes chapters covering definitions and core concepts related to productivity, guidelines for measuring productivity in specific contexts, best practices and pitfalls, and theories and open questions on productivity. You'll benefit from the many short chapters, each offering a focused discussion on one aspect of productivity in software engineering. Readers in many fields and industries will benefit from their collected work. Developers wanting to improve their personal productivity, will learn effective strategies for overcoming common issues that interfere with progress. Organizations thinking about building internal programs for measuring productivity of programmers and teams will learn best practices from industry and researchers in measuring productivity. And researchers can leverage the conceptual frameworks and rich body of literature in the book to effectively pursue new research directions. What You'll Learn Review the definitions and dimensions of software productivity See how time management is having the opposite of the intended effect Develop valuable dashboards Understand the impact of sensors on productivity Avoid software development waste Work with human-centered methods to measure productivity Look at the intersection of neuroscience and productivity Manage interruptions and context-switching Who Book Is For Industry developers and those responsible for seminar-style courses that include a segment on software developer productivity. Chapters are written for a generalist audience, without excessive use of technical terminology. ; Collects the wisdom of software engineering thought leaders in a form digestible for any developer Shares hard-won best practices and pitfalls to avoid An up to date look at current practices in software engineering productivit
Understanding Work Practices of Autonomous Agile Teams: A Social-psychological Review
The purpose of this paper is to suggest additional aspects of social
psychology that could help when making sense of autonomous agile teams. To make
use of well-tested theories in social psychology and instead see how they
replicated and differ in the autonomous agile team context would avoid
reinventing the wheel. This was done, as an initial step, through looking at
some very common agile practices and relate them to existing findings in
social-psychological research. The two theories found that I argue could be
more applied to the software engineering context are social identity theory and
group socialization theory. The results show that literature provides
social-psychological reasons for the popularity of some agile practices, but
that scientific studies are needed to gather empirical evidence on these
under-researched topics. Understanding deeper psychological theories could
provide a better understanding of the psychological processes when building
autonomous agile team, which could then lead to better predictability and
intervention in relation to human factors
Rethinking Productivity in Software Engineering
Get the most out of this foundational reference and improve the productivity of your software teams. This open access book collects the wisdom of the 2017 "Dagstuhl" seminar on productivity in software engineering, a meeting of community leaders, who came together with the goal of rethinking traditional definitions and measures of productivity. The results of their work, Rethinking Productivity in Software Engineering, includes chapters covering definitions and core concepts related to productivity, guidelines for measuring productivity in specific contexts, best practices and pitfalls, and theories and open questions on productivity. You'll benefit from the many short chapters, each offering a focused discussion on one aspect of productivity in software engineering. Readers in many fields and industries will benefit from their collected work. Developers wanting to improve their personal productivity, will learn effective strategies for overcoming common issues that interfere with progress. Organizations thinking about building internal programs for measuring productivity of programmers and teams will learn best practices from industry and researchers in measuring productivity. And researchers can leverage the conceptual frameworks and rich body of literature in the book to effectively pursue new research directions. What You'll Learn Review the definitions and dimensions of software productivity See how time management is having the opposite of the intended effect Develop valuable dashboards Understand the impact of sensors on productivity Avoid software development waste Work with human-centered methods to measure productivity Look at the intersection of neuroscience and productivity Manage interruptions and context-switching Who Book Is For Industry developers and those responsible for seminar-style courses that include a segment on software developer productivity. Chapters are written for a generalist audience, without excessive use of technical terminology. ; Collects the wisdom of software engineering thought leaders in a form digestible for any developer Shares hard-won best practices and pitfalls to avoid An up to date look at current practices in software engineering productivit
Science for Global Ubiquitous Computing
This paper describes an initiative to provide theories that can underlie the development of the Global Ubiquitous Computer, the network of ubiquitous computing devices that will pervade the civilised world in the course of the next few decades. We define the goals of the initiative and the criteria for judging whether they are achieved; we then propose a strategy for the exercise. It must combine a bottom-up development of theories in directions that are currently pursued with success, together with a top-down approach in the form of collaborative projects relating these theories to engineered systems that exist or are imminent
The role of Comprehension in Requirements and Implications for Use Case Descriptions
Within requirements engineering it is generally accepted that in writing specifications (or indeed any requirements phase document), one attempts to produce an artefact which will be simple to comprehend for the user. That is, whether the document is intended for customers to validate requirements, or engineers to understand what the design must deliver, comprehension is an important goal for the author. Indeed, advice on producing āreadableā or āunderstandableā documents is often included in courses on requirements engineering. However, few researchers, particularly within the software engineering domain, have attempted either to define or to understand the nature of comprehension and itās implications for guidance on the production of quality requirements.
Therefore, this paper examines thoroughly the nature of textual comprehension, drawing heavily from research in discourse process, and suggests some implications for requirements (and other) software documentation. In essence, we find that the guidance on writing requirements, often prevalent within software engineering, may be based upon assumptions which are an oversimplification of the nature of comprehension. Hence, the paper examines guidelines which have been proposed, in this case for use case descriptions, and the extent to which they agree with discourse process theory; before suggesting refinements to the guidelines which attempt to utilise lessons learned from our richer understanding of the underlying discourse process theory. For example, we suggest subtly different sets of writing guidelines for the different tasks of requirements, specification and design
- ā¦