• Refine Query
  • Source
  • Publication year
  • to
  • Language
  • 7
  • 3
  • Tagged with
  • 10
  • 10
  • 10
  • 10
  • 6
  • 4
  • 3
  • 3
  • 3
  • 3
  • 3
  • 2
  • 2
  • 2
  • 2
  • 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.
1

Developing a strategic IS plan for the Cherry Creek Sneak

Bass, Stephanie Kay January 2006 (has links) (PDF)
Thesis (M.S.C.I.T.)--Regis University, Denver, Colo., 2006. / "December 2005"--T.p. Title from PDF title page (viewed on Aug. 30, 2006). Includes bibliographical references.
2

A Decision Support System for Sprint Planning in Scrum Practice

Unknown Date (has links)
Scrum is one of the Agile software development processes broadly adopted in industry. Scrum promotes frequent customer involvements and incremental short release. Sprint planning is a critical step in Scrum that sets up next release goals and lays out plans to achieve those goals. This thesis presents a Sprint Planning dEcision Support System (SPESS) which is a tool to assist the managers for Sprint planning. Among considering other Sprint planning factors, SPESS takes into consideration developer competency, developer seniority and task dependency. The results are that the assignments of the tasks of each Sprint to developers guarantee that each team member contributes to their fullest potential, and project planning is optimized for the shortest possible time. Keywords—Scrum, Sprint planning, planning poker, competence, task dependence, Hungarian algorithm, Essence. / Includes bibliography. / Thesis (M.S.)--Florida Atlantic University, 2018. / FAU Electronic Theses and Dissertations Collection
3

The scrum process for independent programmers

Srirangarajan, Ananth. Lall, Pradeep, Umphress, David A., January 2009 (has links)
Thesis--Auburn University, 2009. / Abstract. Includes bibliographical references (p. 39-41).
4

INTEGRATING DESIGN THINKING MODEL AND ITEMS PRIORITIZATION DECISION SUPPORT SYSTEMS INTO REQUIREMENTS MANAGEMENT IN SCRUM

Unknown Date (has links)
The Agile methodologies have attracted the software development industry's attention due to their capability to overcome the limitations of the traditional software development approaches and to cope with increasing complexity in system development. Scrum is one of the Agile software development processes broadly adopted by industry. Scrum promotes frequent customer involvement and incremental short releases. Despite its popular use, Scrum’s requirements engineering stage is inadequately defined which can lead to increase development time and cost, along with low quality or failure for the end products. This research shows the importance of activity planning of requirements engineering in improving the product quality, cost, and scheduling as well as it points out some drawbacks of Agile practices and available solutions. To improve the Scrum requirements engineering by overcoming its challenges in cases, such as providing a comprehensive understanding of the customer’s needs and addressing the effects of the challenges in other cases, such as frequent changes of requirements, the Design Thinking model is integrated into the Scrum framework in the context of requirements engineering management. The use of the Design Thinking model, in the context of requirements engineering management, is validated through an in-depth scientific study of the IBM Design Thinking framework. In addition, this research presents an Items Prioritization dEcision Support System (IPESS) which is a tool to assist the Product Owners for requirements prioritization. IPESS is built on information collected in the Design Thinking model. The IPESS tool adopts Analytic Hierarchy Process (AHP) technique and PageRank algorithm to deal with the specified factors and to achieve the optimal order for requirements items based on the prioritization score. IPESS is a flexible and comprehensive tool that focuses on different important aspects including customer satisfaction and product quality. The IPESS tool is validated through an experiment that was conducted in a real-world project / Includes bibliography. / Dissertation (PhD)--Florida Atlantic University, 2021. / FAU Electronic Theses and Dissertations Collection
5

Startup Kaizen: uma metodologia ágil para desenvolvimento de software em startups / Startup Kaizen: an agile methodology for software development startups

Leonessa, Nathália Maria Rapuano de Lira Novaes 12 December 2016 (has links)
Submitted by Milena Rubi (milenarubi@ufscar.br) on 2017-06-01T14:03:52Z No. of bitstreams: 1 LEONESSA_Nathalia_2016.pdf: 56993911 bytes, checksum: c3674f0762a44d85df19038a13d9f2d2 (MD5) / Approved for entry into archive by Milena Rubi (milenarubi@ufscar.br) on 2017-06-01T14:14:25Z (GMT) No. of bitstreams: 1 LEONESSA_Nathalia_2016.pdf: 56993911 bytes, checksum: c3674f0762a44d85df19038a13d9f2d2 (MD5) / Approved for entry into archive by Milena Rubi (milenarubi@ufscar.br) on 2017-06-01T14:14:33Z (GMT) No. of bitstreams: 1 LEONESSA_Nathalia_2016.pdf: 56993911 bytes, checksum: c3674f0762a44d85df19038a13d9f2d2 (MD5) / Made available in DSpace on 2017-06-01T14:14:40Z (GMT). No. of bitstreams: 1 LEONESSA_Nathalia_2016.pdf: 56993911 bytes, checksum: c3674f0762a44d85df19038a13d9f2d2 (MD5) Previous issue date: 2016-12-12 / Coordenação de Aperfeiçoamento de Pessoal de Nível Superior (CAPES) / The methodologies currently used by startups for market discovery and software development focus on a more agile and fast development, aiming to obtain learning about the potential market. Often, these methodologies set aside good software development practices to make the process faster and more dynamic, with constant end-user participation. If, on the one hand, the use of methodologies such as Scrum and RUP for software development can result in the development of technological solutions that are not used by users due to the lack of participation in software construction, on the other hand, they bring many benefits when it comes to project management and software quality. In contrast, the opposite occurs to the methodologies and tools currently used by startups, such as Lean Startup, Customer Development, Thinking Design and Business Model Canvas. These methodologies and tools focus on the discovery and validation of the market, without concern for the final quality of the product developed for the client, impacting directly. This impact can also be a waste of time in developing a product that no one will be able to use because of the large number of failures or even it never be finalized due to management problems. The lack of concern for good management of a development project, and its final quality, can do as much damage as the lack of approximation with the potential client. Moreover, in an environment of extreme uncertainty, unknown variables should be reduced in order to achieve overall development success, not just business models. The use of good Software Engineering practices may allow obtaining more information and technical data about the solution developed, which directly impact the user. This information can be used as a basis for decision making, thereby reducing risks related to final product quality and project management, making it easier for potential customers to use, and leaner development. In this sense, this work proposes a software development methodology for startups, Startup Kaizen (SK). SK integrates good practices of methodologies such as RUP and Scrum with methodologies focused on validation and market discovery, such as Lean Startup, Customer Development, Thinking Design and Business Model Canvas. This union of good software engineering practices with market discovery aims to minimize the risk variables for the creation of a new company, whether related to market or management and software quality. After the creation of Startup Kaizen, a case study was performed with its application with graduate students in Computer Science at the Federal University of São Carlos in Sorocaba. This application allowed the data collection to analyze the results in the form of a case study. / As metodologias atualmente utilizadas por startups para descoberta de mercado e desenvolvimento de software focam no desenvolvimento mais ágil e rápido, visando a obtenção de aprendizado sobre o mercado de atuação. Muitas vezes, essas metodologias deixam de lado boas práticas de desenvolvimento de software para que ele seja realizado de forma mais dinâmica e rápida, com constante participação do usuário final. Se, por um lado, a utilização de metodologias ágeis como Scrum e metodologias mais tradicionais como RUP, para o desenvolvimento de software pode resultar no desenvolvimento de soluções tecnológicas que não são utilizadas pelos usuários por falta de uma constante participação deles na construção do software, por outro lado, elas trazem inúmeros benefícios quando se trata de gerenciamento de projeto e qualidade de software. Em contrapartida, o oposto ocorre para as metodologias e ferramentas atualmente utilizadas por startups, tais como Lean Startup, Customer Development, Design Thinking e Business Model Canvas. Essas metodologias e ferramentas focam na descoberta e validação de mercado, sem a preocupação com a qualidade final do produto desenvolvido para o cliente, impactando-o diretamente. Esse impacto pode também acarretar um desperdício de tempo no desenvolvimento de um produto que ninguém conseguirá utilizar, devido à grande quantidade de falhas, ou até que nunca será finalizado, devido a problemas de gerenciamento. A falta de preocupação com um bom gerenciamento de um projeto de desenvolvimento, e sua qualidade final, podem trazer tantos prejuízos quanto a falta de aproximação com o potencial cliente. Além disso, no ambiente de extrema incerteza, as variáveis de insegurança devem ser reduzidas ao máximo possível visando a obtenção de sucesso no desenvolvimento como todo, e não apenas em relação a modelos de negócios. A utilização de boas práticas de engenharia de software pode possibilitar a obtenção de mais informações e dados técnicos sobre a solução desenvolvida, que impactam diretamente o usuário. Essas informações podem ser utilizadas como base na tomada de decisão, diminuindo assim, os riscos relacionadas a qualidade final do produto e gerenciamento de projeto, facilitando a utilização por seus potenciais clientes, além de um desenvolvimento mais enxuto. Neste sentido, este trabalho propõe uma metodologia de desenvolvimento de software para startups, o Startup Kaizen (SK). O SK agrega boas práticas de metodologias como RUP e Scrum com metodologias com foco na validação e descoberta de mercado, como Lean Startup, Customer Development, Design Thinking e Business Model Canvas. Essa união de boas práticas de engenharia de software com a descoberta de mercado, tem como objetivo minimizar as variáveis de risco para a criação de uma nova empresa, sejam elas relacionadas a mercado ou gerenciamento e qualidade de software. Após a criação do Startup Kaizen, foi realizado um estudo de caso com sua aplicação com alunos de pós-graduação em Ciências da Computação da Universidade Federal de São Carlos em Sorocaba. Essa aplicação permitiu a coleta de dados para análise dos resultados na forma de estudo de caso. / 33001014
6

Melhoria da comunicação no desenvolvimento distribuído de software baseado em Scrum / Improved communication in distributed software development based on Scrum

Santos, Leonardo Sanches dos 20 July 2016 (has links)
O desenvolvimento de software entre equipes geograficamente distribuídas tem adquirido relevância devido a interesses das organizações, relacionados a custos de projetos, busca de profissionais multidisciplinares e especializados ou visando ampliar a cobertura de seus clientes, atendendo-os de forma mais globalizada. Porém, apesar dos benefícios existentes, há algumas dificuldades oriundas da distribuição de equipes que são inerentes da dispersão temporal e geográfica. Estas dificuldades incluem as diferenças culturais, linguísticas, temporais entre outras, que comprometem a qualidade da comunicação e consequentemente interferem na compreensão mútua entre as equipes que desenvolvem um mesmo projeto de software. O objetivo deste trabalho é apresentar uma melhoria de um processo de desenvolvimento distribuído de software (DDS), baseado em Scrum, capaz de minimizar as interferências e perdas de informações, descentralização de conhecimentos em pessoas específicas e melhorar no fluxo de comunicação e disseminação das informações. Um caso real foi abordado e para o desenvolvimento deste trabalho o método de pesquisa adotado foi a pesquisa-ação. Neste cenário real haviam problemas originados da comunicação ineficiente entre seus atores e exigiu que o desenvolvimento desta pesquisa tivesse várias iterações e retroalimentações até atingir a maturidade. A melhoria da comunicação foi alcançada e é a principal contribuição deste trabalho. / Software development between geographically distributed teams has acquired relevance due to interests of organizations, project-related costs, looking for multidisciplinary and specialized professionals or aiming to expand the coverage of its customers, serving them in a globalized form. However, despite the existing benefits, there are some difficulties originated from the distribution of teams that are inherent in the temporal and geographic dispersion. These difficulties include the cultural, linguistic, temporal among others, which affect the quality of communication and consequently interfere with the mutual comprehension between the teams which develop the same software project. Thus, the aim of this work is to present an improvement in the process of distributed software development (DSD) based on Scrum, capable to minimize interference and information losses, decentralization of knowledge in specific people and improve the communication flow and dissemination of information. A real case was discussed and as for the development of this work the action research was the approach employed in this study. In this scenario, problems originated from inefficient communication between their actors and demanded that the development of this research present several iterations and feedbacks in order to reach its maturity. Improved communication has been achieved and is the main contribution of this work.
7

Melhoria da comunicação no desenvolvimento distribuído de software baseado em Scrum / Improved communication in distributed software development based on Scrum

Santos, Leonardo Sanches dos 20 July 2016 (has links)
O desenvolvimento de software entre equipes geograficamente distribuídas tem adquirido relevância devido a interesses das organizações, relacionados a custos de projetos, busca de profissionais multidisciplinares e especializados ou visando ampliar a cobertura de seus clientes, atendendo-os de forma mais globalizada. Porém, apesar dos benefícios existentes, há algumas dificuldades oriundas da distribuição de equipes que são inerentes da dispersão temporal e geográfica. Estas dificuldades incluem as diferenças culturais, linguísticas, temporais entre outras, que comprometem a qualidade da comunicação e consequentemente interferem na compreensão mútua entre as equipes que desenvolvem um mesmo projeto de software. O objetivo deste trabalho é apresentar uma melhoria de um processo de desenvolvimento distribuído de software (DDS), baseado em Scrum, capaz de minimizar as interferências e perdas de informações, descentralização de conhecimentos em pessoas específicas e melhorar no fluxo de comunicação e disseminação das informações. Um caso real foi abordado e para o desenvolvimento deste trabalho o método de pesquisa adotado foi a pesquisa-ação. Neste cenário real haviam problemas originados da comunicação ineficiente entre seus atores e exigiu que o desenvolvimento desta pesquisa tivesse várias iterações e retroalimentações até atingir a maturidade. A melhoria da comunicação foi alcançada e é a principal contribuição deste trabalho. / Software development between geographically distributed teams has acquired relevance due to interests of organizations, project-related costs, looking for multidisciplinary and specialized professionals or aiming to expand the coverage of its customers, serving them in a globalized form. However, despite the existing benefits, there are some difficulties originated from the distribution of teams that are inherent in the temporal and geographic dispersion. These difficulties include the cultural, linguistic, temporal among others, which affect the quality of communication and consequently interfere with the mutual comprehension between the teams which develop the same software project. Thus, the aim of this work is to present an improvement in the process of distributed software development (DSD) based on Scrum, capable to minimize interference and information losses, decentralization of knowledge in specific people and improve the communication flow and dissemination of information. A real case was discussed and as for the development of this work the action research was the approach employed in this study. In this scenario, problems originated from inefficient communication between their actors and demanded that the development of this research present several iterations and feedbacks in order to reach its maturity. Improved communication has been achieved and is the main contribution of this work.
8

Factors that contribute significantly to scrum adoption as perceived by scrum practitioners working within South Africa organisations

Hanslo, Ridewaan 05 1900 (has links)
Text in English / Scrum is the most adopted and under-researched Agile methodology. The research conducted on Scrum adoption is mainly qualitative. Therefore, there was a need for a quantitative study to investigate Scrum adoption challenges. The general objective of this study was to investigate the factors that have a significant relationship with Scrum adoption as perceived by Scrum practitioners working within South African organisations. To achieve this objective a narrative review to synthesise the existing challenges was conducted, followed by the use of these challenges in the development of a conceptual framework. After that, a survey questionnaire was used to test and evaluate the developed framework. The research findings indicate that relative advantage, complexity, and sprint management are factors that have a significant linear relationship with Scrum adoption. The findings are generalisable to the population, and the author recommends that organisations review the findings during their adoption phase of Scrum. / Council for Scientific and Industrial Research (CSIR) / University of South Africa (UNISA) / School of Computing / M.Sc. (Computing)
9

Program management practices in context of Scrum : a case study of two South African software development SMMEs

Singh, Alveen January 2015 (has links)
Submitted in fulfilment of the requirements for the degree of Doctor of Technology: Information Technology, Durban University of Technology, Durban, 2015. / Agile approaches have proliferated within the software development arena over the past decade. Derived mainly from Lean manufacturing principles, agile planning and control mechanisms appear minimal and fluid when compared to more traditional software engineering approaches. Scrum ranks among the more popular permutations of agile. Contemporary literature represents a rich source of contributions for agile in areas such as practice guidelines, experience reports, and methodology tailoring; but the vast majority of these publications focus on the individual project level only, leaving much uncertainty and persistent questions in the multi-project space. Questions have recently been raised, by both academics and practitioners alike, concerning the ability of Scrum to scale from the individual project level to the multi-project space. Program management is an area encompassing practice and research areas concerned mainly with harmonizing the existence of competing simultaneous projects. Existing literature on program management essentially perceives projects as endeavours that can be carefully planned at the outset, and controlled in accordance with strong emphasis placed on economic and schedule considerations. This complexion seems to be mostly a result of well-established and ingrained management frameworks like Project Management Institute (PMI), and is largely at odds with emerging practices like Scrum. This disparity represents a gap in the literature and supports the need for deeper exploration. The conduit for this exploration was found in two South African software development small to medium sized enterprises (SMMEs) practicing Scrum. The practical realities and constraints faced by these SMMEs elicited the need for more dynamic program management practices in support of their quest to maximize usage of limited resources. This thesis examines these practices with the aim of providing new insights into the program management discourse in the context of Scrum software development environments. The research approach is qualitative and interpretive in nature. The in-depth exploratory case study research employed the two software SMMEs as units of analysis. Traditional ethnographic techniques were commissioned alongside minimal researcher participation in project activities. Activity Theory honed the data analysis effort and helped to unearth the interrelationships between SMME characteristics, program management practices, and Scrum software development. The results of the data analysis are further refined and fashioned into eleven knowledge areas that represent containers of program management practices. This is the product of thematic analysis of literature and data generated from fieldwork. Seeing as the observed practices were highly dynamic in nature, concept analysis provided a mechanism by which to depict them as snapshots in time. As a theoretical contribution, proposed frameworks were crafted to show how program management practices might be understood in the context of organizations striving towards agile implementation. Furthermore, representations of the mutually influential interfaces of SMME characteristics and Scrum techniques that initiate the observed fluid nature of program management practices, are brought to the fore.
10

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)

Page generated in 0.4016 seconds