Um die anderen Arten von Veröffentlichungen zu diesem Thema anzuzeigen, folgen Sie diesem Link: Agil modell.
Dissertationen zum Thema „Agil modell“
Geben Sie eine Quelle nach APA, MLA, Chicago, Harvard und anderen Zitierweisen an
Machen Sie sich mit Top-50 Dissertationen für die Forschung zum Thema "Agil modell" bekannt.
Neben jedem Werk im Literaturverzeichnis ist die Option "Zur Bibliographie hinzufügen" verfügbar. Nutzen Sie sie, wird Ihre bibliographische Angabe des gewählten Werkes nach der nötigen Zitierweise (APA, MLA, Harvard, Chicago, Vancouver usw.) automatisch gestaltet.
Sie können auch den vollen Text der wissenschaftlichen Publikation im PDF-Format herunterladen und eine Online-Annotation der Arbeit lesen, wenn die relevanten Parameter in den Metadaten verfügbar sind.
Sehen Sie die Dissertationen für verschiedene Spezialgebieten durch und erstellen Sie Ihre Bibliographie auf korrekte Weise.
1
Hamed, Amirzadeh, und Khalaf Beigi Reza. „Agil Systemutveckling : En studie av kravhantering och beställarroll i agila angreppsätt“. Thesis, Högskolan Väst, Institutionen för ekonomi och it, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:hv:diva-5510.
Der volle Inhalt der QuelleAnnotation:
This paper is a degree project on the C-level, 15 points at University West, Department of Business and IT dept. Informatics. This study is about agile methodology and its impact on IT projects. Requirements management is a process within an IT project, where customer has certain requirements that must be met by an IT system. The difference between the traditional and agile development is in the requirements management process and it can cause problems in a project. Requirements change during IT projects and to manage requirements, agile principles apply. Specification and planning in the waterfall model is time consuming. Working agile means to have close contact with the client. This minimizes the risk of project failure. With agile methods, functions can be developed at a faster rate and the customer receives prompt delivery. There are currently several different methods for systems development and project management. Some are based on research, others are new and some have been around a long time in the IT world. This work has identified customer involvement; Risk Reduction and Delivery which contribute to several projects fail under traditional systems. Agile methods are flexible, agile and welcome change and the customer will be able to steer the project. Agile methods have however provided the opportunity for developers to more quickly deliver functionality to the customer.Detta arbete är ett examensarbete på C-nivå, 15 poäng vid Högskolan Väst, Institutionen för ekonomi och IT avd. informatik. Denna studie handlar om agila metodiken och dess inverkan på IT-projekt. Kravhantering är en process inom ett IT-projekt, där kund har vissa krav som måste uppfyllas av ett IT-system. Skillnaden mellan det traditionella och agila utvecklingsmetoder ligger i kravhantering process och det kan orsaka problem i ett projekt. Krav förändras under IT-projekt och för att hantera kraven bör agila principer tillämpas. Kravspecifikation och planering inom vattenfallsmodellen är tidskrävande. Att jobba agilt innebär att ha nära kontakt med beställaren. Därmed minimerar det risken för projektets misslyckande. Med agila metoder, kan funktionerna utvecklas i en snabbare takt och kunden får snabb leverans. Det finns idag flera olika metoder för systemutveckling och projektledning. Vissa är baserade på forskning, andra är nya och vissa har funnits en lång tid i IT-världen. Arbetet har identifierat kundinvolvering, Riskreducering och Leveranstid vilka bidra till att flera projekt misslyckas under traditionell systemutveckling. Agila metoder är flexibla, smidiga och välkomnar förändring och kunden kommer att kunna styra projektet. Agila metoder har däremot gett möjlighet för utvecklarna att på ett snabbare sätt leverera funktioner till kunden.
2
Anderzon, Samuel, und Filip Davidsson. „Agile Practices in Production Development : Investigation of how agile practices may be applied in a production development context and what the expected effects are“. Thesis, Jönköping University, JTH, Produktionsutveckling, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-53736.
Der volle Inhalt der QuelleAnnotation:
Globalization has continuously brought an increased competition among companies, which entails a need for faster and more frequent deliveries of new products. Traditional project management methods, such as stage-gate and waterfall, are commonly used in production development projects and builds on a sequential approach. These methods have proven to have some disadvantages in flexibility, long lead times and it often creates communication barriers between the actors at each stage. The software industry has already encountered these obstacles and responded by introducing agile project management. Which improves the adaptability and allow changes to be made, due to new requirements from stakeholders or customers, throughout the entire development process. However, it remains unknown how agile models can improve production development. The purpose of this study was therefore to investigate how agile models can be applied to production development and what the effects are. The authors have performed a case study at eight different companies within the automotive industry. The purpose of it has been to gain a deeper understanding about the case companies current production development processes and review how familiar the organizations are with the concept of agile project management. The extraction of the empirical data was conducted by questionnaires, interviews, and document reviews. An analyzation was done by comparing the empirical findings with the theoretical background out of eleven different categories that relates to project management (e.g., project goals, process, customer integration etc.). The analyzation concluded that the case company exclusively conducts their production development project by using a sequential approach. The analyzation and the eleven categories where, together with the theoretical background about agile project management, later used to create the result by brainstorming different practices to become more agile. The results are presented out of three different scenarios, depending how agile the companies would like to be. For instance, are two process models suggested, one that is completely agile and one that is a hybrid of an agile and a stage-gate. Furthermore, are the implementation of self-organized teams, holistic approach towards internal and external partners, and reduced demand for documentation some of the practices that are suggested. Additionally, are three considerable aspects for the implementation presented. The expected outcome and effects of applying these practices are discussed in the final chapter. Some of these outcomes are a company culture that will attract and retain talented personnel, where shared responsibilities and authorities triggers the employees to an increased commitment and sense of ownership towards their projects. Furthermore, are the companies expected to experience a more flexible and responsive approach towards conducting production development projects with a high focus on customer requirements and creating customer value.
3
Cosic, Admir, und Michel Antonio. „Processförbättring med hjälp av TMMi-Modellen : Utvärdering av en testprocess på ett medelstort företag“. Thesis, Linnéuniversitetet, Institutionen för datavetenskap, fysik och matematik, DFM, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-22385.
Der volle Inhalt der QuelleAnnotation:
Storleken och komplexiteten på dagens system och applikationer ökar. Detta leder till att kraven på system och applikationer ökar också eftersom kunderna kräver av dagens system full funktionalitet inom olika typer av distribuerade miljöer. Kunder är inte bara intresserade av funktionerna i systemen och applikationerna, de förväntar sig också att systemet skall vara av god kvalitet. Av dessa skäl är det mycket viktigt att testa system och applikationer för att säkerställa att de uppfyller kundernas förväntningar. Däremot är det inte bara själva mjukvarans kvalitets frågor som organisationer behöver ha i åtanke, en lika viktig del är själva testprocessens kvalitet. För att öka testprocessens kvalitet krävs det en utvärdering av processen. Utvärderingen identifierar processens styrkor, svagheter och möjligheter. I detta examensarbete har vi utvärderat tesprocessen på ett utvecklingsföretag. Utvärderingen har baserats på anvisningar och rekommendationer från TMMi-modellen, Test Maturity Model Integrated. Vi hade som mål att lyfta fram förbättringsförslag till företagets testprocess. Efter utvärderingen kom vi fram till vilken mognadsnivå verksamheten utifrån TMMi-modellen samt en mängd förbättringsförslag för att höja mognadsnivån på testprocessen.
4
Lundgren, Sara, und Tove Lundkvist. „Mystiken kring överlämningen i den agila projektmodellen : Svenska bankers upplevelse av överlämningen av en produkt och dess konsekvenser“. Thesis, Linköpings universitet, Företagsekonomi, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-158455.
Der volle Inhalt der QuelleAnnotation:
Bakgrund: Den agila projektmodellen har under de senaste två decennierna vuxit fram som en utmanare till den traditionella vattenfallsmodellen. En av de stora skillnaderna mellan projektmodellerna är att i det agila arbetssättet involveras kunden kontinuerligt. Frågan är vad som då händer med överlämningen av den sista versionen av produkten, när utvecklingen är färdig? Samtidigt har bankbranschen på senare år utmanats av nya aktörer vilka profilerar sig som just digitala och IT-inriktade, och både dessa moderna banker såväl som de traditionella storbankerna har anammat det agila arbetssättet för att kunna konkurrera om kundernas uppmärksamhet. Dessa banker arbetar inte agilt till lika hög grad, och frågan är om överlämningen påverkas av det? Syfte: Syftet med studien är att öka förståelsen för hur överlämningen av det slutliga projektresultatet i agila projekt ser ut på svenska banker. Vidare ska studien undersöka om den skiljer sig mellan banker med olika agil mognad samt vilka konsekvenser som kan uppkomma i samband med överlämningen. Genomförande: Studien är genomförd som en flerfallstudie där två fall - storbanker och nischbanker, undersöks. Vidare har en fenomenologisk ansats och ett kvalitativt angreppssätt använts. Empirin har samlats in genom ett målstyrt urval varpå semistrukturerade intervjuer har genomförts med tio projektledare. Slutsats: Studien resulterar i slutsatsen att en överlämning av en slutlig produkt i agila projekt inte genomförs på ett formellt sätt, till skillnad från vad teorin tidigare har antytt. I synnerhet lämnar aldrig ansvaret för produkten någonsin det team som har utvecklat den. Vidare visar studien att storbanker arbetar med en lägre grad av agil mognad än vad nischbanker gör, men att detta inte påverkar hur överlämningen ser ut. Slutligen bidrar studien till insikter om konsekvenser kring att överlämningen inte existerar på ett formellt sätt. Detta leder till en reflektion kring att organisationer behöver anpassa sin agila projektmetodik till sin egen kontext. Projektledare generellt bör dessutom fundera över hur organisationens arbetssätt påverkar organisationen i stort samt vara medveten om de konsekvenser som dyker upp vid förändringar i arbetssättet.Background: During the last two decades, the agile project methodology has grown as a competitor to the more traditional waterfall methodology. One of the biggest differences is, with an agile methodology the customer is involved throughout the project. But what happens in the final handover, when the development is finished? At the same time, the Swedish banking industry has been challenged by new actors whom profile themselves as digital focused and IT centred. Both types of banks have developed an agile way of working to be able to compete about the customers. However, the two types of banks does not work agile with the same maturity, and we wonder if the handover is affected by that? Purpose: The purpose of the study is to increase the understanding of what the handover of the final product in agile projects at Swedish banks looks like. Further, the study will examine if the handover differ between banks with different agile maturity, and which consequences that may arise in connection to the handover. Completion: The study was conducted as a multiple-case study in which two cases - traditional banks and specialised banks were examined. Further, a phenomenological and a qualitative approach has been used. The empirical data has been conducted through a targeted selection, where semi-structured interviews have been held with ten project leaders. Conclusion: The study concludes that the handover of the final product in agile projects does not exist in the formal way previous research has suggested. Specifically, the responsibility of the product does never leave the team developing it. Further, the study show traditional banks work with a lower degree of agile maturity in comparison to specialised banks. However, this does not affect the characteristics of the handover. Finally, the study contributes to insights about the consequences of the handover not being as formal. This contributes to a discussion about the need for organisations to be able to adapt their agile methodology to their own context. In general, project leaders also should reflect upon how their way of working affect the organisation as a whole, as well as being aware of the consequences that appears when changing the organisation’s way of working.
5
Tamari, Matteo. „Scrum e Kanban: framework e strumenti di supporto. Prospettive di applicazione nel progetto Agile methods for Agile working“. Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2020. http://amslaurea.unibo.it/22159/.
Der volle Inhalt der QuelleAnnotation:
Da anni ormai, specialmente nel campo dell'ingegneria del software, vengono utilizzati modelli e framework Agili per lo sviluppo software. Essi hanno cambiato radicalmente il concetto di produzione, portandola a un livello più alto sia in termini di velocità rispetto alla consegna sia di qualità del prodotto consegnato; inoltre, tali modelli e framework vengono oggigiorno applicati anche al di fuori dello sviluppo software e questo dimostra che il loro impiego non ha limiti e barriere. In questo elaborato vengono presentati due tra i più conosciuti: Scrum e Kanban. Lo studio approfondito di entrambi ha permesso di cogliere i campi nei quali uno si applica meglio dell'altro, a seconda del contesto (natura della committenza, numero dei membri e background del team, dimensione del progetto, etc.) nel quale il prodotto richiesto si trova e degli strumenti dei quali Scrum e Kanban dispongono, come la "board", sia fisica sia virtuale. In riferimento a tali strumenti viene trattato dettagliatamente il funzionamento di Jira Software, il quale consente di migliorare la produttività dei team che collaborano anche a distanza, integrando perfettamente i modelli e framework Agili al suo interno. Successivamente, viene illustrata un’applicazione dei modelli Agili al di fuori dello sviluppo software; tale applicazione si divide in tre principali fasi: inception, construction e validation. In particolare, viene descritta come è stata affrontata la fase di inception, che consiste di un’analisi approfondita allo scopo di comprendere lo stato attuale del team, ovvero gli strumenti utilizzati, le metodologie applicate, la gestione delle commesse e dei servizi esterni, con il fine ultimo di far comprendere i vantaggi dati dall'essere Agili e di trasmetterli nei processi lavorativi che ogni elemento svolge ogni giorno sul posto di lavoro.
6
Deekonda, Rahul, und Prithvi Raj Sirigudi. „Assessment of Agile Maturity Models : A Survey“. Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-13230.
Der volle Inhalt der QuelleAnnotation:
Context. In recent years Agile has gained lots of importance in the fieldof software development. Many organization and software practitioners hasalready adopted agile practice due to its flexibility in nature. Hence, agiledevelopment methodologies have been replaced to traditional developmentmethods. Agile is a family of several methodologies namely Scrum. eXtremeprogramming (XP) and several others. These several methods areembedded with different set of agile practices for the organizations to adoptand implement for their development process. But there is still a need forempirical research to understand the benefits of implementing the Agilepractices which contributes to the overall success of accomplishment of thesoftware project. Several agile maturity models have been published over adecade but not all of the models have been empirically validated. Hence,additional research in the context of agile maturity is essential and needed. Objectives. This study focus on providing a comprehensive knowledgeon the Agile Maturity Models which help in guiding the organizations regardingthe implementation of Agile practices. There are several maturitymodels published with different set of Agile practices that are recommendedto the industries. The primary aim is to compare the agile maturity maturitymodels and to investigate how the agile practices are implemented inthe industry Later the benefits and limitations faced by the software practitionersdue to implementation of agile practices are identified. Methods. For this particular research an industrial survey was conductedto identify the agile practices that are implemented in the industry. Inaddition, this survey aims at identifying the benefits and limitations of implementingthe agile practices. A literature review is conducted to identifythe order of agile practices recommended from the literature in agile MaturityModels. Results. From the available literature nine Maturity Models have beenextracted with their set of recommended agile practices. Then the resultsfrom the survey and literature are compared and analyzed to see if thereexist any commonalities or differences regarding the implementation of agilepractices in a certain order. From the results of the survey the benefitsand limitations of implementing the Agile practices in a particular order areidentified and reported. Conclusions. The findings from the literature review and the survey resultsin evaluating the agile maturity models regarding the implementationof agile practices.
7
Lindgren, Linus. „Agile product development for integrated suppliers : A qualitative case study on the challenges of developing internal product development practices for an integrated supplier“. Thesis, KTH, Skolan för industriell teknik och management (ITM), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-278864.
Der volle Inhalt der QuelleAnnotation:
Product development has become essential in today’s technology driven marketplace. Currently, pointbased models such as the stage-gate model are applied in practice of several incumbent firms in the automotive industry. However, stage-gate models have been criticized for being too linear and plan focused as external pressures and internal complexity demand for faster and more flexible development, such as agile development. Although product development has a central role in the success of a firm, suppliers play a central role in helping firms achieve their product development goals. As a result, firms may undertake suppler development and integration initiatives to ensure quality and efficiency at the supplier. Utilizing supplier integration has shown positive effects on several performance outcomes. However, limited research on the effects of suppliers being integrated to deficient development practices has been published. Firms that integrate suppliers into point-based, documentation heavy processes could therefore potentially hinder internal development of flexible practices. Therefore, the aim of this study is to investigate how supplier integration challenges suppliers in adopting agile methods in product development and how these challenges can be addressed. This study is based a qualitative, exploratory case study approach, including 13 interviews with various stakeholders within the case company together with extensive data from observations. The empirical data in combination with theories on agile development, traditional development, and supplier integration resulted in a proposition for adopting agile development approaches for integrated suppliers being locked-in to traditional development models. The findings indicate that integrated suppliers may face challenges in adopting agile methods due to requirements from the integrating firm on using traditional development methods. However, a possibility to utilize agile practices on the microperspective while retaining traditional development methods on the macro-perspective through a hybrid model enables adoption of agile methods for integrated suppliers. Although the possibility to adopt agile methods exist, the methods yield little benefits unless an agile leadership and vision is established. Therefore, a transition towards agile development also requires a transition in organizational culture to promote collaboration, distributed responsibility and collective intelligence.Produktutveckling har blivit väsentlig på dagens teknikdrivna marknadsplats. För närvarande är traditionella modeller som stage-gate vanligt förekommande i flera etablerade företag inom bilindustrin, även om dessa modeller har kritiserats för att vara för linjära och planfokuserade när omgivningen och intern komplexitet kräver snabbare och mer flexibel utveckling. Även om produktutveckling har en fundamental roll i framgången hos ett företag så är leverantörer centrala i att hjälpa företag att uppnå sina produktutvecklingsmål. Som ett resultat av ökad outsourcing kan företag vidta mer utvecklings och integrationsinitiativ för att säkerställa kvalitet och effektivitet hos leverantören. Att använda leverantörsintegration har visat positiva effekter på flera nyckeltal. Emellertid har begränsad forskning om effekterna av att integrera leverantörer i ineffektiva produktutvecklingsmetoder publicerats. Företag som integrerar leverantörer i linjära, dokumentationstunga processer kan därför potentiellt hindra den interna utvecklingen av flexibla tillvägagångssätt. Därmed är syftet med denna studie att undersöka hur leverantörsintegration kan försvåra tillämpning av agila metoder i produktutveckling för leverantörer och hur dessa utmaningar kan adresseras. Denna studie bygger på en kvalitativ, explorativ fallstudie som inkluderar 13 intervjuer med anställda inom det observerade företaget tillsammans med omfattande data från observationer. Empiriska data i kombination med teorier om agil utveckling, traditionell utveckling och leverantörsintegration resulterade i ett förslag till integrerade leverantörer, som är bundna till traditionella utvecklingsmodeller, att adoptera agila utvecklingsmetoder. Resultaten tyder på att integrerade leverantörer kan möta utmaningar när det gäller att använda agila metoder på grund av krav att använda traditionella utvecklingsmetoder från det integrerande företaget. Där emot finns möjlighet att tillämpa agila metoder i mikroperspektivet samtidigt som traditionella utvecklingsmetoder bibehålls i makroperspektivet genom en hybridmodell. Även om möjligheten att adoptera agila metoder finns ger metoderna små fördelar utan adekvat agilt ledarskap och tankesätt. Därmed kräver en övergång till agil produktutveckling också en förändring i organisationskultur för att främja samarbete, distribuerat ansvar och kollektiv intelligens.
8
Gumbel, Kristoffer, und Lina Andersson. „Hur fungerar styrandet av ett projekt utan projektmodell? : En fallstudie på Totalförsvarets Forskningsinstitut“. Thesis, Linköping University, Department of Management and Engineering, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-54763.
Der volle Inhalt der QuelleAnnotation:
Att använda någon slags projektmodell ses för många projektledare som ett stöd och någotatt använda sig av för att projektet ska uppnå ett bra resultat. På TotalförsvaretsForskningsinstitut (FOI) har de valt att inte använda sig av någon projektmodell. Deanpassar istället projektet löpande efter hur det utvecklas. Detta har vi valt att kalla förFOI:s grundmodell.Studiens syfte är att skapa oss en förståelse för hur styrningen i ett projekt utanprojektmodell fungerar. Syftet är även att jämföra denna projektmodell med den agilamodellen Scrum. Fem intervjuer har utförts och utgör grunden för vårt empiriska material.Det empiriska materialet i sin tur har hjälpt oss att besvara vår huvudfråga som lyder, hurstyrande är ett projekt utan projektmodell för projektmedlemmarna på FOI med avseendepå utförande av arbete?Vår studie visar att FOI:s grundmodell och Scrum har fler skillnader än likheter, trots attbåda projektmodellerna lätt kan anpassas efter projektets utveckling. Vi har dock upptäcktatt FOI använder sig av någon slags informell projektmodell då det finns ett fåtal riktlinjeratt följa. Dessa riktlinjer påverkar styrningen av de projektdeltagare som utför arbetet iprojektet, men har liten inverkan på projektets olika projektledare. Under arbetets gångupptäckte vi även att det fanns intressanta gruppsociologiska fenomen att undersöka, tillexempel maktförhållanden och normer. Detta gjorde vi för att närmare undersökastyrningens inverkan och konsekvenserAtt använda någon slags projektmodell ses för många projektledare som ett stöd och någotatt använda sig av för att projektet ska uppnå ett bra resultat. På TotalförsvaretsForskningsinstitut (FOI) har de valt att inte använda sig av någon projektmodell. Deanpassar istället projektet löpande efter hur det utvecklas. Detta har vi valt att kalla förFOI:s grundmodell.Studiens syfte är att skapa oss en förståelse för hur styrningen i ett projekt utanprojektmodell fungerar. Syftet är även att jämföra denna projektmodell med den agilamodellen Scrum. Fem intervjuer har utförts och utgör grunden för vårt empiriska material.Det empiriska materialet i sin tur har hjälpt oss att besvara vår huvudfråga som lyder, hurstyrande är ett projekt utan projektmodell för projektmedlemmarna på FOI med avseendepå utförande av arbete?Vår studie visar att FOI:s grundmodell och Scrum har fler skillnader än likheter, trots attbåda projektmodellerna lätt kan anpassas efter projektets utveckling. Vi har dock upptäcktatt FOI använder sig av någon slags informell projektmodell då det finns ett fåtal riktlinjeratt följa. Dessa riktlinjer påverkar styrningen av de projektdeltagare som utför arbetet iprojektet, men har liten inverkan på projektets olika projektledare. Under arbetets gångupptäckte vi även att det fanns intressanta gruppsociologiska fenomen att undersöka, tillexempel maktförhållanden och normer. Detta gjorde vi för att närmare undersökastyrningens inverkan och konsekvenser.
9
Soundararajan, Shvetha. „Agile Requirements Generation Model: A Soft-structured Approach to Agile Requirements Engineering“. Thesis, Virginia Tech, 2008. http://hdl.handle.net/10919/34511.
Der volle Inhalt der QuelleAnnotation:
The agile principles applied to software engineering include iterative and incremental development, frequent releases of software, direct stakeholder involvement, minimal documentation and welcome changing requirements even late in the development cycle. The Agile Requirements Engineering applies the above mentioned principles to the Requirements Engineering process.
Agile Requirements Engineering welcomes changing requirements even late in the development cycle. This is achieved by using the agile practice of evolutionary requirements which suggests that requirements should evolve over the course of many iterations rather than being gathered and specified upfront. Hence, changes to requirements even late in the development cycle can be accommodated easily.
There is however, no real process to the agile approach to Requirements Engineering. In order to overcome this disadvantage, we propose to adapt the Requirements Generation Model (a plan-driven Requirements Engineering model) to an agile environment in order to structure the Agile Requirements Engineering process. The hybrid model named the Agile Requirements Generation Model is a soft-structured process that supports the intents of the agile approach. This model combines the best features of the Requirements Generation Model and Agile Software Development.Master of Science
10
Nord, Olsson Hjalmar, und Daniel Wiskman. „Motivation och Agila aktiviteter : En fallstudie om hur agila aktiviteter motiverar deltagare i ett utvecklarteam på Tradera“. Thesis, Uppsala universitet, Företagsekonomiska institutionen, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-304079.
Der volle Inhalt der QuelleAnnotation:
Studiens syfte har varit att undersöka hur agila aktiviteter kan bidra till att motivera deltagare i ett agilt utvecklarteam. För att besvara studiens syfte genomfördes en fallstudie under nio veckor där ett utvecklarteam på företaget Tradera observerades. Utöver observationerna gjordes även intervjuer med en majoritet av teamets medlemmar. Genom att kombinera den klassiska motivationsteorin Job Characteristics Modell med scrumteori utvecklades en konceptuell analysmodell. Den konceptuella analysmodellen operationaliserar egenskaper hos de agila aktiviteterna som enligt teorin ger upphov till hög arbetsmotivation. Genom intervjuerna operationaliseras begreppet motivation – där en intervjuteknik som använts i tidigare studier för att mäta motivation anammats. Resultatet av studien visar att de agila aktiviteterna planeringsmöte, demonstration och återblicksmöte i det studerade utvecklarteamet på Tradera innehar egenskaper som skapar förutsättning för hög arbetsmotivation. I en teoretisk men inte empirisk mening stöds sambandet mellan egenskaperna och hög arbetsmotivation. Där berättelser från teammedlemmar om episoder av hög motivation kopplat till de agila aktiviteterna ger en indikation på att egenskaperna hos aktiviteterna gett upphov till psykologiska tillstånd som resulterat i en hög arbetsmotivation.The purpose of this paper is to examine how agile activities can act as motivators for members of an agile development team. In order to serve this purpose a field study of nine weeks was carried out during which an agile development team at Tradera were observed. In addition to the field study interviews where conducted with a majority of the team members. A classical motivational theory in the form of Job Characteristics Model (JCT) and theory about scrum was used to form a conceptual analysis model. The model operationalizes characteristics of the agile activities, which according to JCT creates high work motivation. The concept of motivation was operationalized through the use of an interview technique that has been used in numerous previous studies in order to measure motivation and other non-tangible factors. The study shows that the agile activities planning session, demonstration and retrospective used by the development team at Tradera has inherent characteristics that creates a setting in which high work motivation has the possibility of being prevalent. In a theoretical, but not empirical, way the results of the study supports a connection between the presence of the characteristics in the agile activities and high motivation. Where stories from team members of episodes of high motivation during the agile activities gives an indication of the activities.
11
Svensson, Johan, und Samuel Hanning. „Distansarbetes påverkan på teamwork i en agil organisation : En kvalitativ studie“. Thesis, Uppsala universitet, Företagsekonomiska institutionen, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-448394.
Der volle Inhalt der QuelleAnnotation:
Covid-19-pandemin har medfört ett skifte från samlokaliserat arbete till distansarbete. Den här studien syftar till att förklara vilka effekter distansarbete har på teamwork i agila teams. Studien genomfördes genom djupintervjuer enligt kvalitativ metod, med teammedlemmar på en svensk bank, och analysmodellen baseras på Dickinson och McIntyres teamworkmodell, där komponenterna delade mentala modeller och förtroende adderats. Resultatet indikerar att respondenterna upplever att teamwork förändrats negativt vid distansarbete genom hela modellen, med undantag för teamorientering och teamledarskap. Där upplevs marginell negativ förändring eller ingen förändring. Den agila strukturen upplevs vara en kritisk faktor för att upprätthålla fungerande teamwork vid distansarbete. Kommunikationen face-to-face har dock minskat, vilket leder till flera teamworkutmaningar. Tidigare uppbyggt förtroende och delade mentala modeller verkar underlätta teamwork vid distansarbete. Eftersom trenden indikerar att distansarbete kommer vara aktuellt även efter Covid-19-pandemin måste dessa utmaningar behandlas. Den utvidgade teamworkmodellen verkar kunna förklara effekten på teamwork vid distansarbete i agila teams.
12
Vaarala, Robert, und Johan Svernell. „Personlig motivation i agil projektledning : En fallstudie på Kambi Sports Solutions AB“. Thesis, Uppsala universitet, Företagsekonomiska institutionen, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-202750.
Der volle Inhalt der QuelleAnnotation:
Syftet med studien är att undersöka huruvida det är mer eller mindre motiverande för anställda inom mjukvaruindustrin att jobba enligt agila utvecklingsmetoder än enligt traditionella utvecklingsmetoder. Undersökningen har gjorts med teoretisk utgångspunkt från motivationsskapande variabler ur de kontemporära motivationsteorierna Self Determination Theory samt Job Characteristic model. Som en ansats till att besvara frågeställningen har en kvalitativ fallstudie genomförts på företaget Kambi Sport Solutions AB. Kambi Sport Solutions AB har under de senaste åren genomfört en organisationsförändring där traditionella projektledningsmetoder ersatts av agila projektledningsmetoder. Studiens empiri visar med stöd ur motivationsteori att övergången till agila metoder signifikant påverkat individens motivation positivt. Framförallt som en följd av en högre grad av självbestämmande, kunskapsvariation, identitet i och betydelse av arbetsuppgiften, autonomi samt feedback.
13
Jedyk, Marcin. „Using Feature Models For Reusability In Agile Methods“. Master's thesis, METU, 2011. http://etd.lib.metu.edu.tr/upload/12613338/index.pdf.
Der volle Inhalt der QuelleAnnotation:
The approach proposed in this thesis contributes to implementing source code reuse and re-engineering techniques for agile software development. This work includes an introduction to feature models and some of the Feature Oriented Software Development (FOSD) practices to achieve a lightweight way of retrieving source code. A Feature model created during the course of following FOSD practices serves as an additional layer of documentation which represents the problem space for the developed application. This thesis proposes linking source code with such a feature model for the purpose of identifying and retrieving code. This mechanism helps with accessing the code segment corresponding to a feature with minimal effort, thus suits agile development methods.
At the moment, there is a gap between feature oriented approaches and agile methods. This thesis tries to close this gap between high-level approaches for software modelling (feature modelling) and agile methods for software development.
14
Bodicherla, Saikumar, und Divyani Pamulapati. „Knowledge Management Maturity Model for Agile Software Development“. Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-17659.
Der volle Inhalt der QuelleAnnotation:
Context: Knowledge is the major aspect of an organization which enables the enterprise to be more productive and to deliver the high complexity services. Knowledge management plays a key role in agile software development because it supports cultural infrastructure esteems like collaboration, communication, and knowledge transfer. This research aims to explore how organizations that adopts Agile Software Development (ASD) implement knowledge management utilizing practices that supports the key process areas. Several knowledge management maturity models have been proposed over a decade ago but not all of the models that is specially stated knowledge Management Maturity Model (KMMM) for Agile software development. To fulfil this research gap, we introduce the maturity model which emphasize knowledge management in ASD among the practitioners. This maturity model helps to assess their knowledge management in organization and provides a road map to the organizations for any further improvement required in their processes. Objectives: In this thesis, we investigate the key process areas of knowledge management maturity models that could support agile software development. Through investigation about the key process areas, we found that the organizations should emphasis on key process areas and its practices in order to improve the software process. The objectives of this research include: Explore the key process areas and practices of knowledge management in the knowledge management maturity models. Identify the views of practitioners on knowledge management practices and key process areas for Agile software development. To propose the maturity model for Knowledge management in Agile software development among the practitioner’s opinions. Methods: In this research, we conducted two methods: Systematic mapping and Survey to fulfil our aim and objectives. We conducted Systematic mapping study through the snowballing process to investigate empirical literature about Knowledge management maturity models. To triangulate the systematic mapping results, we conducted a survey. From the survey results, we obtained the responses and were analyzed statistically using descriptive statistics. Results: From Systematic mapping, we identified 18 articles and analyzed 24 practices of Knowledge management maturity models. These practices are indicated in key process areas such as process, people, technology. Through the systematic mapping results, 9 KM practices that were found from KMMM literature were listed in the survey questionnaire and answered by software engineering practitioners. Moreover, 5 other new practices for agile have suggested in the survey that was not found in KMMM literature. To address the systematic mapping and survey results, we propose the maturity model which emphasize knowledge management practices in ASD among the practitioners. Conclusions: This thesis lists the main elements of practices that are utilized by the organization and also show the usage of maturity levels at each practice in detail. Furthermore, this thesis helps the organization's to assess the current levels of maturity that exist to each practice in a real process. Hence, the researchers can utilize the model from this thesis and further they can improve their Km in organizations.
15
Naughton, S. H. „Developing an agile supply chain model for SMEs“. Thesis, University of Liverpool, 2016. http://livrepository.liverpool.ac.uk/3006560/.
Der volle Inhalt der QuelleAnnotation:
Rising worldwide competition is making it increasingly difficult for SME organisations to compete in the marketplace as traditional means of manufacture, and modes of delivery are being changed through technological advancements. In line with these factors, organisations are ever more capable of producing goods that are more bespoke and personalised than in the past and within the price ranges and affordability levels of demanding markets. Whilst large organisations have the power to enforce supply chain compliance in order to meet these changes, it is not always the case for SMEs. The agile supply chain philosophy moves away from traditional methods under which large organisations enforce supply chain compliance, and embraces the concept of supply chain agility that allows the supply chain as a whole to move forward as one and share the benefits as a developed and cohesive unit. Such a philosophy should be to the advantage of all organisations, but ought to be of particular interest to SMEs as its use could assist in improving their competitiveness. This thesis is primarily concerned with the development of agile supply chains within SME organisations. The research sets out to develop the means through which SMEs can develop their agile supply chains so as to make them more efficient and competitive both now and in the future. The research is set upon existing theories and models, particularly following the works of Sharifi et al. (2006), Ismail and Sharifi (2006), Ismail et al., (2006) and Ismail et al., (2011) so as to contribute further to their concepts theoretically and to also present the practical means by which such frameworks can be utilised in industry. The research provides a link between manager perceptions and underlying factors that affect their organisations and how they relate to the markets served. This has been achieved through the development of a model through which SMEs can analyse their present operating position, consider new product features, potential supply chain partners and the means through which to develop their agile supply chains as a complete unit. Using case study methodology, some extensive fieldwork has been undertaken to examine the ideas and extend our understanding of the approaches to build and sustain agile networks for organisations introducing products into markets. The study has assisted in reforming and developing the initial models into practical tools. Further to this, the research offers a series of developmental roadmaps that can be followed by SMEs to assist in the progress of developing agility into their supply chains. The outcomes from the research provide a contribution to academic theory and practice and build upon previous research, taking it forward with practical tools that organisations can utilise. The findings provide evidence for the benefits that can be derived from the developed models such that their application could be realistically considered within a practical setting.
16
Rasch, Linnéa, und Victor Thun. „The Road to Become Agile : A case study of agile transformations in the retail market, including an organization development approach“. Thesis, KTH, Skolan för industriell teknik och management (ITM), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-279642.
Der volle Inhalt der QuelleAnnotation:
In today’s volatile market, retail companies struggle for survival as they have to become more flexible and dynamic. Thus, they change the organization, implementing agile methods. However agile is more than a set of practices and therefore the implementation process needs to be accompanied by organizational development to accomplish successful organizational change. This has been shown to be difficult for retail companies due to their size, defined silos, comfortable long-established ways of doing things and strong bureaucratic hierarchical culture. This thesis studies the implementation of agile in a large-scale retail organization and uses organizational development as a tool for deeper understanding and analysis. The study has been conducted at one of Sweden's leading retail organizations, where the research design contains two phases: one pre-study phase where a deeper understanding of the company and the transformation is achieved resulting in a problem formulation and the second phase where the main study is directed by the problem formulation and leads to an analysis and conclusion. The analysis is based on empirics gathered from three separate teams and is divided into three interconnected change phases, “Preparation”, “Implementation” and “Desired state”. From the analysis in the preparation and implementation phases; strengths and challenges within the organization were identified. Together with a maturity model to evaluate the implemented agile practices and an organizational culture assessment instrument to evaluate people and culture, the strengths and challenges were then used to estimate their current state and compare it to their future desired state. In conclusion, the strengths of the case company were that, when implemented, the observed teams incorporated the agile ceremonies and ways of work successfully. However, there were challenges identified in relation to resistance within management, there was a general lack of support from the sponsors and confusion about the managerial roles. There was also a lack of communication, cooperation and synchronizations between teams.I dagens flyktiga marknader kämpar företag inom dagligvaruhandeln för att överleva då de måste bli mer flexibla och dynamiska i deras strategi. För att bemöta detta ändrar företagen sin strategi genom implementering av agila metoder. Emellertid handlar att vara agil inte bara om att använda sig av olika verktyg och övningar för att ändra hur man arbetar, utan för att implementeringen av agila metoder ska vara lyckad, måste den följas med av en lyckad organisationsförändring. En sådan agil implementering och organisationsförändring har visats vara komplicerad i just dagligvaruhandeln på grund av organisationernas ofta stora storlek, definierade silos, komfortabla gamla traditioner och starka hierarkiska organisationskultur. Denna uppsats studerar implementationen av agilt i ett storskaligt företag inom dagligvaruhandeln och använder sig av organisationsutveckling som ett verktyg för att nå en djupare förståelse och analys. Analysen är uppdelad i tre olika sammanhängande faser “Förberedelse”, “Implementering”, och “Önskat Tillstånd”. Empirin analysen är baserad på kommer från tre olika separata team, vilka är i olika faser av den agila transformationen. I förberedelse- och implementeringsfaserna identifieras styrkor och utmaningar hos företaget. Dessa används sedan tillsammans med en mognadhetsmodell, för att evaluera de agila tillvägagångssätten samt ett bedömningsinstrument för organisationskultur, för att evaluera personer och kultur, i syfte att sedan utvärdera det nuvarande tillståndet i jämförelse med det önskade. Sammanfattningsvis lyckades de observerade teamen att framgångsrikt implementera de agila metoderna och arbetssätten. Däremot identifierades flera utmaningar i relation till motstånd inom management. Det fanns en generell förvirring kring chefs rollernas betydelse och det saknades stöd från ledningsgruppen. Slutligen identifierades även förbättringsområden inom kommunikation, samarbete och synkronisering mellan olika team.
17
Sivander, Fredrik. „An Agile Procurement Model that Facilitates Agile Execution of Projects : A Case Study at Telia Company“. Thesis, Mittuniversitetet, Avdelningen för informations- och kommunikationssystem, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:miun:diva-28647.
Der volle Inhalt der QuelleAnnotation:
Since agile execution of projects has become more frequently used the discovery that the surroundings of the projects are not always compatible has been made. The problematic within the area is traditional accounting restrictions and cost estimation. The purpose with this research is to develop a procurement method that facilitates for agile execution of projects. Previous research proves that the agile principles can be used in a procurement process successfully, but with focus on facilitating on the procurement itself and not on the agile execution. This research includes theories about the agile estimation models and requirement prioritizing methods. The method used to complete this research is design science, which includes six steps to ensure reproducibility and validity. This research resulted in a procurement method that includes three methods and two phases with focus on minimizing the pre-study, with focus on only the most important requirements only. The procurer will then attend the agile execution and both procurer and executer enter the project with the mindset that the initial budget- and time estimation will be increased. Both procurer and executor works together towards the same goal, maximum customer value for minimum cost. The method is tested beside two projects conducted by Telia Company and the test result is that the generated solution reduces the total cost of the project and time to generate project result and facilitates for an agile execution. This research concludes that an agile procurement can facilitate agile execution of project but before agile procurement can be a recommendation more tests are needed.
18
Baccolini, Giulia. „I modelli agili di sviluppo software: il caso Scrum“. Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2014. http://amslaurea.unibo.it/7213/.
Der volle Inhalt der Quelle
19
Ramadoss, Balaji. „Ontology Driven Model for an Engineered Agile Healthcare System“. Scholar Commons, 2014. https://scholarcommons.usf.edu/etd/5110.
Der volle Inhalt der QuelleAnnotation:
Healthcare is in urgent need of an effective way to manage the complexity it of its systems and to prepare quickly for immense changes in the economics of healthcare delivery and reimbursement. Centers for Medicare & Medicaid Services (CMS) releases policies affecting inpatient and long-term care hospitals policies that directly affect reimbursement and payment rates. One of these policy changes, a quality-reporting program called Hospital Inpatient Quality Reporting (IQR), will effect approximately 3,400 acute-care and 440 long-term care hospitals. IQR sets guidelines and measures that will contain financial incentives and penalties based on the quality of care provided. CMS, the largest healthcare payer, is aggressively promoting high quality of care by linking payment incentives to outcomes. With CMS assessing each hospital's performance by comparing its Quality Achievements and Quality Improvement scores, there is a growing need and demand to understand these quality measures under the context of patient care, data management and system integration. This focus on patient-centered quality care is difficult for healthcare systems due to the lack of a systemic view of the patient and patient care. This research uniquely addresses the hospital's need to meet these challenges by presenting a healthcare specific framework and methodology for translating data on quality metrics into actionable processes and feedback to produce the desired quality outcome. The solution is based on a patient-care level process ontology, rather than the technology itself, and creates a bridge that applies systems engineering principles to permit observation and control of the system. This is a transformative framework conceived to meet the needs of the rapidly changing healthcare landscape. Without this framework, healthcare is dealing with outcomes that are six to seven months old, meaning patients may not have been cared for effectively. In this research a framework and methodology called the Healthcare Ontology Based Systems Engineering Model (HOB-SEM) is developed to allow for observability and controllability of compartmental healthcare systems. HOB-SEM applies systems and controls engineering principles to healthcare using ontology as the method and the data lifecycle as the framework. The ontology view of patient-level system interaction and the framework to deliver data management and quality lifecycles enables the development of an agile systemic healthcare view for observability and controllability
20
Korraprolu, Srinivasa Abhilash. „Evaluation of the Relevance of Agile Maturity Models in the Industry : A Case Study“. Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-16788.
Der volle Inhalt der QuelleAnnotation:
Background. Over the years, agile software development has become increasingly popular in the software industry. One of the reasons is that agile development addressed the needs of the organisations better than the traditional models, such as the waterfall model. However, the textbook version of agile development still leaves something to be desired. This could be learnt by observing the implementation of agile methods/frameworks in the industry. The teams often customize agile methods to suit their context-specific needs. When teams in the industry decide to adopt the agile way of working, they are confronted by a choice¾either they have to implement all the agile practices at a time or adopt them over the time. The former choice has shown to come with risks and, therefore, was found that practitioners generally preferred the latter. However, agile practices are not independent, they have dependencies amongst them. A new approach to agile development emerged in the recent years known as Agile Maturity Models (AMMs). AMMs claim to offer a better path to agile adoption. In AMMs, the practices are typically introduced gradually in a particular order. However, these AMMs are multifarious and haven’t been sufficiently evaluated¾especially in the industry practice. Thus, they need to be evaluated in order to understand their relevance in the industry. Objectives. The goal is to evaluate the relevance of AMMs in the industry. By finding relevant AMMs, they could be used to alleviate the formation of agile teams and contribute toward their smoother functioning. By finding those that aren’t, this research could act as a cautionary to those practitioners who could potentially implement these AMMs and risk failure. The objectives are: identifying the agile practice dependencies in the AMMs; finding the agile practice dependencies in an agile team by conducting a case study in the industry; comparing the dependencies from the case study with those in the AMMs.
Methods. The agile maturity models were identified and analysed. A case study was conducted on an agile team to identify the dependencies between the agile practices in the industry practice. Semi-structured interviews were conducted with members of the agile team. Qualitative coding was used to analyse the collected data. The dependencies from the case study were compared with the AMMs to achieve the aim of this research. Results. It was found that dependencies between individual agile practices in the AMMs were almost never possible to be found. However, practices suggested in each maturity levels were derived. Hence, the dependencies were found in the maturity-level level. From the case study, 20 agile practice dependencies were found. 7/8 AMMs were found to be not relevant. 1 AMM couldn’t be evaluated as it heavily relied on the practitioner’s choices. Conclusions. The researchers could use the evaluation method presented in this thesis to conduct more such evaluations. By doing so, the dynamics present in the industry teams could be better understood. On their basis, relevant AMMs could be developed in the future. Such AMMs could help practitioners leverage agile development.
21
D'Angelo, Laura. „Evaluation of code generation in agile software development of embedded systems“. Thesis, Uppsala universitet, Avdelningen för datorteknik, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-353798.
Der volle Inhalt der QuelleAnnotation:
Generating code from software models is considered to be a new generation leap within software development methods. The objective of this M.Sc. project is to evaluate how different approaches to modelling and code generation affect embedded systems software development and propose recommendations on how to improve software development. Two product areas at Saab Surveillance EW Systems in Järfälla, Stockholm, are used as study objects. A research overview is made to highlight themes regarding modelling, code generation and software development in general. Based on these, interviews are held with system engineers and software developers at each product area, where they use different modelling and code generation approaches. The two development processes are described thoroughly. Challenges and advantages related to each area’s approach are investigated. Software development within product area A is affected by the product complexity and the larger scale of the development, including projects running over a longer time with more teams involved. Recommendations include enabling code generation by aligning it with other investments on process improvement and limiting the approach to generating some system components. Software developers within product area B can use full code generation, enabled by the limited product complexity. The product area is affected by software standards and external requirements on the process. Recommendations include extending the modelling approach to make it easier to trace functionality from system to software level. Conclusions are that both product areas can apply modelling and code generation to more software development activities to improve their respective development processes.
22
Zani, Sofia. „Comparazione empirica di sviluppi Agili mediante un modello di qualità e un modello di maturità“. Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2021. http://amslaurea.unibo.it/22816/.
Der volle Inhalt der QuelleAnnotation:
La mia ricerca si propone come obiettivo principale l'elaborazione di una metodologia d'analisi per confrontare i team di sviluppo che utilizzano il modello di lavoro Agile Scrum.
Come caso di studio ho analizzato i dati prodotti nell'ambiente di sviluppo CAS (Compositional Agile System) e le risposte a questionari di 57 intervistati appartenenti a 11 team coinvolti nel progetto di Ingegneria del Software del Corso di Laurea in Informatica dell'anno 2020/2021.
Il modello di qualità del lavoro di Hoegl-Gemuenden e il modello di maturità Scrum di Yin sono due modelli atti ad analizzare aspetti differenti del lavoro di un team e applicati in studi di ricerca separati. La particolarità della mia ricerca è che ogni team è stato valutato secondo entrambi i modelli, e infine ho ritrovato una correlazione tra le valutazioni ottenute.
23
Larsson, John, und Lina Fjeldgård. „Konceptuella modellers roll i agila utvecklingsprojekt“. Thesis, Uppsala universitet, Institutionen för informatik och media, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-226666.
Der volle Inhalt der QuelleAnnotation:
Konceptuella modeller är vanligt förekommande i plandriven utveckling men åsikterna om vad konceptuell modellering är och bör användas till är vitt skilda. Agil systemutveckling har växt fram som en motreaktion på den plandrivna systemutvecklingen och forskning har visat att många traditionella verktyg som förknippas med plandriven utveckling förkastas i detta relativt nya sätt att arbeta. Syftet med denna studie är att belysa hur yrkesverksamma inom agila projekt ser på konceptuell modellering i relation till det agila manifestet. Detta har åstadkommits genom intervjuer med flera utövare av agila projektmetoder. Studien visar att det agila manifestet har låg grad av förankring hos utövarna av agila metoder och att endast vissa av principerna efterlevs. Konceptuella modeller är vanligt förekommande i agila projekt och används i samma typer av aktiviteter som i plandriven utveckling. Motiven bakom användandet i agila projekt är relaterade till de konceptuella modellernas egenskaper som visualiserings- och kommunikationsverktyg.
24
Casi, Greta. „Il modello del Motel Agip nell'Italia dello sviluppo economico (1954 - 1975)“. Master's thesis, Alma Mater Studiorum - Università di Bologna, 2018. http://amslaurea.unibo.it/17251/.
Der volle Inhalt der QuelleAnnotation:
Il progetto di tesi tratta delle strutture alberghiere Agip in Italia, inizialmente in larga scala, analizzando tutti i Motel ancora oggi presenti, focalizzandosi poi su un unico caso studio. A partire dal 1954 l’Agip di Enrico Mattei avvia il programma dei motel realizzandoli lungo le vie principali di tutta Italia, contando alla fine del 1966 più di 37 motel per arrivare successivamente ad un totale di 50. Una volta analizzate tali strutture si è deciso di soffermarsi sul Modello 59, il più riproposto e rappresentativo del modo di costruire italiano durante lo sviluppo economico di quegli anni, scegliendo come caso studio il Motel Agip di Bologna. Di esso si è analizzato ogni aspetto, da quello architettonico a quello strutturale, ricostruendo la storia, le caratteristiche e i difetti riscontrati nel tempo. Venne costruito alla fine degli anni 50, più precisamente nel 1959, in zona Borgo Panigale, lungo la via Emilia, a pochi km dall'ingresso all'Autostrada, presentando la rigida organizzazione interna tipica di tutti gli altri modelli 59 italiani. A causa della crisi economica venne ceduto a soggetti privati, cambiando spesso proprietario e subendo diverse trasformazioni soprattutto dal punto di vista architettonico, fra le quali la demolizione del piano attico, che originariamente ospitava la casa del direttore. Inoltre nel 1989 in seguito ad un ampliamento le facciate hanno subito diverse variazioni, che ne hanno snaturato quasi completamente l’immagine originaria. Il progetto prevede tre interventi principali:
-Riprogettare il piano attico, riportandolo almeno idealmente, alla configurazione iniziale.
-Ricreare l’involucro esterno attraverso l’utilizzo di facciate ventilate, modernizzandone l’immagine e cercando di riportarlo, soprattutto attraverso i colori ma con nuovi materiali, alla configurazione che lo classificava come Modello 59, migliorandone inoltre la classe energetica;
-Adeguare sismicamente l’edificio, attraverso interventi globali e localizzati.
25
Léauté, Thomas. „Coordinating agile systems through the model-based execution of temporal plans“. Thesis, Massachusetts Institute of Technology, 2005. http://hdl.handle.net/1721.1/34681.
Der volle Inhalt der QuelleAnnotation:
Thesis (S.M.)--Massachusetts Institute of Technology, Dept. of Aeronautics and Astronautics, 2005.Includes bibliographical references (p. 149-155).
Agile autonomous systems are emerging, such as unmanned aerial vehicles (UAVs), that must robustly perform tightly coordinated time-critical missions; for example, military surveillance or search-and-rescue scenarios. In the space domain, execution of temporally flexible plans has provided an enabler for achieving the desired coordination and robustness, in the context of space probes and planetary rovers, modeled as discrete systems. We address the challenge of extending plan execution to systems with continuous dynamics, such as air vehicles and robot manipulators, and that are controlled indirectly through the setting of continuous state variables. Systems with continuous dynamics are more challenging than discrete systems, because they require continuous, low-level control, and cannot be controlled by issuing simple sequences of discrete commands. Hence, manually controlling these systems (or plants) at a low level can become very costly, in terms of the number of human operators necessary to operate the plant. For example, in the case of a fleet of UAVs performing a search-and-rescue scenario, the traditional approach to controlling the UAVs involves providing series of close waypoints for each aircraft, which incurs a high workload for the human operators, when the fleet consists of a large number of vehicles.
(cont.) Our solution is a novel, model-based executive, called Sulu, that takes as input a qualitative state plan, specifying the desired evolution of the state of the system. This approach elevates the interaction between the human operator and the plant, to a more abstract level where the operator is able to "coach" the plant by qualitatively specifying the tasks, or activities, the plant must perform. These activities are described in a qualitative manner, because they specify regions in the plant's state space in which the plant must be at a certain point in time. Time constraints are also described qualitatively, in the form of flexible temporal constraints between activities in the state plan. The design of low-level control inputs in order to meet this abstract goal specification is then delegated to the autonomous controller, hence decreasing the workload per human operator. This approach also provides robustness to the executive, by giving it room to adapt to disturbances and unforeseen events, while satisfying the qualitative constraints on the plant state, specified in the qualitative state plan. Sulu reasons on a model of the plant in order to dynamically generate near-optimal control sequences to fulfill the qualitative state plan. To achieve optimality and safety, Sulu plans into the future, framing the problem as a disjunctive linear programming problem.
(cont.) To achieve robustness to disturbances and maintain tractability, planning is folded within a receding horizon, continuous planning and execution framework. The key to performance is a problem reduction method based on constraint pruning. We benchmark performance using multi-UAV firefighting scenarios on a real-time, hardware-in-the-loop testbed.
by Thomas Léauté.
S.M.
26
Gena, Kriti. „Suitability of Model Based Systems Engineering for Agile Automotive Product Development“. The Ohio State University, 2020. http://rave.ohiolink.edu/etdc/view?acc_num=osu1595500667122794.
Der volle Inhalt der Quelle
27
Wickström, Carina, und Robin Holmquist. „The Solo First Pair Second Programming Model“. Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-299589.
Der volle Inhalt der QuelleAnnotation:
Software is fundamental to life in modern society. We have come to depend on it for critical aspects such as managing bank transactions and medical records. However, code defects in software is a common issue, and software not working properly has the potential to cause major damage to both humans and the environment. Many attempts have been made in order to improve software development in order to reduce code defects, among other aspects. One such attempt is the invention of the practice pair programming, where two programmers share and work together on a single workstation. The more traditional way of developing software is solo programming, where each developer is assigned an individual workstation. However, the issue with code defects still remains. Hence, there is a need for better methods for reducing software defects. The purpose of this thesis is to create a software development model for reducing software defects. The model suggested in this thesis is a combined practice where coding with solo programming is followed by re-coding with pair programming called Solo First Pair Second Programming (SFPSP). The goal is to help software development teams to develop more reliable software. Our research was qualitative with support from quantitative data. The research included a literature study and an action study. The literature study was done in order to create a first version of SFPSP entirely based on literature, whereas the action study was done in order to evaluate as well as refine SFPSP based on practical experience. The results of this thesis is the practice SFPSP as well as an evaluation of said practice. Our evaluation shows that SFPSP leads to fewer code defects compared to solo programming. However, the cost with regard to development time and effort is significantly higher for SFPSP compared to solo programming. SFPSP is based on both theoretical and practical knowledge, and has therefore a solid foundation to build upon. Our literature study verified that no practice like SFPSP existed before this thesis.Programvara är grundläggande för livet i det moderna samhället. Vi är beroende av det för kritiska aspekter som att hantera banköverföringar och medicinska journaler. Kodfel i programvara är dock ett vanligt problem, och programvara som inte fungerar som den ska kan orsaka stora skador på både människor och miljön. Många försök har gjorts för att förbättra programvaruutveckling med målet att minska bland annat kodfel. Ett sådant försök är uppfinningen av praxisen parprogrammering, där två programmerare delar och arbetar tillsammans på en enda arbetsstation. Det mer traditionella sättet att utveckla programvara är soloprogrammering, där varje utvecklare tilldelas en individuell arbetsstation. Dock kvarstår problemet med kodfel. Därför finns det ett behov av bättre metoder för att minska kodfel. Syftet med denna avhandling är att skapa en programvaruutvecklingsmodell för att minska kodfel. Modellen som föreslås i denna avhandling är en kombinerad praxis där kodning med soloprogrammering följs av omkodning med parprogrammering, kallad Solo First Pair Second Programming (SFPSP). Målet är att hjälpa programvaruutvecklingsteam att utveckla mer pålitlig programvara. Vår forskning var kvalitativ med stöd av kvantitativ data. Forskningen omfattade en litteraturstudie och en aktionsstudie. Litteraturstudien gjordes för att skapa en första version av SFPSP helt baserad på litteraturen, medan aktionsstudien gjordes för att utvärdera och förfina SFPSP baserat på praktisk erfarenhet. Resultaten av denna avhandling är praxisen SFPSP samt en utvärdering av denna praxis. Vår utvärdering visar att SFPSP leder till färre kodfel jämfört med soloprogrammering. Dock visar den att kostnaden med avseende på utvecklingstid och ansträngning är betydligt högre för SFPSP jämfört med soloprogrammering. SFPSP bygger på både teoretisk och praktisk kunskap och har därför en stabil grund att bygga på. Vår litteraturstudie verifierade att det inte fanns någon praxis som SFPSP före denna avhandling.
28
Eshtiagh, Peyman. „An evaluation of test processes in an agile environment“. Thesis, KTH, Skolan för teknikvetenskaplig kommunikation och lärande (ECE), 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-155399.
Der volle Inhalt der QuelleAnnotation:
The aim of this thesis is to improve the reliability and quality of new requested functionality, and existing modules, at Fortum HR System Solutions. This was conducted through an evaluation of the test processes by implementing principles of Software Testing and Test Management. For the study to successfully improve the testing performed at HR System Solutions, existing test processes were analyzed. The analysis was conducted by evaluating the current test processes using theoretical test evaluation styles called maturity models. The methodology of choice was the Testing Maturity Model (TMM), which was adapted to the nature of HR System Solutions requirements, experience and needs. The evaluation used qualitative methods together with pedagogical principles to conduct interviews and workshops to consolidate the theoretical evaluation. Interviews and workshops were conducted within the team of HR System Solutions, where all members of them team contributed to the thesis at some point. An external interview also took place for comparative study. Results of the evaluation, interviews and workshop were compiled and analyzed accordingly. With the analyzed results in place, flaws in the testing processes were apparent. A generalization of the flaws led to the conclusion in the form of a suggestion. The conclusive suggestion was for Fortum HR System Solutions to establish a test committee/group role within the team. Considering the current economical and organizational situation this job role would be a divided job role appointed to current members of the HR System Solutions team. The research creates a walkthrough on a potential method on understanding inefficiencies within testing processes of a company and providing a cause-based solution.Undersökningen är inriktad på att förbättra tillförlitligheten och kvalitén på ny begärd funktionalitet, och befintliga moduler, på Fortum HR System Solutions. Detta genomfördes genom en utvärdering av testprocesser genom implementation av principer inom Software Testing samt Test Management. För att förbättra testningen som utförs på HR System Solutions var det nödvändigt att analysera de befintliga testprocesserna. Analysen genomfördes genom att utvärdera de nuvarande testprocesserna med hjälp av teoretiska utvärderingsmetoder som kallas Maturity Models. Den valda metoden var Testing Maturity Model (TMM) som tillämpades med avseende på HR System Solutions förutsättningar, erfarenheter och behov. Utvärderingen använder sig av kvalitativa metoder samt pedagogiska principer för att genomföra intervjuer och workshops stärka den teoretiska utvärderingen från TMM. Intervjuer och workshops genomfördes inom HR System Solutions arbetslag, där alla medlemmar bidrog till examensarbetet. Även en extern intervju gjordes i jämförande syfte. Resultatet av utvärderingen sammanställdes och analyserades i enlighet med de förnämnda teoretiska ramvärken. Med hjälp av analyserna visade sig bristerna hos HR System Solutions testprocesser. En generalisering av bristerna gjordes, vilket ledde till slutsatsen i form av ett förslag. Det slutliga förslaget innebar att Fortum HR System Solutions behöver upprätta en testkommitté/grupp inom arbetslaget. Undersökningen visar en potentiell metod för att förstå ineffektiviteten inom testprocesser i ett företag, och tillhandahålla en orsaks-baserad lösning.
29
Almeida, Luís Fernando Magnanini de. „Características, fatores críticos e indicadores de agilidade no gerenciamento de projetos de produtos inovadores“. Universidade Federal de São Carlos, 2012. https://repositorio.ufscar.br/handle/ufscar/3703.
Der volle Inhalt der QuelleAnnotation:
Made available in DSpace on 2016-06-02T19:51:56Z (GMT). No. of bitstreams: 1
4571.pdf: 2835932 bytes, checksum: 857c4fae6471592b22f205d753d4cdcd (MD5)
Previous issue date: 2012-08-13Financiadora de Estudos e Projetos
The theory of project management presents difficulties when applied to the development of innovative products. To solve these difficulties, a series of management methods were created. These methods receive the nomenclature of agile project management and increase the agility of the management process which would be a strategy to deal with the difficulties in those particular projects. However, the concept of agility is vague in the project management theory and the studies found that attempts to measure this performance was not satisfactory, presenting too much subjectivity in the definitions of constructs and starting from little robust definitions of agility. To try to solve this problem, a new model for agility in project management was proposed by Conforto (2011), relying on a definition coined from a systematic literature review of several areas that exhibit this same concept, and perform another systematic review on the models to measure agility in order to incorporate their strengths and create solutions to major weaknesses. This study aims to examine the relationships between the dimensions present in this model of agility to manage projects, in order to verify its validity and possibility its future use as a basis for measurement. Thus, the observed relationships between some features arising from the use of practices from the theory of agile project management theory, critical factors that may impact on the performance of the practices and indicators of agility. For this, a survey was made at the members from eight communities in Brazil Linkedin® chosen from among 79 candidates and selected according to 7 criteria. Also, was created the theoretical concept of "profile 500" which can be used in future research with have analysis made between members of this social network. There was obtained 172 valid responses from 966 users considered eligible for the study. Correlation analysis showed that the relationships proposed in the model of Conforto (2011) are valid and that agility is related to the presence of certain characteristics and are not inherent to the management method chosen, but this performance is related to customer participation and time taken decision. Finally, there was evidenced the importance of customer participation in the design and validation of partial results for a faster management process, and the necessity of carrying out the planning, development and validation with the participation of the client to perform better agility.
A teoria de gerenciamento de projetos apresenta dificuldades quando aplicada ao desenvolvimento de produtos inovadores. Para solucioná-las, surgiram uma série de métodos de gestão que podem ser agrupados sobre a nomenclatura de gerenciamento ágil de projetos. Esses, afirmam que o aumento da agilidade no processo de gestão seria uma estratégia para lidar com essas dificuldades. Contudo, o próprio conceito de agilidade é vago na teoria de gerenciamento de projetos e as tentativas encontradas de se medir esse desempenho não foram satisfatórias, apresentando demasiada subjetividade nos construtos e partindo de definições pouco robustas de agilidade. Para tentar solucionar esse problema, um novo modelo de agilidade para o gerenciamento de projetos foi proposto por Conforto (2011), se baseando em uma definição de agilidade cunhada a partir de uma revisão bibliográfica sistemática de diversas áreas que apresentam esse mesmo conceito, além de realizar outra revisão sistemática sobre os modelos de agilidade, de modo a incorporar os seus pontos fortes e criar soluções para os principais pontos fracos. Este estudo se propõe a verificar as relações entre as dimensões presentes neste modelo de agilidade para o gerenciamento de projetos a fim de verificar sua validade e possibilidade de utilização futura como base para medida. Desse modo, observa as relações entre algumas características advindas da utilização das práticas provenientes da teoria do gerenciamento ágil de projetos, fatores críticos que possam impactar no desempenho das práticas e os indicadores de agilidade. Para isso, foi realizado um levantamento estatístico entre os membros provenientes de 8 comunidades do Linkedin® Brasil escolhidas dentre 79 candidatas e selecionadas segundo a 7 critérios. Também cria o conceito teórico do perfil 500 o qual pode ser utilizado em pesquisas futuras que tenham como população de análise membros de comunidades dessa rede social. Obteve-se 172 respostas válidas dentre 966 usuários considerados aptos a participar do estudo. As análises de correlação mostraram que as relações propostas pelo modelo de Conforto (2011) são válidas e que a agilidade está relacionada à presença de certas características e não são inerentes ao método escolhido, sendo esse desempenho relacionado com a participação do cliente e tempo de tomada de decisão. Por fim, verificou-se a importância da participação do cliente no planejamento e validação dos resultados parciais para a agilidade do processo, e da necessidade realização do ciclo de planejamento, desenvolvimento e validação com a participação do cliente para um melhor desempenho em agilidade.
30
Henriques, Vaughan. „Assessing the Association between Agile Maturity Model Levels and Perceived Project Success“. Master's thesis, University of Cape Town, 2018. http://hdl.handle.net/11427/28407.
Der volle Inhalt der QuelleAnnotation:
The underlying philosophy of the agile manifesto is embodied in principle one which promotes the continuous delivery of software that is deemed valuable by the customer, while principle twelve encourages continual improvement of the delivery process. This constant improvement, or maturity, is not a concept unique to agile methods and is commonly referred to as a maturity model. The most common of maturity model is the Capability Maturity Model Integrated (CMMI). However, research consensus indicates CMMI is incompatible with agile implementation, specifically at higher levels of maturity without sacrificing agility. Agile maturity models, which are aligned to agile principles encourage continuous improvement while maintaining agility. Given the underlying philosophy of the agile manifesto, this research hypothesises that an increase in agile maturity is associated with improved perceived project success, by using a conceptual model based on an existing agile maturity model and how each of the maturity levels are related to the perceived project success. The research also brings to light the concept of perceived project success, showing success in an agile environment is a subjective concept. Conducted quantitatively, the findings of this research show which specific focus areas within each of the maturity levels is most strongly correlated with perceived project success and concludes an increasing correlation between the maturity levels and perceived project success.
31
Villanueva, del Pozo María José. „An agile model-driven method for involving end-users in DSL development“. Doctoral thesis, Universitat Politècnica de València, 2016. http://hdl.handle.net/10251/60156.
Der volle Inhalt der QuelleAnnotation:
[EN] Domain-specific languages (DSLs) are considered to be a powerful tool for enhancing the efficiency of software developers and bring software development closer to end-users from complex domains. However, the successful development of a DSL for a complex domain is a challenge from the technical point of view and because end-user acceptance is key.
Despite this fact, the relevant role of end-users during DSL development has traditionally been neglected. Normally, end-users participate at the beginning to communicate their preferences but they do not participate again until the DSL is completely implemented. As a consequence, if the language to develop reaches a complex domain, the chances that errors appear in the DSL are higher and solving them could involve large modifications that could have been avoided.
As a solution, in this PhD thesis, we propose an agile, model-driven method to involve end-users in DSL development. This thesis researches if the combination of best practices from the model-driven development (MDD) discipline and best practices from agile methods is a suitable approach to involve end-users in the DSL development process.
In order to validate the proposal, we have selected a highly complex domain such as the genetic analysis domain and we have collaborated with geneticists from three organizations. The proposed method has been used to involve these geneticists in the development of a DSL for the creation of genetic analysis pipelines. Simultaneously, we have carried out an empirical experiment to validate whether end-users and developers were satisfied with the proposal.[ES] Los lenguajes específicos de dominio (DSLs) son una herramienta muy potente para mejorar la eficiencia de los desarrolladores de software, así como para acercar el desarrollo software a usuarios sin conocimientos informáticos. Sin embargo, su principal problema es que desarrollar un DSL es complejo; no sólo desde el punto de vista técnico, sino especialmente porque la aceptación de dicho lenguaje por parte de los usuarios finales es clave. A pesar de este hecho, los métodos tradicionales de desarrollo de DSLs no enfatizan el importante rol de los usuarios finales durante el desarrollo. Normalmente, los usuarios participan al inicio para comunicar sus preferencias, pero no vuelven a participar hasta que el DSL está completamente desarrollado. Si el lenguaje a desarrollar aborda un dominio complejo, la posibilidad de que existan errores en el DSL es mayor, y su solución podría conllevar a modificaciones de gran calibre que podrían haberse evitado. Como solución, en esta tesis proponemos un método de desarrollo de DSLs, ágil, y dirigido por modelos que involucra a los usuarios finales. Esta tesis investiga si la combinación de buenas prácticas del desarrollo dirigido por modelos (MDD) y de buenas prácticas de métodos ágiles es adecuada para involucrar a los usuarios finales en el desarrollo de DSLs. Para validar la idoneidad de la propuesta, se ha seleccionado un dominio complejo como el de los análisis genéticos y se ha colaborado con un conjunto de genetistas procedentes de tres organizaciones. El método propuesto se ha utilizado para involucrar a dichos genetistas en el desarrollo de un DSL para la creación de pipelines para el análisis genético. Conjuntamente, se ha llevado a cabo un experimento empírico para validar si los usuarios finales y los desarrolladores están satisfechos con la propuesta de la presente tesis. En resumen, las contribuciones principales de esta tesis doctoral son el diseño e implementación de un método innovador, ágil y dirigido por modelos para involucrar a los usuarios finales en el desarrollo de DSLs, así como la validación de dicha propuesta en un entorno industrial en un desarrollo real de un DSL.
[CAT] Els llenguatges específics de domini (DSLs) son una ferramenta molt potent per a millorar l'eficiència dels desenvolupadors de programari, així com per a apropar el desenvolupament de programari a usuaris sense coneixements informàtics. El problema es que desenvolupar un DSL es complex, no sols des del punt de vista tècnic, sinó especialment perquè l'acceptació de dit llenguatge per part dels usuaris finals es clau. Malgrat aquest fet, els mètodes tradicionals de desenvolupament de DSLs no emfatitzen l'important rol dels usuaris finals durant el desenvolupament. Normalment, els usuaris participen a l'inici per a comunicar les seues preferències, però no tornen a participar fins que el DSL està completament desenvolupat. Si el llenguatge a desenvolupar aborda un domini complex, la possibilitat de que hi hagen errors en el DSL es major i solucionar-los podria implicar modificacions de gran calibre que podrien haver-se evitat. Com a solució, en aquesta tesis proposem un mètode de desenvolupament de DSLs, àgil i dirigit per models que involucra als usuaris finals. Aquesta tesis investiga si la combinació de bones pràctiques del desenvolupament dirigit per models (MDD) i de bones pràctiques de mètodes àgils es adequada per a involucrar els usuaris finals en el desenvolupament de DSLs. Per a validar la idoneïtat de la proposta, s'ha seleccionat un domini complex com el dels anàlisis genètics i s'ha col·laborat amb un conjunt de genetistes procedents de tres organitzacions. El mètode s'ha utilitzat per a involucrar a dits genetistes en el desenvolupament d'un DSL per a la creació de pipelines per al anàlisis genètic. Al mateix temps, s'ha dut a terme un experiment empíric per a validar si tant els usuaris finals com els desenvolupadors estan satisfets amb la proposta de la present tesis. En resum, les contribucions principals d'aquesta tesis doctoral son el disseny i implementació d'un mètode innovador, àgil i dirigit per models per a involucrar als usuaris finals en el desenvolupament de DSLs, així com la validació de la proposta en un entorn industrial amb un desenvolupament real d'un DSL.
Villanueva Del Pozo, MJ. (2016). An agile model-driven method for involving end-users in DSL development [Tesis doctoral no publicada]. Universitat Politècnica de València. https://doi.org/10.4995/Thesis/10251/60156
TESIS
32
Laanti, M. (Maarit). „Agile Methods in large-scale software development organizations:applicability and model for adoption“. Doctoral thesis, Oulun yliopisto, 2013. http://urn.fi/urn:isbn:9789526200347.
Der volle Inhalt der QuelleAnnotation:
Abstract Agile methods have proven to be beneficial in small organizations, and there has also been growing interest in using these methods in large organizations. This dissertation analyzes what agility and agile development are and creates a framework for using those methods in large organizations. The work starts with a Concept Analysis of Agile Software Development and agile-in-large. The theoretical part also reflects the necessary background of Complex Adaptive Systems, Lean Thinking, and Learning Organizations. Then a model of an Agile Enterprise is defined and a Framework for Organizational Development and putting Agile Methods into use in large software development organizations is presented. Large development organizations consist of many levels. It is not enough to use Agile Methods on a certain level only, e.g., on the lowest level, but all levels need to change and adapt to the new way of working. Failure to do so leads to several unwanted consequences, which are described. One possible large-scale Agile Framework is described and analyzed. The usage of Agile Methods on a large scale is validated by quantitative studies. The level of success of using an Agile Framework on a large scale is dictated by how much the same framework for operation is shared within the organization, as partial transformation leads to confusion. But smaller successes can lead into organizational learning. The framework that is proposed can be used to further enhance agility. In this way large-scale agility can be seen as a never-ending series of systematic improvements of the enterprises’ Agile AspectsTiivistelmä Tämä väitöskirja tarkastelee suurten organisaatioiden tarpeisiin sopivien ketterien prosessimallien mallinnusta ja käyttöä. Ketterät menetelmät on todettu hyödyllisiksi pienissä ohjelmistoyrityksissä, joten myös isoissa yrityksissä on herännyt kiinnostus ketteriä menetelmiä kohtaan. Työ alkaa ketterien menetelmien käsiteanalyysillä, ja jatkuu määrittelemällä mitä ketteryys laajassa mittakaavassa on. Teoriaosuus käsittelee taustatiedot kompleksisista sopeutuvista järjestelmistä, lean-ajattelusta ja oppivista organisaatioista tarvittavin osin. Tämän jälkeen määritellään ketterän yrityksen käsite ja esitetään malli laajamittaiselle ketteryydelle. Suurissa kehitysorganisaatioissa on monta tasoa. Ei riitä, että ketteriä menetelmiä käytetään vain jollakin (yleensä alimmalla) tasolla, vaan kaikkien organisaation tasojen täytyy sopeutua uuteen toimintatapaan. Mikäli näin ei tapahdu, saattaa tuloksena olla joukko ei-toivottavia seurauksia, jotka on myös kuvattu tässä työssä. Työssä on esitetty ja analysoitu mahdollinen malli suuren yrityksen ketteryyden toteuttamiseksi. Ketterien menetelmien käyttö isossa yrityksessä on validoitu kvantitatiivisin menetelmin. Isoissa yrityksissä ketteristä menetelmistä saatu hyöty on sidottu siihen miten hyvin koko organisaatio pystyy noudattamaan samaa ketterää toiminnan mallia – osittainen toimintatavan muutos johtaa toimintatapojen konflikteihin. Kuitenkin myös osittaiset onnistumiset voivat johtaa organisaation oppimiseen. Esitettyä mallia voidaan käyttää kehitettäessä toimintatapaa entisestään ketterämpään suuntaan. Tällä tavalla suuren organisaation ketteryys voidaan nähdä jatkuvana sarjana systemaattisia toimintatavan parannuksia, joista jokainen johtaa entistä ketterämpään toimintatapaan
33
Cassirer, Albin, und Erik Hane. „Model-Pipe-Hardware: Method for Test Driven Agile Development in Embedded Software“. Thesis, KTH, Maskinkonstruktion (Inst.), 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-182670.
Der volle Inhalt der QuelleAnnotation:
In this thesis, we present development and evaluation of a new test driven design method for embedded systems software development. The problem of development speed is one of major obstacles for transferring Test Driven Development (TDD) methodologies into the domain of embedded software development. More specically, the TDD cycle is disrupted by time delays due to code uploads and transfer of data between the development "host" system and the "target" embedded platform. Furthermore, the use of "mock objects" (that abstract away hardware dependencies and enable host system testing techniques) is problematic since it creates overhead in terms of development time. The proposed model, Model-Pipe-Hardware (MPH), addresses this problem by introducinga strict set of design rules that enable testing on the "host" without the need of the "mock objects". MPH is based on a layer principle, "trigger-event-loop" and supporting "target" architecture. The layer principle provides isolation between hardware dependent/independent code. The trigger-event-loop is simply a proxy between the layers. Finally, the developed testing fixture enables testing of hardware dependent functions and is independent of the target architecture. The MPH model is presented and qualitatively evaluated through an interview study and an industry seminar at the consulting company Sigma Technology in Stockholm. Furthermore, we implement tools required for MPH and apply the model in a small scale industry development project. We construct a system capable of monitoring and visualisation of status in software development projects. The combined results (from interviews and implementation) suggest that the MPH method has a great potential to decrease development time overheads for TDD in embedded software development. We also identify and present obstacles to adaptation of MPH. In particular, MPH could be problematic to implement in software development involving real-time dependencies, legacy code and a high degree of system complexity. We present mitigations for each one of these issues and suggest directions for further investigations of the obstacles as part of future work.I denna avhandling presenteras utveckling och utvärdering av en ny utvecklingsmetod för mjukvaruutveckling i inbyggda system. Långsam utvecklingshastighet ar ett stort hinder för applicerandet av Test Driven Utveckling (eng. Test-Driven-Development,TDD) inom inbyggda system. Mer specifikt, uppstår flaskhalsar i TDD cykeln på grund av koduppladdningar och dataöverföringar mellan utvecklingsmiljö (host) och plattformen för det inbyggda systemet (target). Vidare är användningen av "mock"-objekt (abstraherar bort hårdvaruberoenden for att möjliggöra tester i hostmiljö) kostsamt då implementatering och design av "mock"-objekten förlänger utvecklingstiden. Den förslagna modellen, Model-Pipe-Hardware (MPH), adresserar detta problem genom att introducera strikta designregler vilket möjliggör tester i hostmiljö utan användning av mocks. MPH bygger på en lagerprincip, en så kallad "trigger-event-loop" och en tillhörande hårdvaruarkitektur. Lagerprincipen möjliggör isolering mellan hårdvaru- beroende/oberoendekod medan trigger-event-loopen fungerar som en proxy mellan lagren. MPH presenteras och utvärderas genom en intervjustudie och ett industriseminarium på konsultbolaget Sigma Technology i Stockholm. Vidare implementeras nödvändig infrastruktur och MPH metoden har applicerarts på ett mindre industriellt utvecklingsprojekt. De kombinerade resultaten från intervjuer, seminarium implementering antyder att MPH har stor potential att öka utvecklingshastighet for TDD i inbyggda system. Vi identierar även möjliga hinder föor applicering av MPH i utveckling av inbyggda system. Mer specifikt kan MPH vara problematisk för inbyggda system som innefattar realtidskrav, så kallad "legacy kod" och för system med hög komplexitet. Vi föreslår möjliga lösningar för dessa problem och hur de bör utredas vidare som en del av framtida arbete.
34
Cabral, Izunildo Fernandes. „An information model for lean, agile, resilient and green supply chain management“. Master's thesis, Faculdade de Ciências e Tecnologia, 2011. http://hdl.handle.net/10362/6620.
Der volle Inhalt der QuelleAnnotation:
Dissertação para a obtenção de Grau de Mestre em Engenharia e Gestão IndustrialIn modern business environments, an effective Supply Chain Management (SCM) is crucial to business continuity. In this context, Lean, Agile, Resilient and Green (LARG), are advocated as the fundamental paradigm for a competitive Supply Chain (SC) as a whole. In fact, competition between supply chains (SC) has replaced the traditional competition between companies. To make a supply chain more competitive, capable of responding to the demands of customers with agility, and capable of responding effectively to unexpected disturbance, in conjugation with environmental responsibilities, and the necessity to eliminate processes that add no value, companies must implement a set of LARG SCM practices and Key Performance Indicators (KPI) to measure their influence on the SC performance. However, the selection of the best LARG SCM practices and KPIs is a complex decision-making problem, involving dependencies and feedbacks. Still, any decision-making must be supported by real and transparent data. This dissertation intends to provide two integrated models to assist the information management and decision-making. The first is an information model to support a LARG SCM, allowing the exchange and storage of data/information through a single information platform. In this model three types of diagrams are developed, Business Process Diagram (BPD), Use Cases Diagram and Class Diagram to assist the information platform design. The second is a decision-making model, designated LARG Analytical Network Process (ANP) to select the best LARG SCM practices/KPI to be implemented in SCs. Both models are developed and validated within the automotive SC, namely in Volkswagen Autoeuropa.
35
Garamendi-Colos, Virginia, Mercedes Cano-Lazarte, Nestor Mamani-Macedo, Carlos Raymundo und Francisco Dominguez. „Agile Inventory Management Model Under a Digital Transformation Approach for Stockout Reduction in Chemical Industry’s MSE“. Springer, 2020. http://hdl.handle.net/10757/656371.
Der volle Inhalt der QuelleAnnotation:
El texto completo de este trabajo no está disponible en el Repositorio Académico UPC por restricciones de la casa editorial donde ha sido publicado.Through digital transformation, company processes that are, or could be, conducted manually are reduced; moreover, human tasks are automated when software-based processes are established. This paper analyzes the adoption of a digital transformation tool to manage inventory through the application of agile models, such as Just-In-Time, and the use of Enterprise Resource Planning (ERP), employing the Deming cycle method, as several unclear empiric processes exist for managing inventory and purchases. It also upholds that as defined processes are established and the companies exert higher control over inventory turnover and outflows, they could apply methods, such as demand forecasting, to avoid stockout, supply shortage, and inventory loss.
36
Albonetti, Luca. „Modelli agili per lo sviluppo software: una panoramica su Scrum, Kanban e Scrumban“. Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2019. http://amslaurea.unibo.it/17834/.
Der volle Inhalt der QuelleAnnotation:
La tesi proposta analizza e confronta tre metodi agili: Scrum, Kanban e Scrumban. Per ogni metodo che viene presentato si approfondiscono i ruoli dei membri del team, le procedure, i rituali e le metriche che lo caratterizzano. Infine vengono presentati alcuni software (Taiga, Trello e UpWave) che i team agili possono sfruttare per applicare il modello scelto per la gestione del processo di sviluppo.
37
Lolli, Nicola. „Convergenze e divergenze tra analisi sismica con modelli di danno e con modelli agli elementi finiti: il caso del campanile della chiesa di San Michele Arcangelo di Novi (MO)“. Master's thesis, Alma Mater Studiorum - Università di Bologna, 2017. http://amslaurea.unibo.it/13618/.
Der volle Inhalt der QuelleAnnotation:
Il tema della tesi è lo studio della torre campanaria della chiesa di San Michele Arcangelo, sita in Novi di Modena. Tale struttura ha subito notevoli danni nel corso degli eventi sismici del 2012 che hanno coinvolto l’Emilia–Romagna, danni tali da rendere inagibile il campanile e la chiesa stessa.
Il tema, affrontato come esercitazione all’interno del laboratorio progettuale e, contestualmente, come tesi di laurea, è stato sviluppato a partire dalle consuete operazione di ricerca storica e rilievo, quest’ultimo reso difficoltoso dall’inaccessibilità della torre campanaria, a causa del crollo dei solai intermedi.
Una volta raggiunta una sufficiente conoscenza del manufatto, è stato possibile iniziare l’analisi del quadro fessurativo ed il confronto con i sei modelli di danno, tipici delle torri campanarie isolate, i quali fanno riferimento, esplicitamente, ai cinematismi.
Terminata l’analisi, si è passati alla realizzazione ed al raffinamento di un modello agli elementi finiti, che permettesse di riprodurre il più fedelmente possibile il comportamento reale della torre campanaria. La possibilità di impiegare un modello agli elementi finiti, nell’ambito di un’analisi modale, è riconosciuta dal DPCM 66 / 2011, al paragrafo 5.2.3, con le dovute accortezze del caso, trattandosi sempre di un modello virtuale che, pur fedele che sia, non potrà mai riprodurre le peculiarità e l’eterogeneità materica dell’elemento reale.
Una volta definito il modello, è stato possibile dedicarsi al fine ultimo della tesi, ovvero il confronto tra i risultati ottenuti mediante l’analisi dei modelli di danno e l’analisi agli elementi finiti.
Infine, ma non meno importante, l’aspetto progettuale: seguendo le indicazioni del prof. Ing. Angelo Di Tommaso, si è scelto di realizzare una struttura reticolare all’interno del fusto del campanile, in modo da fornire resistenza alle azioni taglianti, caratteristica al momento assente, trattandosi di una struttura interamente in muratura.
38
Sousa, Fátima Carina Gonçalves. „Utilização do modelo SCRUM na Megasis“. Master's thesis, Instituto Superior de Economia e Gestão, 2018. http://hdl.handle.net/10400.5/20214.
Der volle Inhalt der QuelleAnnotation:
Mestrado em Gestão de Sistemas de InformaçãoO presente Trabalho Final de Mestrado tem como objetivo descrever todas as atividades desenvolvidas durante a realização do estágio curricular no Centro de Business Intelligence da Megasis/TAP IT, colocando em prática e consolidando conhecimentos adquiridos ao longo do mestrado. Aborda um conjunto de atividades que permitem a automatização de vários processos manuais associados ao modelo Agile de desenvolvimento de software e dá também a conhecer como é aplicada a metodologia Scrum num departamento de Business Intelligence. O relatório começa por dar conta da revisão da literatura explicando o que é o scrum, quem são os participantes e quais as coreografias. De seguida, são descritas as atividades desenvolvidas no estágio, desde o enriquecimento do modelo de dados de scrum com novos conceitos como também a criação de relatórios e dashboards, sendo estes o output final da solução de BI. É feita uma análise critica comparando a literatura existente e as atividades do estágio assim como uma apreciação pessoal sobre as mesmas. As atividades são descritas e acompanhadas com o anexo de imagens dos vários dashboards criados.
The purpose of this master's Report is to describe all the activities developed during the internship at the Megasis/TAP IT Business Intelligence Center, putting into practice and consolidating knowledge acquired through out the master's program. It addresses a set of activities that allow the automation of several manual processes associated with the Agile model of software development. It also shows how the Scrum model is applied in a Business Intelligence Department. The literature review describes topics such scrum, the participants and the events. What it comes next is the description of the activities of the internship, the enrichment of the model of scrum with new concepts and last the dashboards and reports that are the BI final solution output. A critical analysis, as well as a personal assessment, is made comparing the existing literature and the internship activities. The activities are described and accompanied by image attachments of the various dashboards created.
info:eu-repo/semantics/publishedVersion
39
Mostafa, Dina. „Maturity models in the context of integrating agile development processes and user centred design“. Thesis, University of York, 2013. http://etheses.whiterose.ac.uk/6295/.
Der volle Inhalt der QuelleAnnotation:
Integrating Agile development processes and User Centred Design (UCD) gained increased interest arguably due to three reasons: first, the reported advantages of UCD in enabling developers to understand the users needs, and how the software can support their goals. Second, the deficiency of Agile methods in: providing guidance for developing usable software; and discussing usability, user requirements elicitation and usability evaluation methods. Third, differences between Agile methods and UCD that can make their integration challenging. Agile and User Centred Design Integration (AUCDI) research did not exploit Usability Maturity Models (UMMs) potential. Organizations aspiring to achieve AUCDI can utilize UMMs in assessing its UCD capability, identifying organization's UCD weaknesses and strengths, and planning for improvement. This thesis aims to investigate the suitability of utilizing UMMs in the context of Agile processes. In order to achieve this aim, this thesis conducted: first, a Systematic Literature Review (SLR) that identified and classified AUCDI challenges and explored the proposed practices to deal with them. Second, an interview study of industrial AUCDI attempts that identified the AUCDI difficulties and integration methods. Third, an interview study that evaluated the suitability of two UMMs; Nielsen model and Usability Maturity Model-Human Centrdness Scale (UMM-HCS) for utilization in assessing usability maturity levels in the context of Agile projects. The results of these studies revealed that both models are deficient in their theoretical maturation foundations and scoring scheme and in addressing the activities and challenges associated with AUCDI. As a result of these deficiencies we utilized the results of the SLR and the empirical studies in developing a set of dimensions that represent fundamental elements that affect the AUCDI process. These dimensions were utilized in the development of a descriptive AUCDI Maturity Model that addresses the activities, success factors, and challenges identified within the AUCDI domain.
40
Madhira, Phani Srikara Sastry. „Investigating the Applicability of Agile Practices in Software Organizations“. Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4377.
Der volle Inhalt der QuelleAnnotation:
Agile software development has gained significant importance the recent years. Software practitioners have recognized the importance of agile development due to the benefits offered. Therefore, agile software development has been identified as the replacement to traditional or plan driven style of development. There are different frameworks or methods, which follow agile principles, known as agile methodologies. SCRUM and XP are the most popular and widely used agile methods or framework. There are different types of agile methodologies, each containing a set of practices, which can be adapted and implemented in an organization. However, there is still a need for empirical studies to understand the factors like requirements/modifications, challenges and mitigation strategies/techniques, which can enable successful implementation of agile practices in software organizations. In this study, the primary objective is to provide a comprehensive model or framework to practitioners, which includes the list of important requirements/modifications, challenges and mitigation strategies/techniques while implementing agile, and also pertaining to adoption/implementation of individual agile practices specific to SCRUM and XP. This model also includes the categorization of the requirements/modifications and challenges into different levels of an organization, to which they mostly apply. This conceptual model or framework can aid the practitioners in understanding and implementing agile practices in a better way in their organizations. In this study, an industrial survey is conducted in order to identify the list of important requirements/modifications that are needed to implement agile, challenges faced during implementation, and mitigation strategies/techniques needed to address the challenges. Also, categorization of the identified lists into different levels of the organization is also performed using survey. A systematic literature review is performed in order to identify the primary lists of requirements/modifications, challenges and mitigation strategies/techniques, which are further validated and classified using survey. Also, systematic literature review is used to identify the list of requirements/modifications, challenges and mitigation strategies/techniques that are needed while implementing individual agile practices specific to SCRUM and XP. Based on the systematic literature review, 53 primary studies were identified which are relevant to the research area. Upon analyzing the primary studies, the list of requirements/modifications, challenges and solutions are identified for generic agile adoption/implementation and also pertaining to individual practices specific to SCRUM and XP. Thereupon, an industrial survey is conducted where, identified list of requirements/modifications, challenges and mitigation strategies/techniques are provided to the respondents. Respondents were asked to classify the obtained aspects based on the level of importance. Also, they were asked to categorize the obtained requirements/modifications and challenges into different levels of an organization. The survey has obtained 48 responses from different parts of the world. From the results of survey, requirements/modifications, challenges and mitigation strategies/techniques are classified based on the level of importance. Also, requirements/modifications and challenges are categorized into different levels of an organization. Using the obtained factors, a conceptual model or framework was constructed for practitioners that can enable them to understand and implement agile practices in their organizations in a better way. To conclude this research, a comprehensive model or framework was constructed using the final list of important requirements/modifications, challenges and mitigation strategies/techniques while implementing/adopting agile and also pertaining to the individual agile practices, and also based on the categorization of the requirements and challenges into levels of an organization, where they are applicable. The final list of identified lists of requirements/modifications; challenges and mitigation strategies/techniques pertaining to individual agile practices can help practitioners to understand the implementation criteria of agile practices in software organizations. It was observed from the results of survey that perception of literature and practitioners are different in terms of usage of agile practices, as some practices, which were given high focus in the literature, were not given equal priority by the respondents. Empirical findings also help to identify change in policies and procedures and change to open workspace as most important requirements/modifications, organizational resistance and lack of motivated programmers as most critical challenges and proper training and inclusion of experts as most used mitigation strategies/techniques. Moreover, it was concluded that there is also a need for further full-scale empirical works on identifying the factors that affect adoption of agile. Practitioners can identify the benefits from this research and researchers can extend this work to remaining agile methodologies.Agile systemutveckling har fått stor betydelse de senaste åren. Programvaru utövare har insett vikten av agila utvecklings grund av de förmåner som erbjuds. Därför har agile mjukvaruutveckling identifierats som ersättare till traditionella eller planen driven stil av utveckling. Det finns olika ramar eller metoder, som följer agila principer, så kallade agila metoder. SCRUM och XP är de mest populära och mest använda agila metoder eller ramverk. Det finns olika typer av agila metoder, var och en innehåller en uppsättning metoder, som kan anpassas och genomföras i en organisation. Det finns dock fortfarande ett behov av empiriska studier för att förstå de faktorer som krav / modifieringar, utmaningar och begränsningsstrategier / tekniker, som kan göra det möjligt för ett framgångsrikt genomförande av agila metoder i mjukvaruorganisationer. I denna studie, är det primära målet att ge en heltäckande modell eller ramverk för utövare, vilket inkluderar en lista över viktiga krav / modifieringar, utmaningar och begränsningsstrategier / tekniker samtidigt genomföra vig, och även avseende antagande / genomförande av enskilda agila metoder specifika SCRUM och XP. Denna modell innehåller även kategoriseringen av de krav / modifieringar och utmaningar i olika nivåer i en organisation, till vilken de oftast gäller. Denna konceptuella modell eller ramverk kan hjälpa utövarna att förstå och genomföra agila metoder på ett bättre sätt i sina organisationer. I denna studie är en industriell undersökning för att identifiera listan över viktiga krav / ändringar som behövs för att genomföra vig, utmaningar under genomförandet, och begränsnings strategier / tekniker som behövs för att ta itu med utmaningarna. Också, kategorisering av de identifierade listorna i olika nivåer i organisationen är också utföras med undersökningen. En systematisk litteraturöversikt görs för att identifiera de primära listor krav / modifieringar, utmaningar och begränsningsstrategier / tekniker, som är validerade längre och klassificerade med hjälp enkät. Dessutom är systematisk litteraturöversikt används för att identifiera en lista över krav / modifieringar, utmaningar och begränsningsstrategier / tekniker som behövs samtidigt genomföra enskilda agila metoder som är specifika för SCRUM och XP.
+918500053444
41
Nascimento, Gustavo Vaz. „Um modelo de referência para o desenvolvimento ágil de software“. Universidade de São Paulo, 2007. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-07052008-170413/.
Der volle Inhalt der QuelleAnnotation:
A crescente procura por software de qualidade vem causando grande pressão sobre as empresas que trabalham com desenvolvimento de software. As entregas de produtos de software dentro do prazo e custo previstos vêm se tornando, a cada dia, um diferencial importante nesse ramo de atividade. Nesse sentido, as empresas procuram por metodologias que propiciem o desenvolvimento de produtos com qualidade, e que respeitem o custo e prazo previstos. Em resposta a essas necessidades, surgiu uma nova classe de metodologias de desenvolvimento de software, conhecidas como metodologias ágeis. Este trabalho apresenta um estudo realizado sobre as principais características existentes nessa nova classe de metodologias. Uma análise permitiu a identificação de semelhanças e diferenças existentes entre elas, o que possibilitou a criação de um modelo de referência para o desenvolvimento ágil de software. O modelo foi utilizado em uma avaliação de processo baseada no modelo de avaliação da ISO/IEC 15504. A avaliação permitiu a identificação de forças e fraquezas no processo avaliado e possibilitou a definição de ações de melhoria para que o processo avaliado se assemelhasse à um processo de desenvolvimento ágil. Palavra-chave: Metodologia ágil de desenvolvimento. Modelo de referência. Processo de desenvolvimento de software. Avaliação de processo de softwareThe vast demand for software with quality is causing a great pressure on the companies which work with software development. The delivery of software products within the schedule and cost is becoming, every day, an important issue in this area. Therefore, companies are seeking for methodologies to develop products with quality, within the timetable and the cost. Considering these needs, it became a new class of software development methodologies, known as agile methodologies. This research shows a work done upon the main existing characteristics in this new class of methodologies. An analysis allowed the identification of the existing similarities and differences among them, which it made possible to create a new reference model for agile software development. The agile model was used in process assessment based on assessment model from ISO/IEC 15504. The assessment alowed a identification of power and weakness on the process and alowed a definition of improvement action to the process with the intention of to approach the agile development process
42
Sammadyar, Abdul Wahid. „An investigation into the appropriateness of using agile processes to build an educational management information system“. Thesis, University of the Western Cape, 2010. http://etd.uwc.ac.za/index.php?module=etd&action=viewtitle&id=gen8Srv25Nme4_4324_1308727180.
Der volle Inhalt der QuelleAnnotation:
Since there was a need for an Educational Management Information System (EMIS) in the Ministry of Education in Afghanistan, we designed and implemented a prototype for use in the ministry and investigated the appropriateness of using Agile methods for producing the EMIS. The prototype consisted of a database containing data about schools and a Dari interface which was used by educational planners, managers and policy makers of the ministry for decision making and planning. Agile methods are relatively new in software engineering and have an approach and development guidelines which strive for user satisfaction and early incremental delivery of software. We adapt them to local conditions due to their collaborative client-developer approach. The interface, a key component, is easy to use and e cient. The key research result is an evaluation concerning the appropriateness of using Agile Methods for developing the EMIS. Focus groups and surveys were used to develop the prototype and accomplish the study.
43
Beisheim, Maja, und Charline Langner. „Lean Startup as a Tool for Digital Business Model Innovation : Enablers and Barriers for Established Companies“. Thesis, Jönköping University, IHH, Företagsekonomi, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-52579.
Der volle Inhalt der QuelleAnnotation:
Background: The rapidly changing world of digital technologies forces many companies to undertake a digital shift by transforming existing business models into digital business models to achieve sustainable value creation and value capture. Especially, for established companies, that have been successful leaders before the dot-com bubble (1995-2000) and whose business models have been threatened by the emergence of digital technologies, there is a need for a digital shift. We refer to this digitization of business models as digital business model innovation. However, often adoption and implementation of digital technologies require tremendous changes and thus, can be challenging for established companies. Therefore, agile methods and business experimentation have become important strategic elements and are used to generate and test novel business models in a fast manner. We introduce lean startup as an agile method for digital business model innovation, which has proven to be successful in digital entrepreneurship. Thus, it requires further empirical investigation on how to use lean startup in established companies for successful digital business model innovation. Purpose: The purpose of our study is to identify enablers and barriers of lean startup as a tool for digital BMI in established companies. Thus, we propose a framework showing how established companies can be successful in digital business model innovation by using lean startup. Method: We conducted exploratory, qualitative research based on grounded theory following an abductive approach. Using a non-probability, purposive sampling strategy, we gathered our empirical data through ten semi-structured interviews with experts in lean startup and digital business model innovation, working in or with established companies, shifting their business model towards a digital business model. By using grounded analysis, we gained an in-depth understanding of how lean startup is used in practice as well as occurring barriers and enablers for established companies. Conclusion: We emphasize that successful use of lean startup for digital business model innovation is based on an effective (1) lean startup management, appropriate (2) organizational structures, fitting (3) culture, and dedicated (4) corporate governance, which all require and are based on solid (5) methodical competence of the entire organization. Furthermore, (6) external influences such as market conditions, role of competition, or governance rules indirectly affect using lean startup as a tool for digital business model innovation.
44
Naseem, Junaid, und Wasim Tahir. „Study and analysis of the challenges and guidelines of transitioning from waterfall development model to Scrum“. Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2679.
Der volle Inhalt der QuelleAnnotation:
Software engineering practices have experienced significant changes over the period of past two decades. Keeping in view the competitive market trends, now is the high time for many organizations to shift from traditional waterfall models to more agile technologies like Scrum [22][23]. A change of this magnitude is often not easy to undertake. The reason that both software engineering techniques are different in many respects, organizations require considerable amount of analysis of the whole transitioning process and possible scenarios that may occur along the way. Small and medium organizations are normally very skeptical to the change of this magnitude. The scale of change is not limited to only software processes, in fact, difficult part is to deal with old attitudes and thinking processes and mold them for the new agile based Scrum development. The process of change therefore need to be understood in the first place and then carefully forwarded to the implementation phase.
45
Kurtagic, Anessa. „Working With Agile Methodologies During The Covid-19 Pandemic : A qualitative study of an agile teams' transition to remote work from home as a result of the Covid-19 pandemic“. Thesis, Linnéuniversitetet, Institutionen för informatik (IK), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-106923.
Der volle Inhalt der QuelleAnnotation:
Remote work was already an ongoing trend amongst software developers, but the sudden and unexpected occurrence of the COVID-19 pandemic made it normal due to the obligations for many people to stay and work from home. To go from the safeness of the work office with an always-working Internet connection and colleagues around to exchange ideas with, to working from home can be a big change from one day to another. Without a good structure or adjustment from the organization, this would lead to a decrease in good work results, communication issues and difficulty for managers to keep track of what is done and by whom. To facilitate this, commonly used methods are the Agile Methodologies. Beck et al. (2001) make it significant in the 12 principles of Agile that the most efficient and effective method of conveying information is by face-to-face conversation for the best results. Investigating the work that was done face-to-face previous to the pandemic but is now done remotely from home within agile teams is therefore of much relevance today. This thesis was intended to investigate and learn how the use of agile methodologies has facilitated the sudden transition to remote work from home and affected the aspects of communication and work results within an agile development team. The study was conducted using the qualitative method with interviews consisting of seven open-response and two closed-response questions with respondents in agile teams from a software development company in Sweden. The analysis was made thematically in relation to Bridge’s Transition Model, and in relation to previous research. The study identified three themes to answer the research question based on the theoretical framework; The Change, Communication and Work Results. The results of the study show that the use of Agile Methodologies indeed has simplified the sudden transition to remote work from home, which was called The Change, as many of the agile practices already were done online previous to the pandemic. The study has also concluded that the use of Agile Methodologies has positively affected the aspects of communication and work results in an agile team, as it was found that forms of communication became more creative as they occurred more frequently while working from home, and it ultimately led to more valuable end-results.Distansarbete var redan en pågående trend bland mjukvaruutvecklare, men den plötsliga och oväntade förekomsten av COVID-19-pandemin gjorde det normalt på grund av restriktionerna för många människor att arbeta hemifrån. Att gå från arbetskontorets säkerhet med en alltid fungerande internetuppkoppling och kollegor runt om för att diskutera idéer med, till att arbeta hemifrån kan vara en stor förändring från en dag till en annan. Utan en bra struktur eller anpassning från organisationen skulle detta leda till en minskning av goda arbetsresultat, dålig kommunikation och svårigheter för chefer att hålla reda på vad som görs och av vem. Vanliga metoder att använda för att underlätta detta är de agila metoderna. Beck et al. (2001) gör det tydligt i de 12 principerna för Agile att den mest effektiva metoden för att förmedla information i ett projekt är genom konversationer face to face, för bästa resultat. Att undersöka det arbete som innan pandemin gjordes face to face men nu görs på distans hemifrån inom agila team är därför av stor relevans idag. Denna studie var avsedd att undersöka och få kunskap om hur användningen av agila metoder har underlättat den plötsliga övergången till distansarbete hemifrån och påverkat aspekterna av kommunikation och arbetsresultat inom ett agilt utvecklingsteam. Studien genomfördes med hjälp av den kvalitativa metoden med intervjuer bestående av sju öppna frågor och två slutna svarfrågor med respondenter i agila team från ett mjukvaruutvecklingsföretag i Sverige. Analysen gjordes tematiskt i förhållande till Bridge’s Transition Model och i förhållande till tidigare forskning. Studien identifierade tre teman för att besvara forskningsfrågan utifrån det teoretiska ramverket; The Change, Communication och Work Results. Resultaten av studien visar att användningen av agila metoder har förenklat den plötsliga övergången till distansarbete hemifrån, eftersom många av de agila aktiviteterna redan gjordes online före pandemin. Studien har också dragit slutsatsen att användningen av agila metoder har påverkat aspekterna kommunikation och arbetsresultat positivt i ett agilt team, eftersom det visade sig att kommunikationsformer blev mer kreativa eftersom kommunikationen blev mer frekvent inträffande när de arbetade hemifrån, och det ledde slutligen till mer värdefulla slutresultat i projekt.
46
Ittner, Jan. „Software assisted tailoring of process descriptions“. Saarbrücken VDM Verlag Dr. Müller, 2006. http://d-nb.info/987892932/04.
Der volle Inhalt der Quelle
47
Feijoo, Pérez Nataly Eliana. „Modelo híbrido de gestión de portafolio para pequeñas empresas“. Master's thesis, Universidad Peruana de Ciencias Aplicadas (UPC), 2020. http://hdl.handle.net/10757/652239.
Der volle Inhalt der QuelleAnnotation:
El objetivo del presente trabajo de investigación es proponer un modelo híbrido para la gestión de portafolio en pequeñas empresas, siguiendo buenas prácticas de enfoques adaptativos y predictivos. El modelo propuesto se basa en el supuesto de que cada organización ya tiene identificado recursos humanos con el compromiso, habilidades y experiencia necesarios para trabajar bajo una nueva gestión estratégica con métodos agiles.
El modelo adaptativo está basado en el Agile Practice Guide (Project Management Institute, 2017), el estándar para la gestión de portafolio (Project Management Institute, 2017) y la Business Case Essentials: A Guide to Structure and Content (Schmidt, 2003) que es una guía para la elaboración de casos de negocio. De estos, se han tomado conceptos, técnicas y herramientas que han permitido proponer un modelo sencillo de gestión de portafolio que pueda ser adaptado a pequeñas organizaciones.
Por último, es importante indicar que la propuesta del trabajo de investigación se elaboró teniendo como modelo una pequeña empresa de consumo masivo, llamada AFS Consumo EIRL, ubicada en Lima – Perú. Previo a iniciar con el diseño del modelo, se realizaron algunos análisis y diagnósticos, por medio de entrevistas a los miembros de la organización, para finalmente proponer el modelo descrito en el presente trabajo.The objective of this work is to propose a Hybrid Portfolio Management Model in small enterprises, following adaptive and predictive approaches and applying the Standard for Portfolio Management. This model is based on the assumption that each organization has already identified human resources with the commitment, skills and experience necessary to work under a new strategic agile management. The adaptive model is based on the Agile Practice Guide (Project Management Institute, 2017), The Standard for Portfolio Management (Project Management Institute, 2017) and the guide Business Case Essentials: A Guide to Structure and Content (Schmidt, 2003). This work takes concepts, techniques and tools from these three documents to propose a simple portfolio management model that can be adapted to any organization. Finally, it is important to indicate that the research work proposal was prepared using as a model, a small mass consumption company called AFS Consumo EIRL, located in Lima - Peru. Before starting to design this model, some analyzes and diagnoses were carried out through interviews with the members of the organization to finally propose the model described in this work.
Trabajo de investigación
48
Arnelo, Albin, und Broberg Nicole Fogelgren. „Agile Contracts Implementation for Industrial Companies Purchasing Embedded Systems“. Thesis, KTH, Skolan för industriell teknik och management (ITM), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-278900.
Der volle Inhalt der QuelleAnnotation:
The continuous advances and prevalence of embedded systems, being systems consisting of both hardware and software put together, provides a great challenge for industrial companies. Due to the increasing need of complex products to meet the demands of customers, companies more often need to source software from external suppliers. Software has the characteristic of being a product which is difficult to specify as it has the ability to iteratively update itself according to the changing environment, making it hard to determine precisely what it will look like at the beginning of its development. As a result, traditional waterfall contracts, for which the intention is to set clear specifications early on, are often not suitable for developing systems including software. Therefore, the need for flexible contracts, called agile contracts, among industrial companies is emerging to support new technological applications. The purpose of this thesis was to examine what the main challenges are when implementing agile contracts in industrial companies who are purchasing embedded systems, and how these challenges can be mitigated or rectified. This was done by an empirical study in the form of interviews with various relevant actors. Firstly, employees from an industrial company looking to implement agile contracts within its procurement processes to support its embedded system purchases were interviewed. The respondents expressed their concerns and perceived challenges with introducing agile contracts to their business. Then, to answer the challenges interviews were conducted with people who were knowledgeable within the topic of agile contracts. Also, a benchmark, a literature review and a theoretical framework have been performed to analyse previous findings within this research area. This thesis identified nine main challenges being Risk Management, Payment Model, Time Aspect, Communication, Embedded Systems, IP-Rights, Supplier Management, Mindset & Knowledge and Future. Each of these challenges was answered separately, but it was found that some answers overlapped between different challenges. The most prevalent challenge was regarding communication, as a successful relationship built on sufficient collaboration and trust lays a foundation for all the other challenges to be managed more easily. Another recurrent theme was that all involved parties must understand precisely what an agile contract implies in order to make beneficial decisions to manage all the challenges.De kontinuerliga framstegen för inbyggda system, som består av både hårdvara och mjukvara sammansatt innebär en stor utmaning för industriella företag. På grund av det ökade behovet av mjukvara för att möta kundernas efterfrågan behöver företag köpa in mjukvara från externa leverantörer. Mjukvara är svårt att specificera eftersom det har förmågan att iterativt uppdatera sig själv i enighet med den förändrade miljön. Detta gör det svårt att i ett tidigt skede av ett projekt fastställa exakt hur produkten ska vara utformad. På grund av detta är traditionella kontrakt, som ofta följer vattenfallsmodellen för vilken avsikten är att tidigt sätta tydliga kravspecifikationer, sällan lämpade för att köpa in inbyggda system. Därav uppstår behovet av agila kontrakt bland industriföretag för att stödja nya tekniska tillämpningar. Syftet med denna avhandling var att undersöka vilka de huvudsakliga utmaningarna är gällande att implementera agila kontrakt på ett industriföretag som köper in och utvecklar inbyggda system samt hur dessa utmaningar kan bemötas. Detta gjordes i form av en empirisk studie med relevanta aktörer, främst inom ett industriföretag som avser att implementera agila kontrakt i sin inköpsprocess för att effektivisera inköp av inbyggda system. Först intervjuades medarbetare som idag köper in inbyggda system. Dessa fick uttrycka sina tveksamheter och utmaningar kring att implementera agila kontrakt i sin inköpsprocess. Efter det utfördes mer strukturerade intervjuer med kunniga personer inom agila kontrakt med målet att hitta lösningar till de tidigare identifierade utmaningarna. Dessa intervjuer i kombination med en litteraturstudie, ett teoretiskt ramverk och en benchmark användes för att analysera och besvara de identifierade utmaningarna. Denna avhandling identifierade nio huvudsakliga utmaningar från de explorativa intervjuerna; Riskhantering, Betalningsmodell, Tidsaspekt, Kommunikation, Inbyggda System, IP-Rättigheter, Mentalitet & Kunskap samt Framtid. Dessa utmaningar har alla blivit besvarade separat men det fastställdes tidigt att de finns tydliga överlappningar mellan utmaningarna. Den vanligaste överlappningen var angående kommunikation då en framgångsrik relation byggd på samarbete och förtroende lägger grunden för att alla andra utmaningar lättare ska kunna bemötas och lösas. Ytterligare ett återkommande tema var att alla parter måste förstå exakt vad ett agilt kontrakt innebär och hur det fungerar för att kunna fatta rätt beslut och hantera övriga utmaningar.
49
Gryc, Radim. „Využití agilních metod ve startupu“. Master's thesis, Vysoké učení technické v Brně. Fakulta podnikatelská, 2015. http://www.nusl.cz/ntk/nusl-224977.
Der volle Inhalt der QuelleAnnotation:
This master thesis deals with choice of appropriate approach to software development. The thesis specifies currently used approaches of project management. Current project status and approaches are analysed. The thesis focuses on choice of method and its application in the project.
50
Santos, João Paulo Pereira dos. „A simulation model for lean, agile, resilient and green supply chain management: practices and interoperability assessment“. Master's thesis, Faculdade de Ciências e Tecnologia, 2013. http://hdl.handle.net/10362/10972.
Der volle Inhalt der QuelleAnnotation:
Dissertação para obtenção do Grau de Mestre em
Engenharia e Gestão IndustrialIn today’s global market, the environment of unpredictable events has imposed a competitiveness improvement that requires a greater coordination and collaboration among Supply Chain (SC) entities, i.e., an effective Supply Chain Management (SCM). In this context, Lean, Agile, Resilient and Green (LARG) strategies emerged as a response. However, interoperability issues are always presents in operations among SC entities. From the Information Technology (IT) perspective, among all the multi-decisional techniques supporting a logistics network, simulation appears as an essential tool that allow the quantitative evaluation of benefits and issues deriving from a co-operative environment. The present work provides a SC simulation model for analysing the effect of the interoperability degree of LARG practices in the SC performance, through Key Performance Indicators (KPI’s) such as cost, lead time and service level. The creation of two scenarios with a different point of view about the LARG practices allowed to analyse which one contributes to the best SC performance. Since some of the inputs were assumed, it was made a sensitivity analysis to validate the output of the simulation model. Based on the creation of six types of math expressions, it was possible to establish the connection between the effect of the interoperability degree of LARG practices and the SC performance. This analysis was applied on a case study that was conducted at some entities of a Portuguese automotive SC. The software used to develop the simulation model is Arena, which is considered a user-friendly and dynamic tool. It was concluded that SCM, interoperability and simulation subjects must be applied together to help organisations to achieve overall competitiveness, focusing their strategies on a co-operative environment.