• Refine Query
  • Source
  • Publication year
  • to
  • Language
  • 82
  • 15
  • 14
  • 5
  • 2
  • 2
  • 1
  • 1
  • 1
  • 1
  • 1
  • Tagged with
  • 134
  • 134
  • 134
  • 56
  • 47
  • 29
  • 24
  • 23
  • 20
  • 18
  • 18
  • 18
  • 16
  • 15
  • 15
  • About
  • The Global ETD Search service is a free service for researchers to find electronic theses and dissertations. This service is provided by the Networked Digital Library of Theses and Dissertations.
    Our metadata is collected from universities around the world. If you manage a university/consortium/country archive and want to be added, details can be found on the NDLTD website.
61

Riktlinjer for overgangen till distribuerade agila metoder

Zhong, Patrik January 2021 (has links)
Distribuerade agila mjukvaruutvecklings-metoder har aldrig varit mer populärt. Att kunna arbeta hemifrån för att undvika den dagliga pendlingen eller för att samarbeta med utvecklare utomlands har aldrig varit enklare. Tredjepartsverktyg som Zoom och Google Meet förenklar kommunikationsprocessen, och med introduktionen av verktyg som Visual Studio’s “liveshare” som möjliggör realtids-kodning, har agila metoder verkligen flyttat ut från kontoren. Dock är en av de viktigaste komponenterna av att arbeta agilt att arbeta ansikte mot ansikte, vilket innebär att en av de effektivaste metoderna för kommunikation nu förloras när man flyttas till att arbeta med distribuerade metoder. Att övergå till nya metoder är aldrig enkelt, och när företag övergår till en distribuerad framtid kan mjukvaruutvecklare potentiellt drabbas av denna förändring i miljö och metod. Om företag har riktlinjer för övergången till distribuerade metoder kan det potentiellt göra förflyttninen enklare.Problemet är att det inte finns några sådana riktlinjer. Syftet med denna rapport är att skapa riktlinjer med målet att hjälpa organisationer övergå till distribuerade agila metoder från lokala agila metoder. Metoden i denna rapport är en kvalitativ utforskande litteraturstudie tillsammans med utforskande intervjuer som utforskar de positiva och negativa erfarenheterna utvecklare möter när de gör en övergång till distribuerade metoder. Litteraturstudien användes för att formulera forskningskriterierna och intervjufrågorna. Totalt tillfrågades åtta personer som hade erfarenheter av att göra en övergång till distribuerade agila metoder. Dessa intervjuer resulterade i tre generella riktlinjer som kan användas för att förenkla övergången mellan lokala-och distribuerade agila metoder. / Distributed agile software development has never been more popular. Being able to work at home to avoid the commute or simply collaborating with developers abroad has never been easier. Third party tools such as Zoom and Google Meet makes communication easier than ever, and with the introduction of Visual Studio’s live share that enables real-time collaborative coding, distributed agile development truly has moved out of the offices. Yet, one of the core components of the agile working method is working face to face, meaning that one of the most efficient methods of communication is lost upon moving development into a distributed setting. Transitions towards new methods and settings are never easy, and as companies transition towards a remote and distributed future, software developers are potentially burdened by this change in environment. If companies had access to guidelines they could potentially experience a smoother transition. The problem is that there currently do not exist such guidelines. The purpose of this report is to create such guidelines with the goal of helping organizations transition towards distributed agile methods. In this report, the method utilized is a qualitative and explorative literature study, coupled with interviews aimed to explore the positive and negative experiences developers face when transitioning towards distributed methods. A literature study was used to help formulate the research criteria and the interview questions. In total, eight people that had experienced a recent transition towards distributed agile methods were interviewed. These interviews resulted in three general guidelines that can be used to ease the transition between a local and distributed work environment.
62

Software Development Efficiency A Case Study in a Mobil Payment Company

Hassan, Shah, Kaka Khel, Muhammad Noman January 2019 (has links)
Due to Internet, the IT industry have seen rapid changes and to compete in the digital work, the organizations need more vigilance than ever before to respond to market changes and customer needs. Some organizations have opted to go agile to be more efficient in their software development but still deploying agile methodology and reaping its fruits further needs more research and empirical evidence.This research is a case study to evaluate the deployment of agile methodology in Easypark and explore its efficiency focusing on their structure and organization. Certain criterions are chosen to evaluate software development efficiency against that and to analyse what the deployment in the organization has led to.The method chosen for this study is a case study, where the empirical data is gathered through semi structured, and qualitative interviews from five senior employees in Easypark. The responses were analysed and reviewed under the light of theoretical background to elaborate the research question.The results of this case study revealed that efficiency in general have greatly been improved after adopting agile methods in Easypark and the core contributor is the permanent teams for different projects. There have been quite a few complications to deploy agile and that must be taken into consideration when other organizations plan to adopt agile methodologies.
63

Modelling the critical success factors of agile software development projects in South Africa

Chiyangwa, Tawanda Blessing 01 1900 (has links)
There are several critical success factors suggested for why agile software development projects succeed, including organisational and process factors. Although there are an increasing number of identified critical success factors, IT professionals lack the modelling techniques and the theoretical framework to help them meaningfully understand their influences. To solve this problem, this study developed a model by employing the following theories: Theory of Reasoned Action (TRA), Theory of Planned Behaviour (TPB), and Unified Theory of Acceptance and Use of Technology (UTAUT) to create a fit model for agile software development projects. The research sought to answer the question: What are the critical success factors that influence the success of agile software development projects? The literature review considers the continued failure of agile and traditional software development projects which have led to the consideration of, and dispute over, critical success factors — the aspects most vital to a methodology’s success. Though TRA, TPB and UTAUT have previously been applied to agile methodologies, empirical models have not been completely integrated to develop a fit model. This research sought to fill this gap. Data was collected in South Africa through a web-based survey using structured questionnaires and an interview guide. Face-to-face interviews were done to identify the critical success factors in agile projects. The data was captured and analysed for descriptive statistics, convergent and discriminant validity, composite and internal reliability, and correlation in order to inform the structural equation modelling (SEM). SEM was used to test the research model and hypotheses to answer the research questions. The results informed development of a comprehensive model that could provide guidelines to the agile community. The study contributes towards understanding the critical success factors for agile projects. It examined direct, indirect and moderating effects, and the findings contribute towards developing a framework to be used by agile professionals. These key result shows that organisational factors have a great influence on performance expectancy characteristics. To ensure success of agile projects, managers are advised to focus on the effect of the organisation’s environment, culture and policies on performance and effort expectancy. / School of Computing / Ph. D. (Computer Science)
64

Development of a framework to understand the factors that influence software productivity in agile teams

Nzou, Viola 10 1900 (has links)
Productivity improvement in the software industry is one of the major challenges facing many software development companies in this century. Most companies have adopted agile methodologies in order to profit from the benefits claimed for them. Agile methodologies are characterised by frequent software delivery, short feedback loops, quicker response to change, and problem identification earlier in the development process. The agile approach has been recognised as paving a way for companies to acquire higher software productivity, delivering good-quality and cost-effective software, enabling software development companies to respond to business challenges with their demands for high quality, high performance and high development speed in delivering the final product. For companies that adopt agile methodologies, understanding the factors that influence their teams’ software development productivity is a challenging task for management and practitioners today. In this research, an analysis is presented that identifies productivity factors that affect agile teams. It is a study of agile methods to identify common agile practices and/or values that have impact on productivity, and describes suitable metrics that could be used to measure agile team productivity. A qualitative research approach was used, and the case study was chosen as the research strategy. Two South African companies that are located in two different provinces and that adopted agile methodologies in their software development, were selected for the case studies. Qualitative content analysis was used in the research to permit subjective interpretation of factors that influence agile team productivity, and to analyse to what extent these factors affected productivity. This research has shown that an understanding of the factors that influence an agile team’s productivity gives significant insight into the way agile teams work, motivates team members to work together, and leads to uniform metrics in tracking each team’s progress. The study indicates that tracking an agile team’s work and providing adequate tools needed to execute their tasks results in improving agile team productivity. It should be recognised that using metrics to measure performance in agile teams is helpful in creating a team’s culture and trust. In this study, it was found that the factors identified in both literature and case studies affected productivity in the two companies under study, both positively and negatively. The study also found that applying the correct metrics in assessing, analysing and reviewing an agile team’s performance is important when monitoring productivity. Successful software delivery is only possible if individuals are committed to their work, are provided with the necessary tools and have access to a stable working environment. In addition, individual factors such as knowledge, skills, abilities, personalities and experience should be considered when forming agile teams. Consideration of these factors will result in grouping people that are able to work together and achieve a common goal, which is important in improving productivity. A conceptual framework for agile team productivity was proposed. The discussion of the findings is presented in more detail in this research. / School of Computing / M.Sc. (Computing)
65

Exploring issues in agile requirements engineering in the South African industry

Sebega, Yanda 01 1900 (has links)
The agile manifesto has certainly changed the way software is produced in the Information Communications Technology (ICT) industry. However, many persistent challenges cripple agile software development. One challenge is that the constant change in technology makes the requirements hard to implement. Another is that issues of the agile requirements engineering (ARE) process are abundant and pervasive throughout software projects. The aim of this study is to determine common issues in agile requirements engineering in the South African software industry and identify tools and frameworks to mitigate risks emanating from such problems. This includes finding out how much value software practitioners put in the agile principles. This study was essentially quantitative, based on a cross-sectional survey. Self-administered questionnaires were used to collect required data which was then subjected to exploratory data analysis using SPSS (Statistical Package for the Social Sciences), a tool for statistical analysis. The results show that software practitioners have a strong penchant for principles of the Agile Manifesto. Major issues in agile requirements engineering include lack of proper validation tools and techniques, scope problems, lack of proper documentation, issues of prioritisation, as well as unavailability of customer representative. A detailed baseline of issues in agile requirements engineering was created along with a set of recommended tools and techniques used in the software industry. As for the recommendation, it is suggested that companies invest more on validation tools and techniques and consider non-functional requirements integration during software development. / School of Computing / M. Sc. (Computing)
66

Recommendations for improvement to the South African information technology curriculum: a case study of new higher certificate graduates' first year of employment

Panday, Annelee 05 1900 (has links)
Employment issues in South Africa (SA) are a significant problem. There are ongoing discussions revolving around the employability challenges facing South African graduates, particularly in the Information Technology (IT) sector. The preparedness of these IT graduates has been questioned with many looking towards skill sets and employability status while others have scrutinised the validity of the IT curriculum meeting industry needs. The research focuses on a case study of graduates from an accredited, private higher education institution in SA. The study followed a qualitative approach using questionnaires and interviews to understand the experiences of employers, employed graduates and recruitment personnel upon employment of the graduates. This study investigated, determined and confirmed recommendations to adapt the South African higher education IT curriculum to improve the productivity of IT graduates upon employment. / School of Computing / M. Sc. (Computing)
67

Η μεθοδολογία SCRUM και η εφαρμογή της στην ανάπτυξη πληροφοριακών συστημάτων

Ρηγοπούλου, Μαρία 05 February 2015 (has links)
Είναι γεγονός ότι το οικονομικό περιβάλλον του αιώνα που διανύουμε χαρακτηρίζεται από τον έντονο ανταγωνισμό και την ταχύτητα με την οποία εξελίσσονται, όχι μόνο η τεχνολογία και η επιστημονική γνώση, αλλά και αυτά καθαυτά τα συστήματα παραγωγής, διακίνησης και προώθησης στον πελάτη, ποιοτικών προϊόντων και υπηρεσιών. Άμεση συνέπεια των παραπάνω είναι αφενός η αύξηση της αβεβαιότητας των επιχειρήσεων, ως προς το στρατηγικό τους προσανατολισμό, και αφετέρου η αύξηση της πολυπλοκότητας σε κάθε διάσταση της σύγχρονης επιχείρησης (προϊόν, σύστημα παραγωγής, προγραμματισμός, δίκτυο προμηθευτών κλπ). Οι παραπάνω συνθήκες έχουν δημιουργήσει την ανάγκη για την εφαρμογή συστημάτων διοίκησης που να αναγνωρίζουν τη φύση της επιχείρησης του 21ου αιώνα και να προσεγγίζουν ολιστικά το σύνολο των παραμέτρων που δύναται να επιφέρουν ανταγωνιστικό πλεονέκτημα. / In contemporary software development projects companies are facing challenges, such as constantly changing requirements, pressure to deliver faster, and the need to cut costs due to competition. This leads to the increasing uncertainty in companies and to the increasing complexity in all aspects of modern business (product, production system, programming, network providers, etc.). In an attempt to deal with these challenges new methods evolved, which became known as agile project management and agile software development. The agile approach aims to produce high quality software products faster, to create more value and to satisfy customers’ needs better.
68

Tool Support For Distributed Agile Software Development

Usta, Ahsen Serkan 01 May 2006 (has links) (PDF)
Agile Software Development has gained popularity with their people centric view and their common practices for developing software in today&rsquo / s volatile business world where change on requirements is unavoidable. However / the efficiency of the project depends on the communication and the collaboration of the team, which are supported by the co-location of the team. But in some cases colocation of the team cannot be realized, thus agile processes should also support distributed teams. This point was observed by Kircher, Jain, Corsaro, and Levine [31] and they suggested Distributed eXtreme Programming (DXP) after they prepared a study using offthe- shelf software products in order to replace the effect of face-toface communication on the efficiency of the application of agile processes with the aid gathered from tool support. In this study some available tool support for distributed agile software development is investigated and a tool is developed and presented in order to support software configuration management as well as increasing collaboration and communication of the team. The tool is then evaluated from a user&rsquo / s perspective and it is compared with some available software configuration management tools.
69

Inter-team knowledge sharing : A case study on co-located teams’ drivers and barriers for KS

Dahlqvist, Maria, Forsberg, Jacqueline January 2018 (has links)
Agile software development is a high-technology environment with several challenges. One of these is how to manage knowledge. Knowledge sharing is an important part of software development and is supported in agile practices, but mainly within teams, and not between teams. There is much research done about knowledge sharing within teams and a current trend is to research knowledge sharing in globally distributed teams. However, there’s little research about knowledge sharing between co-located teams, and what barriers and drivers exist. We conducted a case study within an IT-company with four co-located development teams to answer the research question: What are the drivers and barriers for knowledge sharing between co-located agile software development teams and how do they relate to different contexts.  Ten semi-structured interviews and one focus group was conducted and analyzed by using thematic analysis. This analysis constructed 6 themes, where 15 drivers and 21 barriers were identified. We contribute to the research field by presenting these barriers and drivers and show which barriers and drivers that exist in several contexts. We also relate our findings to other research. By our findings we also contribute to practitioners to understand when forming inter-team strategies for KS there is not only one way to success, but strategies need to be formed in several levels of organization.
70

Revealing the secret pieces of the puzzle : Studying the hidden influences of agile development context on user-centered design

Laanpere, Jaak January 2018 (has links)
In a world dominated by digital technologies, user-centered design aims to ensure that the users are catered with solutions that deal with their needs. As agile methods have become a prevalent approach in software development, it is crucial for the two disciplines to work together. However, existing studies have already presented incompatibilities between the methods of the two disciplines. This study intends to investigate the impact that agile principles have on the adoption of user-centered approach on a broader scale through the many parties involved in the process. By conducting interviews with practitioners and interpreting the results through the lens of Engeström’s activity system model, the findings of the study reveal significant influences imposed on the user-centered approach by external and organizational factors that are intensified by the agile principles. Three main areas of concern are identified and accompanied by broad suggestions on how to approach resolving them, focusing on the empowerment of UX designers, accurate deliberation of the intentions and practices of user-centered approach, and close collaboration to raise awareness of the benefits of user-centered approach. Lastly, it is emphasized that the identified areas of concern – primarily the problematic impact from clients and executives – need further extensive research to provide definitive solutions.

Page generated in 0.0947 seconds