Дисертації з теми "SCRM process"
Щоб переглянути інші типи публікацій з цієї теми, перейдіть за посиланням: SCRM process.
Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями
Ознайомтеся з топ-50 дисертацій для дослідження на тему "SCRM process".
Біля кожної праці в переліку літератури доступна кнопка «Додати до бібліографії». Скористайтеся нею – і ми автоматично оформимо бібліографічне посилання на обрану працю в потрібному вам стилі цитування: APA, MLA, «Гарвард», «Чикаго», «Ванкувер» тощо.
Також ви можете завантажити повний текст наукової публікації у форматі «.pdf» та прочитати онлайн анотацію до роботи, якщо відповідні параметри наявні в метаданих.
Переглядайте дисертації для різних дисциплін та оформлюйте правильно вашу бібліографію.
1
Wiss, Gullberg Ellen, and Alison Karlsson. "SCRM-processen i byggkeramikbranschen : Innan och under COVID-19 och framåt." Thesis, Linnéuniversitetet, Institutionen för ekonomistyrning och logistik (ELO), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-104983.
Анотація:
Titel: SCRM-processen i byggkeramikbranschen: innan och under COVID-19 och framåt Författare: Alison Karlsson & Ellen Wiss Gullberg Examinator: Peter Berling Handledare: Helena Forslund Bakgrund: Byggkeramikbranschen har visat sig vara en ostuderad bransch med flera litteraturgap, bland annat i relation till SCRM-processen och till COVID-19 pandemin. Syfte: Att genomföra en fallstudie av hur försörjningskedjor i byggkeramikbranschen har arbetat med SCRM-processen innan och under COVID-19 pandemin, samt att skapa en SCRM-process som är specificerad för byggkeramikbranschen. Frågeställningar: Hur har arbetet med SCRM-processen sett ut i återförsäljarens försörjningskedjor innan och under COVID-19 pandemin? Hur skulle en SCRM-process specificerad för byggkeramikbranschen se ut? Genomförande: Genom intervjuer med respondenter från flera aktörer i återförsäljarens försörjningskedjor samlades empiri så att arbetet med SCRM-processen innan och under COVID-19 pandemin kunde kartläggas. Empiri samlades även in från en branschexpert och från försörjningskedjornas aktörer till den andra frågeställningen. Därefter gjordes förslag till en sårbarhetskarta, en riskbedömningsmatris och en riskhanteringsmatris för byggkeramikbranschen, som slutligen sammanfattades till en SCRM-process specificerad för byggkeramikbranschen. Slutsats: Arbetet med SCRM-processen innan COVID-19 tycks inte ha skett i återförsäljarens försörjningskedjor, men alla studerade aktörer har använt sig av SCRM-processen i olika mån under COVID-19, varav återförsäljaren har arbetat mest och leverantörerna arbetat minst med SCRM-processen. En SCRM-process specificerad för byggkeramikbranschen har skapats och har sammanfattats både i text och i figur, där specifika verktyg och branschspecifika aspekter har rekommenderats. Nyckelord: SCRM-process, byggkeramikbranschen, byggkeramik, COVID-19.Title: The SCRM process in the ceramic tiles business: before and during COVID-19 and forward Researchers: Alison Karlsson & Ellen Wiss Gullberg Examinator: Peter Berling Supervisor: Helena Forslund Background: The ceramic tiles business has turned out to be an unstudied business with many literature gaps, among others in relation to the SCRM process and to the COVID-19 pandemic. Purpose: To do a case study of how supply chains in the ceramic tiles business have worked with the SCRM process before and during the COVID-19 pandemic, and to create a SCRM process that is specified for the ceramic tiles business. Research questions: How has the work with the SCRM process looked like in the reseller’s supply chains before and during the COVID-19 pandemic? What could a SCRM process specified for the ceramic tiles business look like? Method: Through interviews with respondents from many of the actors in the reseller’s supply chains, empirical data was collected so that the work with the SCRM process before and during the COVID-19 pandemic could be mapped. Empirical data was also collected from a business expert and from the supply chain actors to the second research question. Thereafter a suggestion for a supply chain vulnerability map, a risk assessment matrix and a risk handling matrix for the ceramic tiles business was created, which was finally summarized to a SCRM process specified for the ceramic tiles business. Conclusion: The work with the SCRM process before COVID-19 seems to have not existed in the reseller’s supply chains, but all of the actors of the supply chains that were studied have used the SCRM process in different degrees during COVID-19, where the reseller has worked the most and the suppliers have worked the least with the SCRM process. A SCRM process specified for the ceramic tiles business has been created and has been summarized both in text and in figure, where specific tools and business specific aspects have been recommended. Keywords: SCRM process, ceramic tiles business, ceramic tiles, COVID-19.
2
Krbušek, Adam. "Použití metodiky SCRUM v inovačním procesu firmy." Master's thesis, Vysoká škola ekonomická v Praze, 2015. http://www.nusl.cz/ntk/nusl-261990.
Анотація:
Diploma thesis deals with SCRUM methodology and its uses in innovation management. The main objective of the thesis is creation of a specific framework which will enable to use SCRUM methodology in the innovation process. The thesis is divided into three parts. The first part presents theoretical framework important for the main research. This part contains literature review and research dedicated to the SCRUM methodology and innovation process. The second part of the thesis deals with mapping of the SCRUM methodology to Hladik's innovation process. This part also contains own design of the innovation management process. The third part of the thesis is dedicated to the case study. The case study uses described innovation management process for verification of the hypothesis saying that is possible to use SCRUM methodology in the innovation process. The author's contribution lies in creation of a framework which provides agile alternative to the classical innovation management models.
3
Zhang, Yanpeng, and Ce Zhou. "Introducing Domain Specific Language for Modeling Scrum Projects." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-13328.
Анотація:
Context. A clear software process definition is important because it can help developers to share a common understanding and improve the development effectiveness. However, if the misconceptions or misunderstandings are introduced to the team during the process definition, it will bring numerous uncertain problems to the projects and reduce the productivity. Scrum is one of the most popular Agile development processes. It has been frequently used in software development. But the misunderstanding of usage of the Scrum method always leads to situations where teams cannot achieve the hyper-productivity even failure. Therefore, introducing a reasonable graphical language for describing the Scrum process may help learners to gain a correct and common understanding of the Scrum method. Objectives. In this study, we introduce a graphical Domain Specific Language for modeling the Scrum process and specific Scrum projects. Further, we evaluated the proposed language to figure out if and how this language can help developers learn Scrum method and understand the specific Scrum projects. For the first, we decide to extract the essential elements and their relative relationships of the Scrum process, and based on that, we define and specify the graphical language. After that, we evaluate the proposed graphical language to validate whether this language can be considered as useful to help developers to learn Scrum method and understand the specific Scrum projects. Methods. In order to define the graphical language, we studied and reviewed the literature to extract the essential elements and their relationships for describing the Scrum process. Based on that, we defined and specified the graphical DSL. With the aim of evaluating the proposed graphical language, we performed the experiment and survey method. This experiment was conducted in an educational environment. The subjects were selected from the undergraduate and master students. At the same time, we carried out a survey to capture the developers‘ opinions and suggestions towards the proposed language in order to validate its feasibility. Results. By studying the literature, we listed and specified the essential elements for describing the Scrum process. By executing the experiment, we evaluated the efficiency and effectiveness of learning Scrum in using the proposed language and the natural language. The result indicates that the graphical language is better than the natural language in training Scrum method and understanding specific Scrum projects. The result shows that the proposed language improved the understandability of the Scrum process and specific Scrum projects by more than 30%. We also performed a survey to investigate the potential use of the proposed graphical DSL in industry. The Survey results show that participants think the proposed graphical language can help them to better understand the Scrum method and specific Scrum projects. Moreover, we noticed that the developers who have less Scrum development experience show more interests in this proposed graphical language. Conclusions. To conclude, the obtained results of this study indicate that a graphical DSL can improve the understandability of Scrum method and specific Scrum projects. Especially in managing the specific Scrum project, subjects can easily understand and capture the detailed information of the project described in the proposed language. This study also specified the merits and demerits of using the graphical language and textual language in describing the Scrum process. From the survey, the result indicates that the proposed graphical language is able to help developers to understand Scrum method and specific Scrum projects in industry. Participants of this survey show positive opinion toward the proposed graphical language. However, it is still a rather long way to applying such a graphical language in Scrum projects development because companies have to consider the extra learning effort of the graphical DSL.
4
Svoboda, Radek. "Efektivní využití SCRUM metodiky ve vývojovém týmu." Master's thesis, Vysoké učení technické v Brně. Fakulta podnikatelská, 2017. http://www.nusl.cz/ntk/nusl-318346.
Анотація:
The master thesis focuses on more efficient application of Scrum methodology in a development team within specific company. The thesis takes an advantage from the SW-CMM philosophy applied in agile environment in order to achieve better effectivity. Theorethical base is utilized for a comparison with current state in the company described in analytical part. Proposals for a solution of current situation are based on drawback detection. Proposals are subject for risk analysis followed by precaution. Costs of proposals implementation with included precautions are evaluated in economic evaluation part. This part also contains benefits of proposals.
5
Kubalcová, Monika. "ITIL v prostředí agilního vývoje software metodikou Scrum." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2014. http://www.nusl.cz/ntk/nusl-235418.
Анотація:
This thesis follows concept of integration ITIL library and agile methodology Scrum into the IT company developing IT services. After theoretical analysis of both concepts and analysis of chosen company, we will develope methodology, which will tie both process approaches and ensure their perfect synergy. As a methodology support, web application was developed. It evaluates effectivness of processes using key informations and their plot representation. Proposed methodology was presented in the AVG Technologies, which used described processes as template for its internal proceses. Main result of the thesis is set of templates describing processes, which could be specified and applied in companies using Scrum together with ITIL for their development.
6
Srirangarajan, Ananth Lall Pradeep Umphress David A. "The scrum process for independent programmers." Auburn, Ala, 2009. http://hdl.handle.net/10415/1617.
7
Kodali, Manvisha. "TRACEABILITY OF REQUIREMENTS IN SCRUM SOFTWARE DEVELOPMENT PROCESS." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-28326.
Анотація:
Incomplete and incorrect requirements might lead to sub-optimal software products, which might not satisfy customers’ needs and expectations. Software verification and validation is one way to ensure that the software products meets the customers’ expectations while delivering the correct functionality. In this direction, the establishment and the maintenance of traceability links between requirements and test cases have been appointed as promising technique towards a more efficient software verification and validation. Through the last decades, several methodologies supporting traceability have been proposed, where most of them realize traceability by implicitly exploiting existing documents and relations. Nevertheless, parts of the industry is reluctant to implement traceability within software development processes due to the intrinsic overhead it brings. This is especially true for all those light-weight, code-centric software development processes, such as scrum, which focus on the coding activities, trying to minimizing the administrative overhead. In fact, the lack of documentation finishes to hamper the establishment of those trace links which are the means by which traceability is realized. In this thesis, we propose a methodology which integrates traceability within a scrum development process minimizing the development effort and administrative overhead. More precisely we i) investigate the state-of-the-art of traceability in a scrum development process, ii) propose a methodology for supporting traceability in scrum and iii) evaluate such a methodology upon an industrial case study provided by Westermo.
8
SILVA, Ivonei Freitas da. "A scrum-inspired process for software product lines scoping." Universidade Federal de Pernambuco, 2013. https://repositorio.ufpe.br/handle/123456789/12265.
Анотація:
Scoping in Software Product Lines (SPL) is the first step to identify products, features,
and assets in a market segment. Traditional approaches for SPL scoping are heavyweight
and upfront processes in scenarios with unpredictable changes and little resources. An
incurred key challenge is handling systematically the iterativeness, adaptability, and
feedback in the SPL scoping process. As a final consequence, the software industry can
hamper investment in the SPL scoping. In this context, the Scrum framework, as the
most popular agile approach to foster the iterativeness, adaptability, and feedbacks, can
address that challenge. Previous studies have combined Scrum into some SPL activities
with good results. This thesis provides a process, named of RiPLE-SCA, for SPL scoping
inspired in the Scrum practices. This process bases on industrial evidence (a case study of
a traditional SPL scoping), expert opinion on agile SPL (through a survey), and scientific
literature about agile SPL (a systematic mapping). A feasibility study and a cross-case
study carried out with two industrial partners indicated that the RiPLE-SCA is practicable
and appropriate for an industrial setting as well as fosters iterativeness, adaptability,
and feedbacks detecting early obsolete features and changes in domain, requirements,
features, and technology.Submitted by João Arthur Martins (joao.arthur@ufpe.br) on 2015-03-12T18:58:41Z No. of bitstreams: 2 Tese Ivonei Freitas da Silva.pdf: 9233841 bytes, checksum: 6029df71deecd12c97bd99e1787a8361 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5)
Made available in DSpace on 2015-03-12T18:58:41Z (GMT). No. of bitstreams: 2 Tese Ivonei Freitas da Silva.pdf: 9233841 bytes, checksum: 6029df71deecd12c97bd99e1787a8361 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Previous issue date: 2013-10-29
CNPq
A atividade de escopo em linhas de produto de software é o primeiro passo para identificar produtos, características e ativos de software em um segmento de mercado. As abordagens tradicionais para escopo de linhas de produto de software são processos densos e abrangentes em cenários com mudanças imprevisíveis e com poucos recursos. Um desafio chave nesse cenário é o gerenciamento sistemático da iteratividade, adaptabilidade e do feedback no processo de escopo de linhas de produto de software. Como último efeito, a indústria de software pode restringir investimentos no processo de escopo. Neste contexto, o framework Scrum, abordagem mais popular para incentivar a iteratividade, a adaptabilidade e o feedback, pode lidar com esse desafio. Estudos anteriores têm combinado Scrum com algumas atividades de linhas de produto de software obtendo bons resultados. Esta tese define um processo, denominado de RiPLE-ASC, para o escopo da linha de produtos de software inspirado nas práticas do Scrum. Este processo basea-se nas evidências da indústria (um estudo de caso real de escopo de linhas de produto usando uma abordagem tradicional), na opinião de especialistas em linhas de produto de software ágeis (através de um survey) e na literatura científica sobre linhas de produto de software ágeis (uma mapeamento sistemático). Um estudo de viabilidade e um estudo de caso “cross-case” executados com dois parceiros industriais de nosso grupo de pesquisa indicaram que o RiPLE-ASC tem aplicação prática e adequa-se em um ambiente de produção de software industrial bem como incentiva a iteratividade, adaptabilidade e o feedback detectando cedo características obsoletas e mudanças no domínio, requisitos, características e tecnologia
9
Malone, Michael W. "Process subversion in Agile Scrum software development| A phenomenological approach." Thesis, Capella University, 2014. http://pqdtopen.proquest.com/#viewpdf?dispub=3632735.
Анотація:
This qualitative study examined the ways in which process subversion, defined as any attempt, conscious or unconscious, to work around, ignore, or turn to one's own purposes an established process, occurs in Scrum software development. Scrum is a software development methodology that uses self-managing teams and a well-defined process but does not dictate developer practices. It has been shown in previous research that problems with Scrum can cause issues with productivity and software quality. This descriptive phenomenological study specifically examined the ways in which process subversion was experienced by Scrum Masters. The Scrum Master is a coach and facilitator to the development team in Scrum. The study revealed a wide variety of perceptions of the Scrum Master's role as well as sources of subversion ranging from individuals on the development team to the structure of the organization. The study also revealed the creativity used by some Scrum Master in responding to such subversion. This study is important because it fills a gap in the extant literature in dealing with the problems that occur when an organization attempts to use Scrum as its development process, and provides insights that may be helpful in either mitigating the effects of such subversion or preventing it outright.
10
Marques, Joice Basilio Machado. "OntoSoft: um processo de desenvolvimento ágil para software baseado em ontologia." Universidade de São Paulo, 2017. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-06022018-084132/.
Анотація:
A formalização e o compartilhamento do conhecimento tem incentivado cada vez mais o uso de ontologias em diversas áreas da computação. Na Engenharia de Software, por exemplo, elas são usadas em diferentes fases do ciclo de vida do software. Especificamente no desenvolvimento de software a ontologia pode ser considerada como um artefato de software que atua na formalização do conhecimento e requisitos, na geração automática de código, na integração contínua e na transformação de dados em conhecimento. No entanto, poucos estudos abordam esses fatores de maneira sistematizada na construção do software baseado em ontologia, ao associar os conceitos da Engenharia de Software à Engenharia de Ontologias. Além disso, as abordagens atuais não inserem princípios ágeis em suas definições. Portanto, este trabalho tem por objetivo definir um processo de desenvolvimento considerando os princípios e valores ágeis para o desenvolvimento de software baseado em ontologia. No processo, denominado OntoSoft, fases, atividades, tarefas, papeis e modelos de artefatos foram definidos de maneira detalhada para guiar as equipes de desenvolvimento. Ademais, foram especificados três cenários de desenvolvimento considerando a complexidade do software a ser desenvolvido, a fim de evidenciar possibilidades distintas na sequência das atividades durante o fluxo de desenvolvimento do software baseado em ontologia. Com base nos estudos de caso conduzidos em diferentes cenários de desenvolvimento, os resultados sugerem que o processo OntoSoft contribui positivamente na produção dos artefatos do software baseado em ontologia, colaborando para a efetividade e produtividade da equipe.Formalization and knowledge sharing have increasingly encouraged the use of ontologies in several areas of computing. In Software Engineering, for example, they have been used in different phases of the software life cycle. Specifically in software development, an ontology can be considered as a software artifact, which acts in the formalization of knowledge and requirements, automatic generation of code, continuous integration and data transformation into knowledge. However, few studies deal with these factors in a systematized way for the development of ontology based software, regarding to associating Software Engineering and Ontology Engineering concepts. In addition, current approaches do not address agile principles in their definitions. In this sense, this work aims to define a development process concerning the principles and agile values for ontology based software development. In the process, called OntoSoft, phases, activities, tasks, roles, and artifact models were defined in detail to guide development teams. In addition, three development scenarios were specified considering the complexity of the software to be developed, in order to demonstrate distinct possibilities of development flow of the ontology based software. Based on case studies conducted in different development environments, the results suggest that the OntoSoft process contributes positively to the development of ontology based software artifacts, contributing to the effectiveness and productivity of the team.
11
Tománek, Martin. "Podpora IS/IT v SCM automobilového průmyslu." Master's thesis, Vysoká škola ekonomická v Praze, 2009. http://www.nusl.cz/ntk/nusl-10337.
Анотація:
Specification and new trends in the automotive industry impose higher requirements on supply chain management. This thesis describes a part of supply chain management -- reverse logistics and circulation of returnable transport units. The main goal and asset of this thesis is to analyse processes of the team managing the circulation of returnable transport units in the British automobile factories Jaguar and Land Rover. The next main aim and asset is to apply the ITIL methodics Incident management for creating and implementing an application which is based on the process analysis and supports informational needs of individual roles in this team.
12
Mačiulis, Edvinas. "Sinchroninio mokymo proceso standartizavimas vaizdo paskaitų sistemoje ViPS." Master's thesis, Lithuanian Academic Libraries Network (LABT), 2008. http://vddb.library.lt/obj/LT-eLABa-0001:E.02~2008~D_20080716_110900-91705.
Анотація:
Magistriniame darbe rašoma apie ViPS lokalaus video paskaitų įrašymo įrankį, ir jo standartizavimo galimybes. Atliekama egzistuojančių sistemų apžvalga ir analizė, įvertinamos kokybinės ir funkcinės galimybės. Pateikiama informaciją tiek apie platformos architektūrą, tiek apie pačio įrankio realizavimo detales, funkcinius ir nefunkcinius reikalavimus, testavimo metodus. Apžvelgiamos e.mokymosi technologijų specifikacijos, tokios kaip IMS LD, AICC, LOM, SCORM. Įvertinamos ir ažvelgiamos SCORM standarto realizavimo galimybės bei diegimo rezultatas.In this master thesis main topic is distace learning. It‘s another learning method more confortable, but makes a little bit difficulties, when the intent is to deliver information ant to make distance learning equal to the traditional. The main problem of distance learning is the presentation of the learning material. Lecturers and other people are trying to make learning process easier and more effective. It‘s characteristics depends on the tools, software and hardware, witch is used to represent and deliver learning material. In this work we will know more about video presentation system ViPS and it‘s additional tool for local video lectures recording, when there is not internet. Presented information is about the value tools give us and requirements for it‘s functionality, architecture and results. Finally we will know more about distance learning standards, it‘s advantages and disadvanages and of course the possibility of implementation of the most suitable standart for the ViPS local recoding tool.
13
Ferbr, David. "Návrh architektury franšízové sítě." Master's thesis, Vysoká škola ekonomická v Praze, 2012. http://www.nusl.cz/ntk/nusl-165146.
Анотація:
The topic of this thesis is the application of business process management approach to an operating franchise network. The aim is to describe the current state of the company, iden-tify problem areas complicating further development and to propose the future state of the company and plan the transition to this state. The theoretical part presents the issue of franchising and the selected topics from the field of process management, which provides the basis for the practical part, devoted to design the proposed changes and plans for their implementation. Work can be interesting in terms of linking of franchising and process management, appli-cation of which it suggests.
14
Lin, Yishuai. "An organizational ontology for multiagent-based Enterprise Process modeling and automation." Phd thesis, Université de Technologie de Belfort-Montbeliard, 2013. http://tel.archives-ouvertes.fr/tel-00977726.
Анотація:
The work presented in this PhD thesis defines a new approach for the modeling and the conceptualization of enterprise business processes in the perspective of building intelligent assistance software tools to support these processes. The proposed approach defines an organizational ontology, named K-CRIO. Its description is based on the Ontology Web Language. To illustrate our work, an intelligent assistance system has been designed and implemented according to the result from the modeling and conceptualization of a specific business process with the K-CRIO Ontology. It is a web-based application that integrates and takes full advantage of multi-agent systems.The K-CRIO Ontology is an Ontology dedicated to the study of organizations and the analysis of business processes adopting an organizational point of view. Specifically, it is used to understand, analyze and reason about organizations and the processes they implement. The targeted organizations are those composed of entities involved throughout products' design and, to do so, following a defined business process. The range of this type of organizations is quite wide. We have thus limited our study to organizations that produce software as the final process goal, specifically IT enterprises delivering software products or services. In this context, the K-CRIO ontology could be used to model structure of the considered organizations and model human activities appearing in their business processes. This ontology could be used to support process assistance within the described organizations. More specifically, the ontology could provide means for reasoning, annotating resources, monitoring design processes, enabling searches and pro-actively proposing tips and proper content. In order to illustrate the usage of K-CRIO, we apply K-CRIO on two different processes: the Waterfall Model and the Scrum methodology. These examples are both classical software-development processes. Moreover, for Scrum, the famous agile software-development process widely used in software enterprises, we have designed and developed an intelligent assistance tool. This tool mainly helps Scrum Masters to make decision by monitoring Scrum project teams' activities within their various projects and collecting knowledge about these activities.
15
Costa, Filho Edes Garcia da. "Integração de padrões organizacionais e de processo ao método ágil Scrum." Universidade Federal de São Carlos, 2006. https://repositorio.ufscar.br/handle/ufscar/310.
Анотація:
Made available in DSpace on 2016-06-02T19:05:16Z (GMT). No. of bitstreams: 1
DissEGCF.pdf: 2151341 bytes, checksum: 2582a4d133839a81e584adb3fcc3f286 (MD5)
Previous issue date: 2006-05-17Universidade Federal de Sao Carlos
Due to the increasing importance of software in society, the software engineering area has devoted continuous effort to improve the software products development process. Today, even with the technological progress, organizations are facing problems to build software within establishing time and costs. Organization and process patterns supply proven solutions to recurring software development process. These pattern categories allow reuse in higher abstract levels, that is, in organizational and process levels. However, else than improve and organize the software development process, organizations must speed up that process to attend market demands. Agile development methods such as Scrum and Extreme Programming (XP) are being often utilized due to the proposal of delivering quality software in less time. In that context, this paper proposes an organized form to use organizational and process patterns together with the Scrum agile method, to allow its extension or adaptation according to the needs of the organization that will use it. Based in use experience and using the SPEM metamodel, phases of integration of organizational and process patterns to Scrum have been proposed and used to create a Scrum extension. Scrum, as other agile methods, presents some weak points that need alternatives to improve them. So, using the phases devised, some organization and process patterns have been integrated to Scrum in order to deal with questions not approached by it. The result of a pilot evaluation study conducted to verify the advantages of that integration and of the SPEM modeling, has indicated the convenience to do them. After the application of the integration phases with some patterns and Scrum, the possibility of guidelines creation to integrate organizational and process patterns to other agile methods has been noted.
Devido à importância cada vez maior do software na sociedade, a área de Engenharia de Software vem se esforçando ao longo dos anos para melhorar o processo de desenvolvimento de produtos de software. Hoje, mesmo com o avanço da tecnologia, as organizações enfrentam problemas para construir software nos prazos e custos estabelecidos. Os padrões organizacionais e de processo fornecem soluções comprovadas para problemas recorrentes no desenvolvimento de software. Essas categorias de padrões possibilitam o reúso em níveis mais altos de abstração, ou seja, em nível organizacional e de processo. Porém, além de melhorar e organizar o processo de desenvolvimento de software, as organizações precisam acelerar esse processo para atender às demandas de mercado. Métodos ágeis de desenvolvimento como Scrum e Extreme Programming (XP) estão sendo cada vez mais utilizados, devido à sua proposta de liberar software com qualidade em prazos menores. Nesse contexto, este trabalho propõe uma forma ordenada para utilizar padrões organizacionais e de processo em conjunto com o método ágil Scrum, para possibilitar sua extensão ou adaptação, de acordo com as necessidades da organização que o utiliza. Com base em uma experiência de uso e com a utilização do meta-modelo SPEM (Software Process Engineering Metamodel) as etapas de integração dos padrões organizacionais e de processo com o Scrum foram elaboradas e utilizadas para criar uma extensão desse método. O Scrum, como outros métodos ágeis, apresenta alguns pontos fracos que necessitam de alternativas para melhorá-los. Assim, por meio das etapas elaboradas, alguns padrões organizacionais e de processo foram integrados ao Scrum para tratar as questões não abordadas por ele. O resultado de um estudo piloto de avaliação conduzido para verificar as vantagens dessa integração e da modelagem realizada com SPEM indicou a conveniência de fazê-los. Após a aplicação das etapas de integração com alguns padrões e o Scrum, notou-se a possibilidade da criação de diretrizes de integração de padrões organizacionais e de processo a outros métodos ágeis.
16
ARAGAO, ANDREA BARCELLOS DE. "SCM MODEL BASED ON PROCESS INTEGRATION, INFORMATION SHARING, AND PERFORMANCE MEASURES." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2004. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=5130@1.
Анотація:
COORDENAÇÃO DE APERFEIÇOAMENTO DO PESSOAL DE ENSINO SUPERIORA gestão da cadeia de suprimentos (SCM, Supply Chain Management) está criando oportunidades e desafios para a competição no mundo dos negócios. Apesar disto, ainda existem poucos modelos que oferecem uma análise efetiva de SCM. Dentro deste contexto, esta dissertação tem o intuito de propor um modelo para analisar cadeias de suprimentos baseado em dimensões- chave necessárias para uma bem sucedida SCM. Nessa dissertação, as dimensões consideradas são: integração de processos de negócios, identificação dos membros-chave da cadeia, compartilhamento de informação e medidas de desempenho apropriadas para cadeia de suprimento. Com o objetivo de validar o modelo e avaliar a sua aplicação, foi conduzido um estudo de caso em diferentes cadeias de suprimento de um grande fabricante nacional de cilindros de armazenamento de Gás Natural Veicular (GNV). Para efeitos da análise de SCM, este fabricante é considerado nesta aplicação como a empresa focal da cadeia. A partir da aplicação do modelo nessas diferentes cadeias pôde-se constatar um maior compartilhamento de informação e adoção de medidas de desempenho no processo de negócio SRM (Supplier Relationship Management) do que no processo de negócio CRM (Customer Relationship Management). No CRM, também foi constatado que as cadeias são mais integradas com o fabricante de cilindros de GNV, quando esse cilindro é o seu produto principal, e menos integrada, quando o produto principal das cadeias é outro, como por exemplo, o automóvel zero quilômetro.
The Supply Chain Management (SCM) is creating many opportunities and challenges for world business competition. In spite of this, there are still just a few models that offer an effective SCM analysis. Within this context, this dissertation attempts to propose a model for a supply chain analysis based on key dimensions that are necessary for a successful SCM. The key dimensions considered in this dissertation are: business processes integration, key supply chain members identification, information sharing, and appropriate supply chain performance measures. In order to validate the model and to evaluate its application, a case study was conducted in different supply chains of a big national manufacturer of CNG (Compressed Natural Gas) cylinders for vehicles. Towards the SCM analysis, this manufacturer is considered in this application as the supply chain`s focal company. With the model`s application in these different supply chains, it was possible to figure out a more intense information share and use of performance measures in the SRM (Supplier Relationship Management) business process than in the CRM (Customer Relationship Management) business process. In CRM, it was also found that the supply chains are more integrated with the focal company when the cylinder is the chain`s main product and less integrated when the chain`s main product is another, for instance, a brand new car.
17
Doležel, Patrik. "Zefektivnění vybraného firemního procesu pomocí nástrojů projektového řízení." Master's thesis, Vysoké učení technické v Brně. Fakulta podnikatelská, 2019. http://www.nusl.cz/ntk/nusl-399420.
Анотація:
This diploma thesis deals with a type of efficiency improvement of the hiring process in a company, where agile methods are used for the development of its software products. The theoretical part describes specification of traditional and agile methods, and a profound description of the Scrum and Kanban methods and the use of agile methods for hiring activities. In the following part, there is issued an analysis of the current situation in the company oriented to HR department and suggesting possible solutions for discovered problems.
18
Lönngren, Josefin, and Sandra Fahlén. "Kvalitetssäkring och test av leveranser vid arbete enligt scrum : En fallstudie på företaget SSG." Thesis, Mittuniversitetet, Avdelningen för informations- och kommunikationssystem, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:miun:diva-28658.
Анотація:
Failed projects are often caused by not detected failures and therefore tests should be performed at some time during the project to avoid those failures. In the agile method Scrum the tests of IT services are executed by the supplier to secure the quality of the services. In theory, no tests are performed by the product owner. This requires big amount of trust to the supplier and a close partnership. In agile methods the time and costs are fixed, and because of this there is also a risk that unfinished products are delivered on deadline. Little research about tests and Scrum can be found, and therefore the aim with this study is to evaluate how and when quality assurance and tests should be treated in the best way by the product owner in Scrum. The study aims to answer the question of which manual test type is relevant to perform by the product owner to ensure the quality of the IT services. The question about how and when the test should be executed should also be answered. The study is based on a case study at the company Standard Solutions Group (SSG) which is a technical consultancy. The methodology in the study involves interviews, observations, a survey, and a literature study. The different methods are used to gather information from different perspectives and should increase reliability. Acceptance tests are selected to be best suitable to be performed by the product owner. To answer the question about how the test should be executed the authors select to develop a checklist. The acceptance tests should be done continuously to create more efficiency, and it also should be easier to correct the errors.Idag grundas ofta misslyckade projekt på att fel inte uppmärksammas och för att undvika dessa fel bör tester utföras någon gång under arbetet. I den agila metoden Scrum utförs tester på produkten av leverantören, däremot utförs i teorin inga tester från produktägarens sida, som är kunden i Scrum. Detta kräver stor tillit och ett nära samarbete mellan kund och leverantör. Eftersom agila metoder innebär att tiden och kostnaden är fast finns det även en risk att halvfärdiga produkter levereras vid deadline. Då tidigare forskning inte undersökt ämnet är syftet med arbetet att utvärdera hur och när kvalitetssäkring av leveranser på ett lämpligt sätt ska utföras från produktägarens sida i Scrum. Målet är dels att besvara frågan om vilken manuell testtyp som är relevant att utföra från produktägarens sida vid kvalitetssäkring av IT-tjänster. Dessutom ska även frågorna om hur och när det manuella testet bör utföras i Scrum besvaras. Denna studie baseras på en fallstudie som utförs hos Standard Solutions Group (SSG) som är en teknisk konsultverksamhet. Studien genomförs med hjälp aven övergripande metod som följs genom hela arbetet för att komma fram till en lösning. I studien används även andra modeller för att utföra observationer, enkätundersökning, intervjuer och en litteraturstudie. Detta för att få information från flera olika perspektiv vilket ökar studiens tillförlitlighet. Studien resulterar i atttest-typen acceptanstester är ett lämpligt test att utföra frånproduktägarens sida. En checklista utvecklas för att svara på frågan om hur testet ska utföras. För att skapa mer effektivitet så att fel enklare ska kunna åtgärdas utförs acceptanstestester kontinuerligt under arbetets gång.
19
Marçal, Ana Sofia Cysneiros. "SCRUMMI : um processo de gestão ágil baseado no SCRUM e aderente ao CMMI." Universidade de Fortaleza, 2009. http://dspace.unifor.br/handle/tede/81820.
Анотація:
Made available in DSpace on 2019-03-29T23:15:49Z (GMT). No. of bitstreams: 0
Previous issue date: 2009-07-10Nowadays, organizations have employed substantial efforts in processes improvement based on quality models, such as CMMI. Additionally, these organizations have shown a growing interest in the adoption of agile methods, focusing on increasing their productivity. Based on the assumption that it is possible to combine agility with discipline, this research initially embraced the challenge of analyzing the adherence of Scrum to CMMI practices, specifically with Project Management processes. This work contemplated a quantitative research to investigate the real interest of the Brazilian organizations in adopting agile practices and CMMI in the management of their projects. The research results were used as basis to the definition of an agile management process, called Scrummi, built from an extension of the Scrum to be compliant with the CMMI project management process areas. Scrummi is a simple but complete management process, which can be extended and tailored to support a variety of projects, being relevant to organizations that aim to adopt an agile project management methodology compatible with CMMI practices. The process documented in this research was used in a real software development project in a Brazilian R&D company which is compliant to CMMI maturity level 3, showing that agility and discipline can be applied together. Through Scrummi, innovative practices were introduced in the organizational context. The case study project became a reference inside the company, representing a new style of management. Main improvements achieved were related to increase in productivity, directly influenced by high commitment and development of project team. Keywords: Agile Project Management, SCRUM, CMMI, Agile Software Development
Atualmente vive-se um cenário onde organizações de software têm empregado esforços substanciais na melhoria dos seus processos com base em modelos de qualidade, tais como o CMMI. Adicionalmente, estas organizações têm demonstrado um interesse crescente na adoção de métodos ágeis, com foco em aumentar sua produtividade. Acreditando-se na hipótese de que é possível combinar agilidade com disciplina, este trabalho abraçou inicialmente o desafio de analisar a aderência do Scrum em relação ao CMMI, especificamente no que diz respeito aos processos de gerenciamento de projetos. Em seguida, foi feita uma pesquisa quantitativa para se investigar o real interesse de organizações brasileiras em adotar práticas de métodos ágeis e CMMI na gestão de seus projetos. Os resultados obtidos com as investigações realizadas embasaram a definição do processo de gestão ágil, chamado Scrummi, construído a partir de extensões do Scrum para ficar aderente às áreas de processo de gerenciamento de projeto do CMMI. O Scrummi é um processo de gestão simples e completo, o qual pode ser estendido e adaptado para atender a uma grande variedade de projetos, sendo relevante para organizações que têm o propósito de adotar uma metodologia de gerenciamento de projetos ágil e que seja ao mesmo tempo compatível com práticas do CMMI. O processo definido neste trabalho foi aplicado em um projeto real de desenvolvimento de software em uma empresa brasileira de pesquisa e desenvolvimento aderente ao nível 3 de maturidade do CMMI mostrando assim que agilidade e disciplina podem andar juntas. Através do Scrummi foram introduzidas práticas inovadoras no contexto organizacional, tornando o projeto do estudo de caso uma referência na empresa com relação ao novo estilo de gerenciamento. As melhorias envolveram aumento de produtividade obtida através do desenvolvimento e comprometimento do time do projeto. Palavras-chave: Gerenciamento Ágil de Projetos, SCRUM, CMMI, Métodos Ágeis.
20
Choma, Joelma. "ScrumUX: uma abordagem para integrar design de interação do usuário ao processo Scrum." Universidade Federal de São Carlos, 2015. https://repositorio.ufscar.br/handle/ufscar/7918.
Анотація:
Submitted by Milena Rubi (milenarubi@ufscar.br) on 2016-10-19T11:30:53Z
No. of bitstreams: 1
Choma_Joelma_2015.pdf: 93651349 bytes, checksum: 4f1e422a507384b78e63a797fc7488f8 (MD5)Approved for entry into archive by Milena Rubi (milenarubi@ufscar.br) on 2016-10-19T11:31:08Z (GMT) No. of bitstreams: 1 Choma_Joelma_2015.pdf: 93651349 bytes, checksum: 4f1e422a507384b78e63a797fc7488f8 (MD5)
Approved for entry into archive by Milena Rubi (milenarubi@ufscar.br) on 2016-10-19T11:31:20Z (GMT) No. of bitstreams: 1 Choma_Joelma_2015.pdf: 93651349 bytes, checksum: 4f1e422a507384b78e63a797fc7488f8 (MD5)
Made available in DSpace on 2016-10-19T11:31:30Z (GMT). No. of bitstreams: 1 Choma_Joelma_2015.pdf: 93651349 bytes, checksum: 4f1e422a507384b78e63a797fc7488f8 (MD5) Previous issue date: 2015-11-10
Não recebi financiamento
Agile development principles ensure that continuous attention to technical excellence combined with a good design contributes to increased agility ensuring products with higher quality. Usability is one of the quality attributes, and is related to making the experience enjoyable user through an efficient and intuitive interface design. Agile methods are committed to deliver valuable software to the satisfaction of the customer. At times, they deliver only the utility, without covering aspects of usability. Design solutions providing greater usability and more appropriate to the users’ context is the main concern of the Interaction Design (IxD). The IxD is based on user-centered design, which takes into account the users needs and wants, aiming to promote interaction more enjoyable experience. In recent years, the attention in integrating user-centered design practices into agile methodologies has increased. However, a very limited number of contributions have addressed the integration into a broader level, gathering practices and providing guidance to the organization of work within a software development roadmap. This dissertation presents an approach to integrate user interaction design into Scrum process through activities and artifacts. In the first stage of the study, a literature study was performed to determine possible strategies for integrating IxD into Scrum process. Furthermore, an action research approach was applied to define and evaluate the artifacts that would support the ScrumUX integration approach, closely with the professionals in the software development industry. In the second stage, an experimental study was carried out to evaluate the proposed ScrumUX integration compared to traditional Scrum approach. The experiment was carried out in an academic context, in which nineteen students divided into five teams worked in software development projects, in the ERP systems domain. Statistical tests confirmed a significant difference between the experimental and control groups, noting that the teams who used the ScrumUX approach produced software with better degree of usability in the task support perspective, considering ERP systems’ users opinion.
Princípios do desenvolvimento ágil asseguram que a atenção contínua á excelência técnica aliada á um bom design contribui para o aumento de agilidade garantindo produtos com maior qualidade. A usabilidade é um dos atributos da qualidade, e está relacionada com tornar a experiência do usuário agradável por meio de um design de interface eficiente e intuitivo. Métodos ágeis estão comprometidos em satisfazer os clientes entregando software de valor. Mas, por vezes, acabam entregando somente a utilidade, sem cobrir os aspectos de usabilidade. Projetar soluções com maior usabilidade e mais apropriadas ao contexto dos usuários é a principal preocupação do Design de Interação (DxI). O DxI fundamenta-se no design centrado no usuário, que leva em conta as necessidades e desejos dos usuários para promover a mais agradável experiência de interação. O interesse em integrar práticas de design centrado no usuário com metodologias ágeis tem aumentado nos últimos anos. Contudo, um número bem limitado de contribuições têm abordado a integração em um nível mais abrangente, reunindo práticas e fornecendo orientações para a organização do trabalho dentro de um roteiro de desenvolvimento de software. Esta dissertação apresenta uma abordagem para integrar o Design de Interação do usuário ao processo Scrum por meio de atividades e artefatos. Na primeira etapa do estudo, realizou-se um estudo bibliográfico para verificar as possíveis estratégias para a integração do DxI com o processo Scrum, e em paralelo uma abordagem de pesquisa-ação foi aplicada, junto á profissionais da indústria de desenvolvimento de software, para definir e avaliar os artefatos que dariam suporte á abordagem de integração ScrumUX. Na segunda etapa, um estudo experimental foi conduzido com objetivo de avaliar a proposta de integração ScrumUX em relação ao Scrum tradicional. O experimento foi realizado em contexto acadêmico, onde dezenove alunos divididos em cinco equipes atuaram em projetos de desenvolvimento de software no domínio de sistemas ERP. Os testes estatísticos confirmaram uma diferença significativa entre os grupos experimentais e de controle, apontando que as equipes que utilizaram a abordagem ScrumUX produziram softwares com melhor grau de usabilidade na perspectiva de suporte á tarefas, considerando o ponto de vista de usuários de sistemas ERP.
21
Dreiseitel, Jiří. "Agilní metody vývoje software." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2015. http://www.nusl.cz/ntk/nusl-264956.
Анотація:
The thesis deals with basic principles of agile software development and describes their advantages compared to the traditional approach. Siemens, s.r.o in Brno uses combination of Scrum and Kanaban as part of organizational processes, therefore the thesis focuses mainly on the method Scrum, Kanban, Scrum-ban and compares these methods with each other. The thesis also analyzes the existing project and results were consulted with the representative of the Siemens company together with the proposals for improvement. JIRA plugin was designed and implemented base on our mutual agreement. This module extends the current tool for analyzing agile projects, this leads to better support of decision making in the context of agile processes. Benefits and further upgrades are consulted at the end of the thesis.
22
Johansson, Sofia. "Evaluation of alkali- impregnated honeycomb catalysts for NOx reduction in the SCR-process." Thesis, Växjö University, School of Technology and Design, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:vxu:diva-1151.
Анотація:
Samples of SCR catalysts were impregnated with the following alkali salts; KCl, K2SO4 and ZnCl2 at two different concentrations in a wet impregnation method. The activities of the six samples were measured in a test reactor and at different temperatures between 250-350 ºC. Compared to fresh catalyst, the impregnated samples all had lower activity. It seems like KCl is the most poisoning salt, depending on the lowest value of the activity. The experimental results are expected as compared to earlier articles, which reports that all alkali salts has deactivating effects on a catalyst and that KCl is among the most poisoning ones. By making a cross-section SEM analysis, the penetration of the metals at different depths in to the catalyst material wall was evaluated. An ICP-AES analysis was carried out in order to see the concentration of K and Zn of the test samples. Finally, the pore diameter and active surface was measured by BET method. Since the values of the active surface didn’t change compared to a fresh catalyst and the pore diameter was only slightly decreased we can suppose that the alkali salts deactivates the catalyst by coating of the catalyst pore structure and not as a pore blocking.
23
Šindelářová, Šárka. "Procesní model organizace." Master's thesis, Vysoká škola ekonomická v Praze, 2012. http://www.nusl.cz/ntk/nusl-165131.
Анотація:
This thesis covers with the topic of process management and organization modeling. The goal is to design a future state of process architecture in selected department of a multi-national company, which is based on ISO / IEC TR 29110-5-1-2:2011 for very small entities, complemented by techniques of agile methodologies. The final form of the future proposal includes the conceptual and detail design according to the aforementioned standard, supported by the selected agile techniques, adjusted for the results of the differential analysis of conceptual and detail design and current status. The theoretical part presents the issue of process management and modeling standards and a methodology for modeling and control of IT processes. The practical part is devoted to the application of the selected standard for IT management processes and agile techniques that support this standard. The proposed process architecture is modeled using the selected methodology MMABP and prescribed standards. The work can serve as an inspiration for the company that would be suited a combination of traditional and agile approaches to IT.
24
Mišurová, Katarína. "Posouzení informačního systému firmy a návrh změn." Master's thesis, Vysoké učení technické v Brně. Fakulta podnikatelská, 2018. http://www.nusl.cz/ntk/nusl-378347.
Анотація:
A thesis deals with the assessment of the information system in an engineering company, the assessment of its efficiency and the proposal of the ICT modification to improve this system. Furthermore, the thesis deals with the proposal of the information system changes in the company and the elimination of the risks related to these changes. An analytical part also deals with the company analysis, the analysis of the company processes and the analysis of the current information system. .
25
Tanner, Maureen Cynthia. "Social conditions leading to Scrum process breakdowns during Global Agile Software Development: a theory of practice perspective." Doctoral thesis, University of Cape Town, 2013. http://hdl.handle.net/11427/17270.
Анотація:
Global Software Development (GSD) and Agile are two popular software development trends that are gaining in popularity. In addition, more and more organisations are now seeking to engage in agile software development within the GSD context to reap the benefits of both ventures and achieve project success. Hence, agile methodologies adapted to fit the GSD context are commonly termed Global Agile Software Development (GASD) methodologies. However, because of geographical, temporal, and cultural challenges, collaboration is not easily realized in the GASD context. In addition, this work context is characterized by multiple overlapping fields of practice, which further hinder collaboration, and give rise to social challenges. Given the existence of these social challenges, there is a need to further investigate the human-centred aspect of collaboration during GASD. Following an extensive literature review on the application of Scrum and other agile methodologies in GASD between 2006 and 2011, it was noted that there is a lack of understanding of the social conditions giving rise to the social challenges experienced during GASD. It was noted that past studies have instead sought to describe these social challenges and to provide mitigating strategies in the form of best-practices, without detailing and theorising about the social conditions under which these social challenges emerge. One of the objective of the study was thus to investigate the use of Scrum during GASD. In particular, the Scrum process breakdowns experienced during and after Scrum's sprint planning and retrospective meetings were identified. The social conditions under which these breakdowns emerged were investigated in the light of Bourdieu's Theory of Practice. Scrum Process breakdowns were defined as any deviation from an ideal Scrum process (as per the Scrum methodology's guidelines) which yields to the emergence of social challenges, conflict or disagreements in the GASD team. The study was empirical and qualitative in nature and followed the positivist research paradigm. Two case studies, in line with Bonoma (1985)'s "drift" and "design" stages of case study design, were undertaken to investigate the phenomena of interest and answer the research questions. The first case focused on a distributed agile team executing a software project across South Africa (Cape Town) and Brazil (Sao Paulo) while the second case focused on a team executing an agile software project across India (Pune) and South Africa (Durban). The site selection was carefully thought out and the results from the first case informed the second case in order to add more richness in the data being gathered. In both case studies, data was collected through semi-structured interviews, documentation, field notes and direct observation. The underlying theoretical framework employed for the study was the Theory of Practice (Bourdieu, 1990). The study has identified various forms of Scrum process breakdowns occurring during and after sprint planning and retrospective meetings: » Different perceptions about task urgency at the software development sites » Disagreements on the suitability of software engineering practices » Low level of communication openness during meetings involving the whole GASD team compared to internal meetings at the sites » Impromptu changes to user stories' content and priorities » Product Owner's low level of authority » Disagreements on estimation mechanisms » Number of User Stories to be completed during the Sprint Is imposed on the team » Decisions on Scrum process updates not made by the development team » Selective invitation to retrospective meetings In addition, various social conditions were identified as possibly leading to the emergence of these Scrum process breakdowns in the GASD context: » GASD project stakeholders' low level of capital in the joint field » Different beliefs and values because of multiple fields Two theoretical propositions were derived to describe the social conditions and the corresponding Scrum process breakdowns which are likely to emerge under these conditions.
26
Vieira, Óscar Alfredo Cardoso. "The benefits of implementing a scrum framework on the product development process of a non-it company." Master's thesis, Instituto Superior de Economia e Gestão, 2020. http://hdl.handle.net/10400.5/20770.
Анотація:
Mestrado em Gestão/MBAThe adoption of Agile methodologies, and specifically the Scrum framework, emerges as a manifestation against traditional approaches due to their inability to accept requirements changes during the product development process. Despite its initial use in the IT sector, Agile and Scrum succeeded in showing its ableness to provide benefits for all types of industries independently of its status quo. The purpose of this project is to highlight the benefits and advantages of the Agile methodology and, more precisely, the Scrum Framework for non-IT product development. Taking those into consideration, the main objective is to evaluate how the product development process of a specific multinational company, that has been using traditional methods across the last years, can benefit from the use of a different framework The current study starts by reviewing relevant published literature to find the theoretical factors affecting project management and product development processes, to further proceed by adopting an Action Research methodology in order to conduct a problem-based investigation. By combining direct observation with the use of a structured survey that evaluates six different categories of company?s Scrum readiness, this study articulates the exact points where the organization needs to work on and where it does stand, currently, regarding Scrum implementation. As a result, to foster future implementation, a set of suggestions are defined and the possible benefits are pointed out.
info:eu-repo/semantics/publishedVersion
27
Bacchiocchi, Gianluca. "Il processo di gestione dei brevetti in SCM Group s.p.a.: analisi e riprogettazione." Master's thesis, Alma Mater Studiorum - Università di Bologna, 2012. http://amslaurea.unibo.it/4266/.
28
Almeida, Ilton Marchi de. "Proposta de uso integrado dos métodos Scrum e CCPM na gestão de múltiplos projetos /." Bauru, 2017. http://hdl.handle.net/11449/151169.
Анотація:
Orientador: Fernando Bernardi de SouzaBanca: Jose de Souza Rodrigues
Banca: Robert Eduardo Cooper Ordoñez
Resumo: A Gestão de Projetos (GP) ganhou papel de destaque na viabilidade dos objetivos estratégicos das organizações. O desenvolvimento de produtos e serviços vem recebendo forte pressão do mercado, demandante de lançamentos frequentes e em prazos cada vez menores. Para atender estas novas exigências, a GP deve prover informações úteis para tomadas de decisões em ambientes de múltiplos e complexos projetos, sujeitos a relevantes incertezas e volatilidade. Considerando as oportunidades de melhoria das práticas da GP para lidar com este ambiente instável e ambíguo, o objetivo deste trabalho é propor, utilizando o método de Teoria Fundamentada em Dados (TFD), um framework que prescreva como aplicar de forma combinada dois métodos de GP: a Gestão de Projetos por Corrente Crítica (Critical Chain Project Management - CCPM) e o Scrum. Os resultados obtidos por este trabalho apontam que a integração destes métodos pode potencializar os benefícios e atenuar as fragilidades de cada uma delas em particular, e cujo uso articulado e coordenado pode permitir decisões mais efetivas em ambientes voláteis, incertos, complexos e ambíguos (VUCA - Volatility, Uncertainty, Complexity and Ambiguity) de múltiplos projetos.
Abstract: Project Management (PM) has gained a major role in the viability of the strategic objectives of organizations. The development of products and services has been under stronger market pressure, requesting frequent releases and in ever-shorter periods. To meet these new requirements, initiatives for maintaining PM as an information provider to make decisions in multiple and complex projects, exposed to relevant uncertainty and volatility, should be sought. Regarding the opportunities for improvement of PM practices to deal with this unstable and ambiguous environment, the objective of this work is to propose, using the Grounded Theory (GT) method, a framework that prescribes how to apply two GP methods in combination: the Critical Chain Project Management - CCPM and Scrum. The results of this work indicate that the integration of these methodologies can enhance the benefits and mitigate the weaknesses of each of them in particular. This hybrid model could permit a better articulation and coordination of the project tasks, allowing effective decisions in multiple project environments affected by volatility, uncertainty, complexity and ambiguity (VUCA).
Mestre
29
Mählberg, Esbjörn. "Agilt - men agilt nog?" Thesis, Uppsala universitet, Informationssystem, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-155302.
Анотація:
This paper aims to investigate whether a small organization with small development teams can find a value in leaving a functioning development process to follow a formal systems development methodology, if these organizations can find support in an agile systems development method and in such case the method needs to be adjusted according to the organizations unique conditions. A traditional plan-driven system development methodology includes a number of phases that are carried out sequentially and a completed phase can basically not be resumed. All requirements are specified at the beginning of a project and at the end of the project only one delivery of software take place. This can cause difficulties in for example dealing with changing requirements. Agile system development methods intend to deal with changing requirements and to enable continuous delivery of valuable, working software. In this paper, both the traditional plan-driven methods and agile methods will be explained. Research methodology and existing system development theories will be discussed and a company where the study has been conducted will be presented. The company's current work processes are analyzed and presented, and all collected data will be reviewed. The results of the paper shows that no initial adaptation of agile methods, Scrum in this specific case, needs to be implemented and that there is no evidence to suggest that small organizations with small development teams can not work after a formal agile methodology. Finally, a general discussion of the study will be conducted and conclusions whether the study objective has been achieved or not will be discussed.Denna uppsats ämnar undersöka huruvida en mindre organisation med små utvecklingsteam kan finna ett värde i att lämna en fungerande utvecklingsprocess för att följa en formell systemutvecklingsmetod, ifall dessa organisationer kan hitta ett metodstöd i agila systemutvecklingsmetoder och om metoderna i så fall behöver anpassas utefter organisationens unika förutsättningar. En traditionell plandriven systemutvecklingsmetod innehåller ett antal faser som genomförs sekventiellt och en slutförd fas kan i stort sett inte återupptas. Alla krav specificeras i början av ett projekt och endast en leverans av mjukvara sker. Detta kan medföra svårigheter med att hantera till exempel förändrade krav. Agila systemutvecklingsmetoder har för avsikt att hantera förändrade krav samt möjliggöra kontinuerliga leveranser av värdefull och fungerande programvara. Under uppsatsen kommer såväl traditionella plandrivna metoder som agila metoder att förklaras närmare. Metodval för forskningen och befintliga systemutvecklingsteorier kommer att diskuteras och ett företag där studien har bedrivits kommer att presenteras. Företagets nuvarande arbetsprocess analyseras och presenteras och alla datainsamlingar kommer att gås igenom. Resultatet av uppsatsen visar på att inga initiala anpassningar av agila metoder, Scrum i det här specifika fallet, behöver genomföras och att det inte finns något som tyder på att små organisationer med små utvecklingsteam inte kan arbeta efter en formell agil metod. Slutligen kommer en allmän diskussion om studien att föras och slutsatser gällande om syftet med studien har uppnåtts kommer att diskuteras.
30
PERKUSICH, Mirko Barbosa. "Um processo baseado em redes bayesianas para avaliação da aplicação do scrum em projetos de software." Universidade Federal de Campina Grande, 2018. http://dspace.sti.ufcg.edu.br:8080/jspui/handle/riufcg/1672.
Анотація:
Submitted by Emanuel Varela Cardoso (emanuel.varela@ufcg.edu.br) on 2018-09-10T20:31:40Z
No. of bitstreams: 1
MIRKO BARBOSA PERKUSICH – DISSERTAÇÃO (PPGCC) 2018.pdf: 3631770 bytes, checksum: 855cc4a180be90ee4d3788f2b18b6141 (MD5)Made available in DSpace on 2018-09-10T20:31:40Z (GMT). No. of bitstreams: 1 MIRKO BARBOSA PERKUSICH – DISSERTAÇÃO (PPGCC) 2018.pdf: 3631770 bytes, checksum: 855cc4a180be90ee4d3788f2b18b6141 (MD5) Previous issue date: 2018-03-05
O aumento na utilização de métodos ágeis tem sido motivado pela necessidade de respostas rápidas a demandas de um mercado volátil na área de software. Em contraste com os tradicionais processos dirigidos a planos, métodos ágeis são focados nas pessoas, orientados à comunicação, flexíveis, rápidos, leves, responsivos e dirigidos à aprendizagem e melhoria contínua. Como consequência, fatores subjetivos tais como colaboração, comunicação e auto-organização são chaves para avaliar a maturidade do desenvolvimento de software ágil. O Scrum, focado no gerenciamento de projetos, é o método ágil mais popular. Ao ser adotado por uma equipe, a aplicação do Scrum deve ser melhorada continuamente sendo complementado com práticas e processos de desenvolvimento e gerenciamento ágeis. Apesar da Reunião de Retrospectiva, evento do Scrum, ser um período reservado ao final de cada sprint para a equipe refletir sobre a melhoria do método de desenvolvimento, não há procedimentos claros e específicos para a realização da mesma. Na literatura, há diversas propostas de soluções, embora nenhuma consolidada, para tal. Desta forma, o problema em questão é: como instrumentar o Scrum para auxiliar na melhoria contínua do método de desenvolvimento com foco na avaliação do processo de engenharia de requisitos, equipe de desenvolvimento e incrementos do produto? Nesta tese, propõe-se um processo sistemático baseado em redes bayesianas para auxiliar na avaliação da aplicação do Scrum em projetos de software, instrumentando o método para auxiliar na sua melhoria contínua com foco na avaliação do processo de engenharia de requisitos, equipe de desenvolvimento e incrementos do produto. A rede bayesiana foi construída por meio de um processo de Engenharia de Conhecimento de Redes Bayesianas. Uma base de dados, elicitada de dezoito projetos reais de uma empresa, foi coletada por meio de um questionário. Essa base de dados foi utilizada para avaliar a acurácia da predição da Rede Bayesiana. Como resultado, a previsão foi correta para quatorze projetos (acurácia de 78%). Dessa forma, conclui-se que o modelo é capaz de realizar previsões com acurácia satisfatória e, dessa forma, é útil para auxiliar nas tomadas de decisões de projetos Scrum.
The use of Agile Software Development (ASD) is increasing to satisfy the need to respond to fast moving market demand and gain market share. In contrast with traditional plan-driven processes, ASD are people and communication-oriented, flexible, fast, lightweight, responsive, driven for learning and continuous improvement. As consequence, subjective factors such as collaboration, communication and self-management are key to evaluate the maturity of agile adoption. Scrum, which is focused on project management, is the most popular agile method. Whenever adopted, the usage of Scrum must be continuously improved by complementing it with development and management practices and processes. Even though the Retrospective Meeting, a Scrum event, is a period at the end of each sprint for the team to assess the development method, there are no clear and specific procedures to conduct it. In literature, there are several, but no consolidated, proposed solutions to assist on ASD adoption and assessment. Therefore, the research problem is: how to instrument Scrum to assist on the continuous improvement of the development method focusing on the requirements engineering process, development team and product increment? In this thesis, we propose a Bayesian networks-based process to assist on the assessment of Scrum-based projects, instrumenting the software development method to assist on its continuous improvement focusing on the requirements engineering process, development team and product increments. We have built the Bayesian network using a Knowledge Engineering Bayesian Network (KEBN) process that calculates the customer satisfaction given factors of the software development method. To evaluate its prediction accuracy, we have collected data from 18 industry projects from one organization through a questionnaire. As a result, the prediction was correct for fourteen projects (78% accuracy). Therefore, we conclude that the model is capable of accurately predicting the customer satisfaction and is useful to assist on decision-support on Scrum projects.
31
Jašek, Tibor. "Automatizace procesů agilního vývoje." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2016. http://www.nusl.cz/ntk/nusl-255437.
Анотація:
The goal of master thesis "Automation of Processes in Agile Development" is research of agile metodics with a focus on development practices in the Kentico company. This thesis describes different tools used as a support of agile software development including JIRA Software and Confluence, which are used in Kentico. Important part of this thesis is analysis of the current company processes and a plan of their optimization and automation. During the implementation part a web application which displays metrics arising from analysis and optimization proposal phase is realized. This thesis also contains discussion of it's realization and possible improvements.
32
Gajdušek, Radek. "Certifikace CMMI ve vývoji software v agilním prostředí." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2013. http://www.nusl.cz/ntk/nusl-235462.
Анотація:
The goal of master thesis "CMMI Certification for Software Development in Agile Environment" is CMMI quality model research with focus on software development in agile environment in the Siemens company. In the beginning CMMI model and Scrum methodics are introduced. The core of this thesis is focused on the current state analysis. Output of the analysis is a list of potential areas that are currently not compatible with quality model requirements. These areas are to be improved for the company to achieve the desired CMMI certification level. Possible improvements are introduced to the consultant. During the implementation part a web application is realized helping to remove most of the identified imperfections. Application benefit is objectively evaluated by an internal audit. The work includes discussion of possible further application development and quality model standard evolution in this company.
33
Salinas, Távara Mario Josymar. "Integración holística de Scrum en la gestión de proyectos de mejora bajo el marco de Lean Manufacturing." Bachelor's thesis, Pontificia Universidad Católica del Perú, 2020. http://hdl.handle.net/20.500.12404/17385.
Анотація:
El presente trabajo de investigación nace por la necesidad de explicar que las metodologías
actuales en la gestión de proyectos de mejora de procesos pueden adoptar una visión ágil e
integradora; es decir, se debe integrar dos o más metodologías, según la necesidad, y no
restringir a que en un proyecto se debe usar una única metodología. Frente a ello, en esta
investigación se explora la integración de la metodología SCRUM y de Lean manufacturing a
nivel conceptual evaluando una interrelación de herramientas mostrando una afinidad para
generar una metodología sinérgica. Además, se evalúa a nivel práctico, mostrando diferentes
estudios donde ambas metodologías confluyen en un mejor desempeño o desarrollo del
proyecto. Finalmente, se valida la hipótesis planteada ante una vasta revisión de literatura y de
otros trabajos académicos.Trabajo de investigación
34
Santos, Andréa Cristina dos. "Modelo de referência para o processo de desenvolvimento de produtos em um ambiente de SCM." Florianópolis, SC, 2008. http://repositorio.ufsc.br/xmlui/handle/123456789/91863.
Анотація:
Tese (doutorado) - Universidade Federal de Santa Catarina, Centro Tecnológico. Programa de Pós-Graduação em Engenharia Mecânica.Made available in DSpace on 2012-10-24T03:18:57Z (GMT). No. of bitstreams: 1 252100.pdf: 8810345 bytes, checksum: 9b4a050409649ba5593ca0d79dd92e73 (MD5)
Hoje, mais do que no passado, os negócios dependem das relações estratégicas com seus clientes e fornecedores, com o propósito de criar valor ao produto em desenvolvimento e de manter ou melhorar o posicionamento da empresa no mercado. Esta tese apresenta um modelo de referência para o processo de desenvolvimento de produtos, inserindo conceitos, informações e conhecimentos de SCM no PDP, com o propósito de integração e sincronização das tomadas decisões de PDP e SCM. São apresentados três elementos fundamentais para sincronização das decisões do SCM e PDP: 'projeto da' cadeia de suprimentos, 'projeto para' cadeia de suprimentos e arquitetura do produto. Além disso, o detalhamento do modelo de referência envolve o fornecimento de um caminho para o envolvimento dos fornecedores no PDP, por meio das conexões do processo de outsourcing com o PDP. O modelo proposto foi avaliado por especialistas acadêmicos e de empresas, que apontaram a necessidade da existência do desenvolvimento de vários conhecimentos prévios na empresa, para promover a integração do PDP com o SCM. Como resultado deste trabalho, destaca-se a importância dos conhecimentos técnicos, na fase de planejamento estratégico do produto, assim como, a integração de diferentes áreas para integrar e sincronizar as tomadas de decisão do PDP com o SCM. Com isso, este trabalho ressalta novas áreas de pesquisas em que há necessidade de uma maior integração de conhecimentos para se promover novas soluções para os problemas das empresas num ambiente de SCM. Today, more than in the past, businesses depend on strategic relations with their clients and suppliers, in order to give value to a product under development and maintain or improve the position of a company in the market. This thesis presents a reference model for the product development process (PDP), incorporating concepts, information and knowledge from SCM into PDP, with the aim of the integration and synchronization of decision making in PDP and SCM. Three fundamental elements for the synchronization of SCM and PDP decisions are presented: 'design of' the supply chain, 'design for' the supply chain and product architecture. Also, the detailing of the reference model includes providing a way of involving the suppliers in the PDP, through the connection of the outsourcing process with the PDP. The proposed model was evaluated by academic and business specialists, who indicated the need for the development of several areas of prior knowledge in the company, in order to promote the integration of PDP with SCM. As a result of this study, the importance of technical knowledge in the strategic planning phase of the product, as well as the integration of different areas in order to integrate and synchronize the decision making of PDP with SCM, was highlighted. Thus, this study brings to light new research areas in which there is the need for greater integration of knowledge in order to promote new solutions for company problems in an SCM environment.
35
Chipana, Choque Roxana Jessica. "Proceso de desarrollo de software del proyecto de tracking crediticio aplicando la metodología Scrum para el Banco Interbank." Bachelor's thesis, Universidad Nacional Mayor de San Marcos, 2018. https://hdl.handle.net/20.500.12672/10144.
Анотація:
Detalla el desarrollo del proyecto llamado Tracking Crediticio, en el que se implementó un módulo en la web de Banca Empresa para permitir que los clientes puedan consultar sus productos y así resolver los inconvenientes descritos antes. El proceso de desarrollo del proyecto fue realizado siguiendo las pautas y principios de la metodología SCRUM que el área de Transformación Banca Comercial ha venido trabajando desde hace 2 años, uno de los beneficios fue la adaptación constante a cambios en los requerimientos y entrega incremental del producto, obteniendo como resultado un módulo acorde a lo que el cliente final esperaba según la evaluación realizada.Trabajo de suficiencia profesional
36
Castilla, Dalila. "A Hybrid Approach Using RUP and Scrum as a Software Development Strategy." UNF Digital Commons, 2014. http://digitalcommons.unf.edu/etd/514.
Анотація:
According to some researchers, a hybrid approach can help optimize the software development lifecycle by combining two or more methodologies. RUP and Scrum are two methodologies that successfully complement each other to improve the software development process. However, the literature has shown only few case studies on exactly how organizations are successfully applying this hybrid methodology and the benefits and issues found during the process. To help fill this literature gap, the main purpose of this thesis is to describe the development of the Lobbyist Registration and Tracking System for the City of Jacksonville case study where a hybrid approach, that integrates RUP and Scrum, was implemented to develop a major application to provide additional empirical evidence and enrich the knowledge in this under-investigated field.
The objective of this research was fulfilled since the case study was described in detail with the specific processes implemented using RUP and Scrum within the context of the IBM Rational Collaborative Lifecycle Management Solution. The results may help researchers and practitioners who are looking for evidence about conducting a hybrid approach. However, more case studies that successfully combine RUP and Scrum need to be developed in order to have enough empirical evidence.
37
Butkus, Karolis. "CMMI taikymas naudojant judriųjų metodikų praktikas." Master's thesis, Lithuanian Academic Libraries Network (LABT), 2011. http://vddb.laba.lt/obj/LT-eLABa-0001:E.02~2010~D_20110709_152440-76480.
Анотація:
Pagrindinis darbo tikslas ištirti ir aprašyti CMMI antro brandos lygio procesų sričių susiejimą (angl. mapping) su judriųjų metodų praktikomis ir juo remiantis pasiūlyti rekomendacijas, leidžiančias pasiekti CMMI proceso sričių tikslus. Apžvelgus literatūros šaltinius nagrinėjančius CMMI ir judriųjų metodų susiejimo problematiką, identifikuoti egzistuojantys CMMI proceso sričių ir judriųjų metodų susiejimai. Nustatyti susiejimai nėra pilni, dažnai trūksta konkretumo ir detalumo. Todėl buvo suformuoti ir aprašyti CMMI komponentų ir judriųjų metodų veiklų bei artefaktų susiejimo principai, leidžiantys įvertinti, kaip plačiai ir kokiomis judriųjų metodų veiklomis yra padengiamos proceso srities praktikos. Jais remiantis nustatomi ir CMMI tipinių darbo produktų bei judriųjų metodų sukuriamų artefaktų atitikmenys. Tyrimui buvo pasirinkti du judrieji metodai (Scrum ir XP) ir CMMI antrojo brandos lygio proceso sritys. Remiantis aprašytąja metodika, autorius atliko CMMI proceso sričių praktikų susiejimą su pasirinktųjų judriųjų metodų praktikomis. Gauti rezultatai leido įvertinti kiekvienos proceso srities susiejimą ir pateikti rekomendacijas, kaip pasiekti nepilnai arba silpnai padengtų proceso sričių tikslus įtraukiant papildomas veiklas, naudojant papildomus įrankius arba kaip veiklos vykdymo įrodymus sukuriant pagalbinius dokumentus ir ataskaitas.The main goal of this study was to perform a detail mapping of CMMI maturity level 2 practices with agile methods and to write recommendations for achieving process area goals. The review of literature revealed mapping problems between CMMI model components and agile methods. The existing mappings between CMMI and agile methods are incomplete and often do not give enough details. Therefore new mapping principles were described and written by author. They allow to perform mapping between CMMI components and agile methods’ practices and artifacts and to evaluate how largely and which process area practices are covered by agile activities. Two agile methods were selected for research (Scrum and XP). And process areas of the CMMI maturity level 2 were chosen for applying described principles. Detail CMMI practices and agile method activities mapping was done using described method, which revealed least satisfied process area practices. According to the mapping results, the recommendations how to achieve CMMI level 2 were written. They state which activities could be included or what tools could be used in order to achieve process improvement in accordance with CMMI.
38
Sabar, Suneel. "Software Process Improvement and Lifecycle Models in Automotive Industry." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-69640.
Анотація:
The quality of a product depends on the quality of the underlying process is a well known fact. Software development organizations have been struggling to decrease their cost, increase their ROI, reduce time-to-market, and enhance the quality of their products. This all depends upon the improvement in the processes they are following inside their organizations. A number of software process improvement models exist in market, e.g., CMMI, SPICE and Automotive SPICE. But before an organization can improve its development and management processes, it is very important to know whether it is following the right processes. There exist a number of software development process models, mainly categorized into Traditional and Agile, which provide the step-by-step guidance to develop and manage the software projects.The current thesis presents a study of software process improvement models in automotive industry, their weaknesses and strengths and presents a comparison of how do they relate to each other. This thesis also explores some software development models which are more famous in automotive industry, and the applicability of process improvement models in conjunction with the Agile software development models. A case study was performed at an automotive software supplier organization to investigate the experience of combining Agile practices with organization’s company-tailored software development model that was incorporating Automotive SPICE standards.
39
Vera, Valdivia Abel. "Estrategia Corporativa de YOBEL SCM para la Optimización y Estandarización de Procesos de Manufactura en Chile." Tesis, Universidad de Chile, 2008. http://www.repositorio.uchile.cl/handle/2250/101988.
Анотація:
Yobel SCM empresa dedicada a la maquila de cosméticos, transformaciones y servicios logísticos en Latinoamérica ha determinado que los centros de manufactura en la región necesitan estandarizar y optimizar sus procesos, motivado principalmente por una diferencia entre la casa matriz y las filiales, estas últimas evidenciando una falta de control de gestión en los procesos y por los mercados cada vez más competitivos.
El objetivo general de este trabajo es alcanzar una operación de manufactura de clase mundial superior o al menos similar a sus pares en el resto de Latinoamérica, que contemple la implementación de indicadores de gestión y su aplicabilidad en los procesos productivos de la filial chilena, vinculando el objetivo de esta tesis a la estrategia corporativa de la compañía.
Para este estudio la metodología consiste en implementar los indicadores de gestión corporativos con la finalidad de medir los procesos actuales, posteriormente realizar el análisis de brechas, así como el análisis y selección de las alternativas de solución que disminuya las diferencias encontradas. Luego realizar el plan de implementación de la alternativa de solución para finalmente hacer el respectivo análisis relación costo – beneficio que permita acortar las diferencias entre los indicadores de gestión de la corporación y Chile, todo esto dentro del marco de los factores críticos de éxito (FCE) como son el apoyo de la gerencia, nivel de compromiso de los actores del proyecto, restricciones presupuestarias, factores culturales, tamaños de operación, infraestructura entre otros.
Se concluye que se cumplieron los objetivos y alcances del estudio, en los primeros meses de implementación se observa un comportamiento positivo en los indicadores de gestión respecto al benchmarking corporativo, los cuáles han subido en promedio 7 puntos porcentuales respecto a la realidad encontrada; se estimó la inversión para las mejoras en $5773000 pesos que se recupera en 13 meses.
Sin embargo este proceso no fue sencillo debido a los FCE como la resistencia al cambio, diferencias tecnológicas las que fueron superadas con trabajos en equipo, capacitación, gestión del cambio; así estas mejoras deben ser analizadas desde las perspectivas de personas, procesos y tecnología para superar dichos obstáculos.
40
Silva, Alexandre Machado. "Padrão de qualidade de software de apoio ao gerenciamento de projetos SCRUM em um cenário de desenvolvimento distribuído de software." Universidade de Fortaleza, 2011. http://dspace.unifor.br/handle/tede/87750.
Анотація:
Made available in DSpace on 2019-03-29T23:27:42Z (GMT). No. of bitstreams: 0
Previous issue date: 2011-09-12As far as software development is concerned, we normally think about which models can be used in order to make the process the most effective we can get. Yet, when we need to develop software together with groups of makers who are in geographically separated environments, the possibility of possible problems tend to increase considerably. So, a question immediately comes out: How can we join these two situations with the guarantee of the effectiveness in the process of software development? Aiming to help solve such a problem, we present in this paper a study of quality of evaluation of the products to development of software using the SCRUM framework. Trying to help the development of the tool, or on the process of evaluation of the tolls that already exist, this paper uses the ranking for factor or sub-factor goals to identify and rate the quality attributes of greater importance for this specific situation. The results of the qualities were based on specific literature, as well as in analyses of some existing software in the market, and also the help of some professionals who use DDS, SCRUM or both of them. It was also made a field survey, together with professionals who manage projects, system analysts, program writers, customers, product owners, professors, scrummasters and web designers, trying to rate these quality attributes, which results were conquered through the evaluation of software quality. The study and the analyses for the development set standards for tools to support project management SCRUM scenario distributed software development. Keywords: Software, Software Engineering, Software Development, Scrum, Distributed Software Development.
Quando o assunto é desenvolvimento de software pensamos logo em quais modelos podem ser utilizados a fim de que o processo de construção seja o mais eficiente possível. Porém, quando necessitamos desenvolver software com grupos de desenvolvedores que estão em ambientes geograficamente distribuídos, as variáveis de possíveis problemas tendem a aumentar consideravelmente. Então vem logo à pergunta: como associar estas duas realidades garantindo a eficiência no processo de desenvolvimento de software? Com o intuito de ajudar a equacionar tal problema, apresentamos neste trabalho um estudo de avaliação da qualidade dos produtos para desenvolvimento distribuído de software usando o framework SCRUM. Com o intuito de definir um padrão de qualidade para ferramentas de apoio a gerência de projetos SCRUM no cenário DDS, este trabalho usa a classificação por objetivos fatores e subfatores a fim de identificar e hierarquizar atributos de qualidade de maior importância para este domínio de aplicação. O levantamento dos atributos foi baseado em literatura especializada, bem como na análise de alguns softwares existentes no mercado, e auxílio de profissionais que utilizam DDS (Desenvolvimento Distribuído de Software), SCRUM ou os dois. Foi realizada, ainda, uma pesquisa de campo, junto a profissionais que são gerentes de projetos, analistas de sistemas, programadores, clientes, product owners, professores, scrum másters e web designers, visando à hierarquização desses atributos de qualidade, cujos resultados foram obtidos através de um modelo de avaliação da qualidade de software. O estudo e análise desses resultados fornecem subsídios para a definição de um padrão de qualidade para ferramentas de apoio a gerência de projetos com o uso do framework SCRUM em cenários de desenvolvimento distribuído de software. Palavras-chave: Software, Engenharia de software, Desenvolvimento de software, SCRUM, Desenvolvimento Distribuído de Software.
41
THATTE, ASHISH A. "Competitive Advantage of a Firm through Supply Chain Responsiveness and SCM Practices." University of Toledo / OhioLINK, 2007. http://rave.ohiolink.edu/etdc/view?acc_num=toledo1176401773.
42
Puchnar, Michal. "Posouzení informačního systému firmy a návrh změn." Master's thesis, Vysoké učení technické v Brně. Fakulta podnikatelská, 2017. http://www.nusl.cz/ntk/nusl-319217.
Анотація:
This thesis is focused on analyzying of the information system in comapany Tirad s.r.o. which uses information system Workplan. Theoretical part is focused on problematics of information systems in general, it defines the methods for analysis of information system effectiveness. We are going to use systems Zefis and HOS 8. Based on these methods are discovered weaknesses and are proposed possible solutions for improving of information system effectiveness which leads to increasing of company performance and threads elimination.
43
Cabrera, Diaz Diego Alonso. "Implementación de un proceso en el sistema de cobranza para reducir costos operativos en una entidad aseguradora aplicando metodología SCRUM." Bachelor's thesis, Universidad Nacional Mayor de San Marcos, 2021. https://hdl.handle.net/20.500.12672/17035.
Анотація:
El presente trabajo de suficiencia profesional va orientando al desarrollo de software cuyo
principal objetivo fue reducir costos por pago de comisión a un operador externo por cargo al débito
automático en una Entidad Aseguradora. Se realizó mejoras a los procesos de afiliación y cobros
y se implementó un nuevo proceso de migración en conjunto con el área de Operaciones para
enviar los cargos de las pólizas en producción afiliadas a VISA, logrando enviarlas directamente
al BCP. Para implementar la solución se utiliza la metodología Scrum y buenas prácticas del
mundo ágil con la conformación de un equipo multidisciplinario, en este caso la célula de
Cobranzas, al tener mucha incertidumbre en la definición inicial y al ver que se podía realizar
entregas de manera incremental. El resultado luego del despliegue permitió un ahorro
considerable en costos, reducción de carga operativa e incrementos de intentos de cobro al BCP
por ser un aliado estratégico logrando la satisfacción del negocio y el usuario final.
44
Gon?alves, Marcus Vin?cius Guedes. "O uso da metodologia ?gil como processo de desenvolvimento participativo de sistemas." PROGRAMA DE P?S-GRADUA??O EM DESIGN, 2017. https://repositorio.ufrn.br/jspui/handle/123456789/25022.
Анотація:
Submitted by Automa??o e Estat?stica (sst@bczm.ufrn.br) on 2018-04-02T15:49:18Z
No. of bitstreams: 1
MarcusViniciusGuedesGoncalves_DISSERT.pdf: 4727721 bytes, checksum: 2e8bf3d5496323f84a56936afa519116 (MD5)Approved for entry into archive by Arlan Eloi Leite Silva (eloihistoriador@yahoo.com.br) on 2018-04-09T20:52:05Z (GMT) No. of bitstreams: 1 MarcusViniciusGuedesGoncalves_DISSERT.pdf: 4727721 bytes, checksum: 2e8bf3d5496323f84a56936afa519116 (MD5)
Made available in DSpace on 2018-04-09T20:52:05Z (GMT). No. of bitstreams: 1 MarcusViniciusGuedesGoncalves_DISSERT.pdf: 4727721 bytes, checksum: 2e8bf3d5496323f84a56936afa519116 (MD5) Previous issue date: 2017-06-15
No contexto em que a equipe de desenvolvimento do SIGRH est? inserida, em que a quantidade de solicita??es por novas melhorias ? bem maior que a capacidade de entrega, ? necess?ria a ado??o de um processo que priorize o que venha aumentar o m?ximo poss?vel o valor do sistema. Utilizar um processo com excesso de formalidade pode diminuir a velocidade de progresso do projeto. Por outro lado, a falta total de formalidade n?o garante que os objetivos do projeto sejam alcan?ados. Uma metodologia de desenvolvimento ?gil como o Scrum, consegue atender a esses requisitos, com entregas frequentes, resultando no aumento da satisfa??o dos clientes, e melhorias no comprometimento, motiva??o, colabora??o e troca de conhecimento entre os membros da equipe de desenvolvimento. O objetivo deste trabalho foi descrever o processo de implanta??o do Scrum e, aplicando-se t?cnicas de design participativo, a cria??o e utiliza??o de uma ferramenta para apoiar as atividades segundo as pr?ticas do Scrum, possibilitando o registro colaborativo das informa??es, facilitando o acompanhamento do progresso por toda a equipe e auxiliando na gest?o do projeto.
In a context in which the development team is not able to deliver the amount of requests for new improvements, a process that prioritizes what will add maximum possible value for the system is desired. Using a process with too much formality can slow the progress of the project. On the other hand, the total lack of formality does not ensure that project objectives are met. An agile development methodology such as Scrum can meet these requirements, with frequent deliveries, resulting in increased customer satisfaction, and improvements in commitment, motivation, collaboration and knowledge exchange among the development team. The objective of this paper was to describe the Scrum implementation process and, using participatory design techniques, the build and use of a tool to support activities according to Scrum practices, enabling the collaborative registration of information, facilitating the monitoring of progress by the entire team and assisting in project management.
45
Škramlík, Jan. "Solution Delivery Process Framework for BMC Remedy Products." Master's thesis, Vysoká škola ekonomická v Praze, 2015. http://www.nusl.cz/ntk/nusl-193121.
Анотація:
The goal of this thesis is creation of methodology for repeatable transformation of customer business needs and goals resulting from company IT strategy to system functionality and process implementation in Business/IT Service Management projects using BMC Atrium and Remedy products. This methodology will be based on existing project management methodologies PRINCE2 and SCRUM. In the thesis I also refer to parts of ITIL v3 process framework. The aim of the thesis is to provide a project delivery framework for IT Consultancy organizations. The framework will foster efficient planning, tracking and communication of requirements and deliverables between IT Consultancy and their customer during entire project lifecycle and will therefore enable repeatable and consistent high quality delivery of customer success.
46
Durand, Lino Martín Alonso. "Desarrollo de una aplicación móvil bajo la metodología SCRUM, para optimizar el proceso de venta en una empresa de telecomunicaciones: año 2017." Bachelor's thesis, Universidad Nacional Mayor de San Marcos, 2021. https://hdl.handle.net/20.500.12672/16989.
Анотація:
En el Perú, el proceso de venta en toda empresa en la actualidad siempre viene
acompañado de un sistema eficiente, rápido y robusto, el cual debe soportar la mayor
cantidad de interacciones en simultáneo sin presentar problemas de intermitencia y que
este sea de fácil uso para el usuario. Teniendo en cuenta estos puntos, el área de Ventas
de una empresa de telecomunicaciones, en el 2016, realiza un estudio sobre los
problemas que se presentan en los Distribuidores Autorizados a nivel nacional, ya que
notaron que no aumentaba el número de ventas mensuales. En base a estos resultados,
el área planteó nuevas estrategias para captar más clientes. Dentro de estas, se planteó
desarrollar una Aplicación Móvil bajo el sistema operativo Android, la cual cumpla con 3
principales características: eficiencia, velocidad y robustez. A mediados del 2016 se
inician los desarrollos de la aplicación, y ya que se necesitaba de un entregable en el
menor tiempo posible y bajo los estándares de arquitectura en la empresa, se optó por el
uso de la metodología de desarrollo SCRUM, y para la capa de integración se diseñó bajo
la arquitectura SOA (On-Premise). Esta aplicación permitió brindar una mejor experiencia
de usuario, tanto que por este nuevo sistema actualmente pasa el 70% de las ventas.
47
Gustafson, Anders. "Interna flöden och processer på Å&R Carton : processbaserad verksamhetsanalys och förbättringsförslag för ledtidsreduktion." Thesis, Linköping University, Department of Science and Technology, 2003. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-2141.
Анотація:
Denna rapport syftar till att, på Å&R Carton i Norrköping, analysera de interna flödena och processerna samt ge förslag på hur ledtider ska kunna reduceras väsentligt. Ett sätt att uppfylla syftet är att dela in verksamheten i processer genom olika metoder och kriterier förprocessbestämning. Valda metoder i rapporten är; kvalitativ ansats med hög validitet och reliabilitet, processbaserad verksamhetsanalys och procedurbeskrivning.
Genom omfattande litteraturstudier, insamlande av data i form av intervjuer, benchmarking, platsundersökningar och interna dokument har nulägesmodeller arbetats fram. Analysen av dessa visar bland annat på att såväl planeringsprocessen som inköpsprocessen idag inte fungerar värdeadderande och bör ses över. Därutöver finns också andra processer som bidrar till ett komplext flöde. Dessa behöver effektiviseras eller ändras för att korta ledtider. Vidare visar analysen på att en omfattande attitydsundersökning behövs, dels för att komma till rätta med vissa stämningar och dels för att på sikt skapa en effektiv arbetsmiljö.
Till förbättringsförslagen hör, förutom en attitydsundersökning, förslaget att utarbeta tydliga mål och strategier. Sedan måste dessa kommuniceras till samtliga anställda, till exempel genom arbetsgrupper. Vidare föreslås att Å&R Carton tittar på automatisk datafångst som ett mycket kostnadseffektivt sätt att kontrollera det totala flödet. På lång sikt bör också företaget titta på att implementera processorientering. Dock behöver företaget först och främst se till att skapa en förändringsvillig attityd för att nå framgång i sitt effektiviseringsarbete. Slutsatsen blir att Å&R Carton har stor potential att väsentligt förkorta sina ledtider om företaget hanterar situationen rätt. För att lyckas kan delar av denna rapport användas där det viktigaste är att en engagerad ledning visar vägen.
The purpose of this final thesis is to analyse the internal processes at Å&R Carton in Norrköping and give proposals to reduce time in the Supply Chain. One way to fulfill the purpose is to use Process Based Analys and split the organisation in different processes. Process Based Models have then been constructed by studying litterature, benchmarking, internal documents and making a lot of interviews. The analys shows that different processes must be changed to make the flow through the Supply Chain more efficient. The analys give us also recommendations like attitude investigations and implementation of ECR. The conclusion is that Å&R Carton have great potential to reduce time in the Supply Chain if the management are active, follow the recommendations and show the employees the way about.
48
Kanprachar, Surachet. "Modeling, Analysis, and Design of Subcarrier Multiplexing on Multimode Fiber." Diss., Virginia Tech, 2003. http://hdl.handle.net/10919/26744.
Анотація:
This dissertation focuses on the use of subcarrier multiplexing (SCM) in multimode fibers, utilizing carrier frequencies above what is generally utilized for multimode fiber transmission, to achieve high bit rates. In the high frequency region (i.e., frequencies larger than the intermodal bandwidth), the magnitude response of multimode fiber does not decrease monotonically as a function of the frequency but is shown to become relatively flat (but with several deep nulls) with an amplitude below that at DC. The statistical properties of this frequency response at high frequencies are analyzed. The probability density function of the magnitude response at high frequencies is found to be a Rayleigh density function. The average amplitude in this high frequency region does not depend on the frequency but depends on the number of modes supported by the fiber. To transmit a high bit rate signal over the multimode fiber, subcarrier multiplexing is adopted. The performance of the SCM multimode fiber system is presented. The performance of the SCM system is significantly degraded if there are some subcarriers located at the deep nulls of the fiber. Equalization and spread spectrum techniques are investigated but are shown to be not effective in combating the effects of these nulls. To cancel the effects of these deep nulls, training process and diversity coding are considered. The basic theory of diversity coding is given. It is found that the performances of the system with training process and the system with diversity coding are almost identical. However, diversity coding is more appropriate since it requires less system complexity. Finally, the practical limits and capacity of the SCM multimode fiber system are investigated. It is shown that a signal with a bit rate of 1.45 Gbps can be transmitted over a distance up to 5 km.Ph. D.
49
Díaz, Vergara Pablo Andrés. "Caso de negocio: Implementación de metodología ágil en el proceso de mejora de requerimientos e incidencias sistémicas en una empresa de retail financiero." Tesis, Universidad de Chile, 2019. http://repositorio.uchile.cl/handle/2250/170635.
Анотація:
Tesis para optar al grado de Magíster en Gestión y Dirección de EmpresasEl objetivo de este caso de negocio, es apoyar la implementación de la Metodología Ágil, específicamente Scrum en una empresa del Retail Financiero en Chile (CMR-Falabella). Se espera, que, a través de este trabajo, se oriente a la empresa en la elección de su portafolio de mejoras y requerimientos de TI, como también, la aplicación de Scrum, en el trabajo diario de sus necesidades y mejoras de los procesos de apoyo al negocio. La información y datos entregados, será levantado de las áreas de operaciones y sistemas como del negocio de CMR-Falabella, para lo cual, se realizó entrevistas con expertos de Ti como así mismo personas claves de recursos humanos y del negocio. CMR-Falabella, siempre ha entregado soluciones fáciles y rápidas para sus clientes, por lo cual, se hace necesario un alineamiento y oportunidad en el área de TI, con respecto a mejoras y revisiones de cómo se están realizando las cosas actualmente. Se realizará un levantamiento de la metodología clásica v/s la metodología ágil propuesta (Scrum), lo que llevará a identificar y cuantificar, a través de métricas, el valor que Scrum entregará a la organización, con respecto a las entregas y puestas en producción de los desarrollos por parte del área de sistemas. Sin duda un factor importante, es la colaboración del área de Recursos Humanos, que, a través, de su oficina de Gestión de Cambio, impulsará, comunicará y motivará a cada uno de los integrantes de la organización, como a los equipos de la Célula a enfrentar esta nueva forma de hacer las cosas, todo esto alineados con los valores de CMR-Falabella. Es un gran desafío de cambiar los paradigmas, con entregas parcializadas a los clientes, que aportan un valor a la organización, con definiciones que se irán enriquecerán en cada sprint, que permitirá generar ahorros y un Time to Market anual (MM$623), que, ayudará con los resultados y a mantener los lineamientos con los objetivos planteados, entregando beneficios en tiempos más cortos. El trabajo en equipo comienza desde un inicio, como así mismo el trabajo colaborativo y la autogestión de los integrantes es fundamental en cada una de las etapas de la metodología Scrum, los resultados se ven cada 10 días, lo que permite innovar en cada definición y no esperar hasta la entrega final.
50
Žideckas, Egidijus. "Tiekimo proceso kontrolės metodų analizė ir taikymas kuriant informacinę sistemą." Master's thesis, Lithuanian Academic Libraries Network (LABT), 2004. http://vddb.library.lt/obj/LT-eLABa-0001:E.02~2004~D_20040527_154217-86410.
Анотація:
An overall process of globalization influences major changes in companies’ bussiness strategy. Supply chain management (SCM) becomes one of the most prioritetical activities in company. Seeking to survive in hard competition, they must improve their distribution strategies. Spreading Net technology requires flexible company to work directly with suppliers and to be able to react quickly and reasonably to demanding environmental changes. The classic objective of SCM is to be able to have the right products in the right quantities (at the right place) at the right moment at minimal cost. This requires a close integration of effective control functions and SCM to assure correctness and maturity of sending and receiving information, complience with internal company rules and supply strategies. This paper analyses SCM information systems emphasising their principles, pecularities and weaknesses. A new control method of SCM is introduced — „SCM using complex control methods“. It adds content management principles to current SCM control methods. This paper describes system concept, system architecture and generic business process models. To prove effectiveness of this method software was designed, developed and implemented in one big trading company. Additionally quality research of implemented software was made and it showed the effectiveness of applying quality assurence in software implementation process.