23,795 research outputs found
Beyond Surveys: Analyzing Software Development Artifacts to Assess Teaching Efforts
This Innovative Practice Full Paper presents an approach of using software
development artifacts to gauge student behavior and the effectiveness of
changes to curriculum design. There is an ongoing need to adapt university
courses to changing requirements and shifts in industry. As an educator it is
therefore vital to have access to methods, with which to ascertain the effects
of curriculum design changes. In this paper, we present our approach of
analyzing software repositories in order to gauge student behavior during
project work. We evaluate this approach in a case study of a university
undergraduate software development course teaching agile development
methodologies. Surveys revealed positive attitudes towards the course and the
change of employed development methodology from Scrum to Kanban. However,
surveys were not usable to ascertain the degree to which students had adapted
their workflows and whether they had done so in accordance with course goals.
Therefore, we analyzed students' software repository data, which represents
information that can be collected by educators to reveal insights into learning
successes and detailed student behavior. We analyze the software repositories
created during the last five courses, and evaluate differences in workflows
between Kanban and Scrum usage
Project Success in Agile Development Projects
The paper explains and clarifies the differences between Waterfall and Agile
development methodologies, establishes what criteria could be taken into
account to properly define project success within the scope of software
development projects, and finally tries to clarify if project success is the
reason why many organizations are moving to Agile methodologies from other ones
such as Waterfall. In the form of a literature review, it analyses several,
publications, investigations and case studies that point out the motives why
companies moved to Agile, as well as the results they observed afterward. It
also analyses overall statistics of project outcomes after companies evolved
from traditional methodologies such as Waterfall to Agile development
approaches
Psychological Safety and Norm Clarity in Software Engineering Teams
In the software engineering industry today, companies primarily conduct their
work in teams. To increase organizational productivity, it is thus crucial to
know the factors that affect team effectiveness. Two team-related concepts that
have gained prominence lately are psychological safety and team norms. Still,
few studies exist that explore these in a software engineering context.
Therefore, with the aim of extending the knowledge of these concepts, we
examined if psychological safety and team norm clarity associate positively
with software developers' self-assessed team performance and job satisfaction,
two important elements of effectiveness.
We collected industry survey data from practitioners (N = 217) in 38
development teams working for five different organizations. The result of
multiple linear regression analyses indicates that both psychological safety
and team norm clarity predict team members' self-assessed performance and job
satisfaction. The findings also suggest that clarity of norms is a stronger
(30\% and 71\% stronger, respectively) predictor than psychological safety.
This research highlights the need to examine, in more detail, the
relationship between social norms and software development. The findings of
this study could serve as an empirical baseline for such, future work.Comment: Submitted to CHASE'201
Comparative Study on Agile software development methodologies
Today-s business environment is very much dynamic, and organisations are
constantly changing their software requirements to adjust with new environment.
They also demand for fast delivery of software products as well as for
accepting changing requirements. In this aspect, traditional plan-driven
developments fail to meet up these requirements. Though traditional software
development methodologies, such as life cycle-based structured and object
oriented approaches, continue to dominate the systems development few decades
and much research has done in traditional methodologies, Agile software
development brings its own set of novel challenges that must be addressed to
satisfy the customer through early and continuous delivery of the valuable
software. It is a set of software development methods based on iterative and
incremental development process, where requirements and development evolve
through collaboration between self-organizing, cross-functional teams that
allows rapid delivery of high quality software to meet customer needs and also
accommodate changes in the requirements. In this paper, we significantly
identify and describe the major factors, that Agile development approach
improves software development process to meet the rapid changing business
environments. We also provide a brief comparison of agile development
methodologies with traditional systems development methodologies, and discuss
current state of adopting agile methodologies. We speculate that from the need
to satisfy the customer through early and continuous delivery of the valuable
software, Agile software development is emerged as an alternative to
traditional plan-based software development methods. The purpose of this paper,
is to provide an in-depth understanding, the major benefits of agile
development approach to software development industry, as well as provide a
comparison study report of ASDM over TSDM.Comment: 25 pages, 25 images, 86 references used, with authors biographie
Управління міжнародним бізнесом: Agility Journey для високотехнологічних компаній
The purpose of the article is the development of recommendations for the business maturity determination and measurement in the implementation of the agile approach for high-tech companies. Methods of analysis of documents, observation, personal and in-depth interviews, case studies have been used in the research.
The findings of the research: Business Agility Journey has been suggested for defining the state of the maturity of the company and conducting express diagnostics of agility. Agile Project Management Journey has been developed for the identification of weaknesses by the companies in the path to agility, as well as for
the determination of events for the transition from the traditional to the agile approach. Personal Agility Checklist has been designed for testing the soft skills of employees for the presence of the agile mindset. Research limitations include the study of the maturity of companies in the IT industry. Practical implications
are based on the use of suggested Agility Journeys in defining the state of maturity and main problems on the transition path. Also, Personal Agility Checklist will help to check the agility of the future employees. The originality of the article is based on the uniqueness of the Agility Journey that has been developed for the
first time. Further research on this topic should be focused on the development of an agile mindset as a prerequisite for the provision of agility in the company.Метою статті є розробка рекомендацій щодо визначення та вимірювання зрілості бізнесу при впровадженні еджайл-підходу для високотехнологічних компаній. У дослідженні використовуються методи аналізу документів, спостереження, особистого та глибинного інтерв’ю та кейс-стаді. Розроблено Business Agility Journey для визначення стану зрілості компанії та проведення експрес-діагностики еджайльності. Agile Project Management Journey було розроблено для визначення компаніями своїх слабких сторін, а також заходів для переходу від традиційного до еджайльного підходу. Personal Agility Checklist був створений для перевірки «гнучких навичок» (soft skills) співробітників на наявність гнучкого мислення (agile mindset). Обмеження досліджень включають вивчення зрілості компаній ІТ-галузі. Практична значущість ґрунтується на використанні запропонованих Agility Journeys для визначення стану зрілості та основних проблем на шляху переходу. Також Personal Agility Checklist допоможе перевірити еджайльність майбутніх працівників. Оригінальність статті базується на унікальності Agility Journey, яка була розроблена вперше. Подальші дослідження на цю тему доцільно зосередити на розвитку гнучкого мислення як передумови забезпечення еджайльності в компанії
Business Value Is not only Dollars - Results from Case Study Research on Agile Software Projects
Business value is a key concept in agile software development. This paper presents results of a case study on how business value and its creation is perceived in the context of agile projects. Our overall conclusion is that the project participants almost never use an explicit and structured approach to guide the value creation throughout the project. Still, the application of agile methods in the studied cases leads to satisfied clients. An interesting result of the study represents the fact that the agile process of many projects differs significantly from what is described in the agile practitioners’ books as best practices. The key implication for research and practice is that we have an incentive to pursue the study of value creation in agile projects and to complement it by providing guidelines for better client’s involvement, as well as by developing structured methods that will enhance the value-creation in a project
Misaligned Values in Software Engineering Organizations
The values of software organizations are crucial for achieving high
performance; in particular, agile development approaches emphasize their
importance. Researchers have thus far often assumed that a specific set of
values, compatible with the development methodologies, must be adopted
homogeneously throughout the company. It is not clear, however, to what extent
such assumptions are accurate.
Preliminary findings have highlighted the misalignment of values between
groups as a source of problems when engineers discuss their challenges.
Therefore, in this study, we examine how discrepancies in values between groups
affect software companies' performance.
To meet our objectives, we chose a mixed method research design. First, we
collected qualitative data by interviewing fourteen (\textit{N} = 14) employees
working in four different organizations and processed it using thematic
analysis. We then surveyed seven organizations (\textit{N} = 184). Our analysis
indicated that value misalignment between groups is related to organizational
performance. The aligned companies were more effective, more satisfied, had
higher trust, and fewer conflicts.
Our efforts provide encouraging findings in a critical software engineering
research area. They can help to explain why some companies are more efficient
than others and, thus, point the way to interventions to address organizational
challenges.Comment: accepted for publication in Journal of Software: Evolution and
Proces
- …