With its core in adaptability and change responsiveness, the Agile methodology has become a popular application of the project process within the often volatile environment of today’s software development projects. The Agile methodology emphasizes interaction between project roles over documentation and formal processes. This higher interaction increases the need for functioning information dissemination throughout the entire project process. The study was carried out at a small sized Swedish IT consultancy firm. The company wished to acquire a project management and planning software tool to support the entire project process and all involved project roles. However, awareness of areas in the project process in need of support was not entirely clear. Therefore, the objective of the study was to investigate the company’s application of the Agile project process and identify potential challenges. Furthermore, the objective was to investigate how a project management and planning software tool can support the Agile project process within software development. The thesis was carried out as an abductive case study, where qualitative data collection methods and literature studies were combined. As a result from the study, two main conclusions have been drawn. Firstly: requirements engineering, the customer role, communication, and knowledge transfer were concluded as prominent challenges in the project process in need of increased support. Secondly, a project management and planning software tool can support the project process by: increasing the communication and collaboration abilities, providing holistic and historical project overview, providing a single storage location, and providing structure. Furthermore, the study has also shown that the project management and planning software tool needs to interact with the Agile project process in order to provide successful support. As final contribution, the Interaction model was created. The model visualizes the main areas in which a project management and planning software tool must interact with the Agile process, in order to support the entire project process successfully. / Genom dess anpassningsförmåga och förändringsmottaglighet har den Agila metodiken blivit en populär tillämpning för projektprocessen inom mjukvaruutveckling, en miljö där snabba förändringar tillhör vardagen. Den Agila metodiken framhäver interaktion mellan projektroller  framför  dokumentation  och  formella  processer,  vilket  ökar  behovet  av fungerande informationsspridning genom hela projektprocessen. Studien  har  utförts  hos  ett  mindre  svenskt  IT-konsultföretag,  vilket  önskade  att införskaffa en programvara för ett projektlednings- och planeringsverktyg som kan stötta hela  projektprocessen  och  alla  involverade  projektroller.  Medvetenheten  kring  de områden i projektprocessen som är i behov av stöd var däremot inte helt tydlig. Målet med   studien   var   därför   att   undersöka   företagets   tillämpning   av   den   Agila projektprocessen  och  identifiera  eventuella  utmaningar.  Vidare  var  målet  också  att undersöka hur en programvara för ett projektlednings- och planeringsverktyg kan stödja den Agila projektprocessen inom mjukvaruutveckling. Examensarbetet utfördes som en abduktiv fallstudie där flera kvalitativa datainsamlingsmetoder användes tillsammans med litteraturstudier. Som resultat av studien har två huvudslutsatser dragits. För det första; kravhantering, kundrollen, kommunikation  och  kunskapsöverföring  identifierades som framträdande utmaningar i projektprocessen i behov av ökat stöd. För det andra, att en programvara för ett projektlednings- och planeringsverktyg kan stödja projektprocessen genom att; förbättra  kommunikations-  och  samarbetsmöjligheterna,  ge  en  övergripande  och historisk projektöverblick, fungera som en gemensam lagringsplats och tillhandahålla struktur.  Vidare  har  studien  visat  att  en  programvara  för  ett  projektlednings-  och planeringsverktyg  måste  interagera  med  den  Agila  projektprocessen  för  att  ge  ett effektivt  stöd.  Som  ett  slutligt  bidrag  skapades  "the  Interaction  model",  vilken visualiserar huvudområdena inom vilka en programvara för ett  projektlednings- och planeringsverktyg måste interagera med projektprocessen för att ge ett fullt stöd till processen.

Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2016-03-15T15:42:08Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Uncertanty Management in Software Projects - Marcelo Marinho.pdf: 6691446 bytes, checksum: c11ad7bca6e24d387867ffea22b8e5ed (MD5) / Made available in DSpace on 2016-03-15T15:42:08Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Uncertanty Management in Software Projects - Marcelo Marinho.pdf: 6691446 bytes, checksum: c11ad7bca6e24d387867ffea22b8e5ed (MD5) Previous issue date: 2015-11-11 / Various projects types are proposed with different objectives; it is necessary to manage strategically, according to organizational goals. Successful projects increase sales, reduce costs, improve quality, customer satisfaction, the work environment; among other benefits. An increasing number of companies use project management as a key strategy for maintaining competitiveness, increasing the value possibility to their business. However, many projects with all the ingredients for success fail. One reason for this is related to failure in assessing the uncertainties by executives, managers and project team. In a typical software development environment it is not different. Thus, the aim of this work is to propose an approach to manage uncertainties in software projects to contribute to their better performance and influence their success. The research method used in this work is based on the principles of Evidence-Based Software Engineering. During the guide conception stage an exploratory literature research on managing uncertainty in software projects and a systematic literature review on the state of the art theme in a more structured way along with an action research conducted in a software development project were conducted. In addition, semi-structured interviews with software industry experts and researchers in the field were carried out in order to obtain improvement to the approach. In the evaluation phase a focus group was conducted to evaluate the proposed approach. The results showed that an exploratory literature review helped to characterize the difference between risk and uncertainty and mapped the uncertainty sources. The systematic literature review found 5 ways to manage uncertainties in projects; 18 practices for project management focusing on reducing uncertainties; a confirmation of the uncertainty sources mapped in primary studies and the relationship between uncertainty and innovative projects was assessed. In the action research there was an application of techniques and strategies in projects and investigation on whether those contributed to uncertainty; in semi-structured interviews the addition of the practical point of view for the approach was evaluated and added. Finally, the focus group was performed to assess the elaborated approach. The results of this research contribute to software project management by defining an approach to uncertainty management, as well as describing strategies and guidelines for team members. / Vários tipos de projetos são propostos, com diferentes objetivos, em que é preciso gerenciálos estrategicamente de acordo com metas organizacionais. Projetos bem sucedidos aumentam as vendas, reduzem os custos, melhoram a qualidade, a satisfação do cliente, o ambiente de trabalho, entre outros benefícios. Assim, um número crescente de empresas utilizam o gerenciamento de projetos como uma estratégia fundamental para manter a competitividade, aumentando a possibilidade de valor aos seus negócios. No entanto, muitos projetos com todos os ingredientes para o sucesso, falham. Um dos motivos porque isso acontece relaciona-se com a não avaliação das incertezas pelos executivos, gerentes e equipe do projeto. Em um ambiente de desenvolvimento de software típico não é diferente. Baseado nisso, o objetivo geral deste trabalho é propor uma abordagem para gerenciar as incertezas em projetos de software, contribuindo assim para um melhor desempenho dos projetos de software e influenciando no seu sucesso. O método de pesquisa adotado neste trabalho está fundamentado nos princípios da Engenharia de Software baseado em evidências. Foi realizada uma pesquisa exploratória da literatura sobre gerenciamento das incertezas em projetos de software. Em seguida, de forma mais estruturada, foi realizada uma revisão sistemática da literatura sobre o estado da arte do tema juntamente com uma pesquisa-ação, conduzida em um projeto de desenvolvimento de software. Além disso, entrevistas semi-estruturadas foram realizadas com especialistas da indústria de software e pesquisadores na área a fim de avaliar as evidências encontradas e adicionar insumos para a abordagem. Na fase de avaliação foi realizado um grupo focal com especialistas que avaliaram a abordagem proposta. Os resultados da revisão da literatura exploratória serviu para caracterizar a diferença entre riscos e incertezas e foram mapeadas as fontes de incertezas. Da revisão sistemática da literatura encontramos 5 formas de gerenciar as incertezas nos projetos e 18 práticas para o gerenciamento de projetos focando na redução das incertezas. Foi realizada uma confirmação das fontes de incertezas mapeadas nos estudos primários e avaliada a relação entre incertezas e projetos inovadores. Na pesquisa-ação pôde-se aplicar técnicas e estratégias em projetos e investigar se essas contribuíram para gestão da incerteza. Nas entrevistas semiestruturadas foi avaliado e adicionado o ponto de vista prático para a abordagem. Finalmente, um grupo focal foi realizado para avaliar a abordagem elaborada. Os resultados desta pesquisa contribuem para a gestão de projetos de software por definir uma abordagem para o gerenciamento de incerteza, bem como descrevendo as estratégias e orientações para os membros da equipe.

Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2017-04-24T14:13:59Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) An Approach to Innovative Software Project Management - Final.pdf: 4765797 bytes, checksum: 1279ab985bdeaf01b2453e5ba5ace612 (MD5) / Made available in DSpace on 2017-04-24T14:13:59Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) An Approach to Innovative Software Project Management - Final.pdf: 4765797 bytes, checksum: 1279ab985bdeaf01b2453e5ba5ace612 (MD5) Previous issue date: 2016-09-05 / CNPQ / Innovation has been recognized as an essential condition for gaining competitive advantage, but also for survival in the software industry. The participation of everyone is essential both in idea generation and innovation implementation. Besides the innovation concern, project-oriented software factories are adopting models like CMMI and MPS.Br to achieve an advantage regarding quality. However, the engagement of everyone is sometimes overlooked, so that innovative ideas (incremental innovations) or opportunities for improvement are not perceived. The aim of this study is to build an approach to manage innovative software project (ISPM), guiding project managers and team members in managing innovation in project-oriented software factories. Thus, this approach can be a determining factor in fostering innovation and avoiding it to be stifled by stimulating engagement and participation. A mixed method was used to analyze the phenomenon of fostering innovation in project-oriented software factories, composed of a systematic literature review (SLR) and an action research (AR) in a real organization. The SRL analyzed 17 primary studies, from an initial set of 2,827 articles, where impact factors in ISPM were identified, resulting in the initial approach. The action research was conducted in a large international organization of software development, with units throughout Brazil. The final model of the ISPM approach confirmed the positive influence of engagement and participation of everyone on idea generation and innovative behavior project-oriented software factories. Demonstrating that it is possible to innovate in this context and keep following the procedures defined for the organization. In particular, the findings showed that the creation of a motivating and open environment for creativity made feasible the innovation development. The study results provided explanatory power to promote innovation, as well as showed the importance to study such phenomena in the software industry, specifically in project-oriented software factories. Moreover, the approach provided several strategies and recommendations for professionals to foster innovation and avoid it to be stifled. / Inovação tem sido reconhecida como uma condição essencial para se ganhar vantagem competitiva e sobreviver na indústria de software. A participação de todos é primordial, tanto na geração de ideias quanto na implementação da inovação. Além da preocupação em inovar, as fábricas de software orientadas a projetos vêm adotando modelos como CMMI e MPS.Br para conseguir um diferencial em termos de qualidade. Porém, o engajamento de todos por vezes é negligenciado, fazendo com que ideias inovadoras (inovações incrementais) ou oportunidades de melhoria não sejam percebidas. O objetivo deste estudo é construir uma abordagem para o gerenciamento de projetos inovadores de software (ISPM), orientando os gerentes de projeto e membros da equipe na gestão da inovação, em fábricas de software orientadas a projetos. Desta forma, esta abordagem pode ser um fator determinante para fomentar a inovação e evitar que ela seja sufocada, ao estimular o engajamento e participação de todos. Um método misto foi utilizado para analisar o fenômeno do fomento à inovação em fábricas de software orientadas a projetos, sendo composto por uma revisão sistemática da literatura (SLR) e uma pesquisa-ação (AR) em organização real. A SRL analisou 17 estudos primários, de um conjunto inicial de 2.827 artigos, onde foram identificados os fatores de impacto para o ISPM, resultando na elaboração de uma abordagem inicial. A pesquisa ação foi realizada em uma grande organização internacional de desenvolvimento de software, com unidades espalhadas pelo Brasil. O modelo final da abordagem para ISPM confirmou a influência positiva do engajamento e da participação de todos na geração de ideias e no comportamento inovador em fábricas de software orientadas a projetos. Demonstrando que é possível inovar neste contexto, sem abdicar de seguir os processos definidos para a organização. Em particular, os achados mostraram que a criação de um ambiente motivador e aberto à criatividade viabilizaram o fomento da inovação. O resultado do estudo proporcionou poder explanatório ao fomento da inovação, assim como mostrou a importância de se estudar o fenômeno na indústria de software, especificamente em fábricas de software orientadas a projetos. Além disso, a abordagem proporcionou diversas estratégias e recomendações aos profissionais da área para fomentar a inovação e evitar que ela seja sufocada.

Conselho Nacional de Desenvolvimento Científico e Tecnológico / The tasks allocation process is a key activity in project management. Being able to conciliate the people profile, as well their professional aspirations is a real challenge for managers. Software projects differ from the rest because of its intangibility and complexity, characteristics that contribute to the failure of these projects. In addition, such projects depend on skilled and highly specialized manpower and the knowledge to motivate and develop them is an extremely important factor for achieving success in this area. Thus, this document sought to present a model of task allocation in software projects that considers, in addition to organizational goals (cost, time, etc.), the professional aspirations of the participating members. The proposed strategy for research is through the simulation of multi-agent systems, systems generally used for behavioral simulation entities. Through this model was intended to provide the manager a tool to aid in decision making in the process of task allocation in software development companies, allowing them to view different scenarios and strategies, looking for producing a better performance in project implementation and greater people satisfaction. / O processo de atribuição de tarefas é uma atividade chave na gerência de projetos. Ser capaz de conciliar o perfil das pessoas, bem como seus anseios profissionais nesse processo é um desafio para gestores. Projetos de software diferem dos demais devido a sua intangibilidade e complexidade, características que contribuem ao fracasso desses projetos. Além disso, tais projetos dependem de mão-de-obra altamente especializada e capacitada e saber motivá-las e desenvolvê-las é um fator de extrema importância para alcançar êxito nessa área. Dessa forma, o presente trabalho buscou apresentar um modelo de alocação de tarefas em projetos de software que considera, além dos objetivos organizacionais (custos, prazos, entre outros), os anseios profissionais dos membros participantes. A estratégia proposta para a investigação é através da simulação de sistemas multiagentes, sistemas geralmente utilizados para simulação de entidades comportamentais. Com esse modelo pretendeu-se prover ao gestor uma ferramenta de auxílio na tomada de decisão no processo de alocação de tarefas em empresas de desenvolvimento de software, permitindo a visualização de diversos cenários e estratégias, gerando dessa forma melhor desempenho na execução de projetos e maior satisfação dos profissionais.

為提升國內軟體專案生產力和品質，建立度量與分析的機制，本研究參考能力成熟度整合模式(Capability Maturity Model Integration, CMMI)之度量與分析流程領域作為指引，結合GQM (Goal-Question-Metric)及PSM (Practical Software & Systems Measurement)的度量方法論，發展一套提問式驅動度量與分析流程規劃法，稱為QMAP (Questions driven- Measurement & Analysis Process Planning)—運用5W1H (Why, Who, When, What, Where & How) 提問方式，有系統地依據CMMI度量與分析流程的要求，找出軟體專案的成功因素，逐步建立組織內部的度量與分析流程的基準。首先，以某公司之個案情境為例進行背景分析、目標分析和流程分析，接著以使用分析—使用案例及其描述之資訊需求，建議整合運用PSM Insight, MS Project及IBM Rational ClearQuest等工具來支援軟體專案度量與分析流程之自動化。經工具系統之實作展示，再以自我評鑑來檢視QMAP於CMMI度量與分析流程之目標及執行方法的符合程度，而部分未達成的項目則作為未來研究之方向。 / This research proposes a method called QMAP (Questions driven- Measurement and Analysis Process Planning) in order to meet goals and practices in Capability Maturity Model Integration (CMMI). QMAP is about 5W1H questions which begin with why, who, when, what, where and how. Before answering the 5W1H questions, we start with background analysis, goal analysis, and process analysis based on a sample company’s management context. Use Cases are then described as the formal information requirements of the MA process support system. In the implementation, we suggest to integrate some tools, such as MS Project, PSM Insight, and IBM Rational ClearQuest, to facilitate the measurement data collection and analysis activities during the software project development. After illustrating the implementation prototype, a checklist for self-appraisal is presented to identify the compliances of CMMI goals and practices, and the incomplete parts for future research extension.

<p>У овом раду приказанa je анализа резултата истраживања,<br />постојећих техничких решења и искустава из IT индустрије у<br />појединачним и комбинованим областима: дистрибуирани<br />развој софтвера и управљање софтверским пројектима у<br />дистрибуираном окружењу, метричка заснованост управљања<br />софтверским пројектима, адатибилност у управљању агилним<br />софтверским пројектима, адаптибилни дистрибуираних<br />информациони системи.<br />Предложен је функционално-технолошки теоријски модел<br />софтверске подршке адаптибилног дистрибуираног<br />информационог система за подршку управљању реализацијом<br />софтверских пројеката. Предложени су приступи у процесу<br />развоја система у оквиру креирања модела софтверских<br />функција и концептуалног модела података. Предложени су<br />метрички модели за евалуацију артефакта у развоју софтвера у<br />области развоја информационих система, као и метрички<br />модели за процену трајања пројекта и мониторинг успеха<br />процеса у дистрибуираном развоју софтвера.<br />Описана је имплементација почетног прототипа система<br />(реализованог као web апликација www.it-project.rs), у оквиру<br />ког су реализоване основне функције система. Извршена су<br />емпиријска истраживања могућности коришћења прототипа<br />система у настави и професионалном усавршавању студената и<br />анализа резултата пробног коришћења прототипа од стране ИТ<br />кадрова уз пратеће анкетирање. Извршена је бенчмаркинг<br />анализа најчешће коришћених расположивих алата издвојених<br />анкетирањем. Извршена је анализа резултата емпиријских<br />истраживања у односу на ефикасност примене прототипа.<br />Извршена је анализа резултата примене метричких модела за<br />евалуацију артефакта развоја софтвера, мониторинг успеха<br />процеса и процену трајања пројекта у делу процеса<br />имплементације софтвера. Реализовано је унапређење<br />прототипа у односу на претходно дефинисане захтеве<br />функционално-технолошког теоријског модела система.</p> / <p>U ovom radu prikazana je analiza rezultata istraživanja,<br />postojećih tehničkih rešenja i iskustava iz IT industrije u<br />pojedinačnim i kombinovanim oblastima: distribuirani<br />razvoj softvera i upravljanje softverskim projektima u<br />distribuiranom okruženju, metrička zasnovanost upravljanja<br />softverskim projektima, adatibilnost u upravljanju agilnim<br />softverskim projektima, adaptibilni distribuiranih<br />informacioni sistemi.<br />Predložen je funkcionalno-tehnološki teorijski model<br />softverske podrške adaptibilnog distribuiranog<br />informacionog sistema za podršku upravljanju realizacijom<br />softverskih projekata. Predloženi su pristupi u procesu<br />razvoja sistema u okviru kreiranja modela softverskih<br />funkcija i konceptualnog modela podataka. Predloženi su<br />metrički modeli za evaluaciju artefakta u razvoju softvera u<br />oblasti razvoja informacionih sistema, kao i metrički<br />modeli za procenu trajanja projekta i monitoring uspeha<br />procesa u distribuiranom razvoju softvera.<br />Opisana je implementacija početnog prototipa sistema<br />(realizovanog kao web aplikacija www.it-project.rs), u okviru<br />kog su realizovane osnovne funkcije sistema. Izvršena su<br />empirijska istraživanja mogućnosti korišćenja prototipa<br />sistema u nastavi i profesionalnom usavršavanju studenata i<br />analiza rezultata probnog korišćenja prototipa od strane IT<br />kadrova uz prateće anketiranje. Izvršena je benčmarking<br />analiza najčešće korišćenih raspoloživih alata izdvojenih<br />anketiranjem. Izvršena je analiza rezultata empirijskih<br />istraživanja u odnosu na efikasnost primene prototipa.<br />Izvršena je analiza rezultata primene metričkih modela za<br />evaluaciju artefakta razvoja softvera, monitoring uspeha<br />procesa i procenu trajanja projekta u delu procesa<br />implementacije softvera. Realizovano je unapređenje<br />prototipa u odnosu na prethodno definisane zahteve<br />funkcionalno-tehnološkog teorijskog modela sistema.</p> / <p>Тhis work presents analysis of research results, existing<br />technical solutions and experiences from IT industry in<br />separate and combined fields of: distributed software<br />development, software project management in distributed<br />environment, metric-based software project management,<br />adaptability in management of agile software projects, as<br />well in the field of adaptable distributed information<br />systems.<br />Functional-technological theoretical model of software<br />support to adaptable distributed information system for<br />software projects realization has been proposed. Approaches<br />to creating software functions model and conceptual data<br />model within the process of the system development were<br />proposed. Metric models for evaluation of artefacts created<br />in software development within information system<br />development, as well as metric models for project duration<br />estimation and monitoring of process success in distributed<br />software development were proposed.<br />Implementation of initial prototype of the system<br />(developed as web application www.it-project.rs), that<br />includes basic functions, was described. Empirical research<br />on possibilities for using prototype in educational<br />environment and professional improvement of students, as<br />well as analysis of results from using the prototype by IT<br />professionals, with additional questionnaire, has been<br />conducted. Benchmarking analysis of most frequently used<br />available tools, extracted from questionnaire results, has<br />been performed. Analysis of empirical research results has<br />been performed in the context of prototype using efficiency.<br />Analysis of results in metric models application in evaluation<br />of software development artefacts, process success<br />monitoring and project duration estimation, in software<br />implementation process part, has been conducted.<br />Improvement of prototype has been implemented according<br />to requirements defined in previously proposed functionaltechnological<br />theoretical model of the system.</p>

Canvases gelten als leichtgewichtiges Werkzeug für die Darstellung komplizierter Sachverhalte. Die Arbeit „Organisierte Software-Startups mit kollaborativen Canvases" beschäftigt sich mit der Konzeption eines Canvas-Frameworks für die Unterstützung von Softwareprojekten. Ein Überblick über die Eigenschaften des Werkzeugs sowie existierende Canvases aus den Bereichen der Geschäftsmodellierung und der Softwareprojektsteuerung bilden die Einführung in das Thema. Im Anschluss werden zwei weitere Canvases für Projektplanung und Kundengespräche eingeführt, deren Eignung im Rahmen einer universitär durchgeführten Studie evaluiert wird. Aus den Feldern der insgesamt drei Canvases für den Kontext der Softwareentwicklung werden in einer Variabilitätsanalyse Kriterien herausgearbeitet, die die Anpassung des Werkzeugs für den individuellen Projektkontext ermöglichen. Den Abschluss bildet die Diskussion möglicher Ansätze zur Vollständigkeitsbewertung ausgefüllter Canvases.

軟體專案承諾升級現象發生時，可能會造成更多資源成本的投入，若投入更多的資源，而專案依然失敗，則會造成更多的浪費，是企業界最不希望看到的情形。本研究利用推敲可能性理論探討此現象，了解不同的說服方式如何影響受測者的決策過程。根據遇到專案的狀況，依照訊息訴求分成理性訴求與感性訴求的敘述方式，加入框架效應 (正向／負向) 以及訊息強度 (低／中／高) 兩變數，以自我責任作為調節變項進行探討，研究在不同情況敘述下，決策制定者接收專案訊息描述後其決策過程中的推敲可能性，以及推敲可能性與決策之間的關係。 研究發現如下： 1. 單一效果影響下，訊息強度中比起其他兩個強度較容易引起訊息接收者運用中央路徑思考。 2. 訊息訴求、訊息框架以及訊息強度會交互影響受測者推敲可能性，在正向框架下，訊息訴求與訊息強度對訊息接收者運用中央路徑做決策有顯著的交互作用。 3. 在訊息強度中與強的情況下訊息訴求與訊息框架對訊息接收者運用中央路徑做決策有顯著的交互作用。 4. 在感性訴求、正向框架與訊息強度強的訊息描述下，訊息接收者運用中央路徑思考時，較不容易做出承諾升級的決定。 5. 在自我責任調節下，則是感性訴求、負向框架與訊息強度弱的訊息描述，會引起訊息接收者運用中央路徑思考時，較不容易做出專案繼續的決策。 / Escalation of commitment is common in software project development. There are a few theories that have been used to explain this behavior, including the framing effect and self-responsibility. This study investigates the issue from the dual-path elaboration likelihood model (ELM) to examine how different persuasion routes may play roles in the decision process. An experiment was designed to study the effect of different descriptions of project status that may lead to different decision routes (central versus peripheral routes). The experiment design includes message appealing (rational vs emotional appealing), message strength (strong, medium and weak), and framing (positive vs. negative) as main variables and the responsibility as a moderator. The subject was asked to decide whether s/he would continue the project under a given scenario. Our results includes the following: 1. Message appealing, message framing, and message strength have significant interaction effect on the subject’s decision routes; 2. In positive framing, message appealing and strength has significant interaction effect on the use of the central route; 3. When message strength is medium or strong, message appealing and framing has significant interaction effect on the use of the central route; 4. Regarding to decision escalation, the likelihood of escalation is lower when the decision route is central (thinking) under the emotional appealing, positive framing, and strong message; 5. The likelihood of escalation is lower when the decision route is central under the emotional appealing, negative framing, and weak message description.

Canvases gelten als leichtgewichtiges Werkzeug für die Darstellung komplizierter Sachverhalte. Die Arbeit „Organisierte Software-Startups mit kollaborativen Canvases" beschäftigt sich mit der Konzeption eines Canvas-Frameworks für die Unterstützung von Softwareprojekten. Ein Überblick über die Eigenschaften des Werkzeugs sowie existierende Canvases aus den Bereichen der Geschäftsmodellierung und der Softwareprojektsteuerung bilden die Einführung in das Thema. Im Anschluss werden zwei weitere Canvases für Projektplanung und Kundengespräche eingeführt, deren Eignung im Rahmen einer universitär durchgeführten Studie evaluiert wird. Aus den Feldern der insgesamt drei Canvases für den Kontext der Softwareentwicklung werden in einer Variabilitätsanalyse Kriterien herausgearbeitet, die die Anpassung des Werkzeugs für den individuellen Projektkontext ermöglichen. Den Abschluss bildet die Diskussion möglicher Ansätze zur Vollständigkeitsbewertung ausgefüllter Canvases.:Abbildungsverzeichnis VII Tabellenverzeichnis IX 1 Einführung 1 1.1 Motivation 1 1.2 Verwandte Literatur 2 1.3 Konzept 3 2 Das Canvas als kollaboratives Werkzeug 5 2.1 Was ist ein Canvas? 5 2.2 Welche Vorzüge bietet die Verwendung eines Canvas als Werkzeug? 6 3 Einsatz von Canvases in Geschäftsmodellentwicklung und Softwareprojektsteuerung 9 3.1 Canvases für die Entwicklung von Geschäftsmodellen 9 3.1.1 BusinessModel Canvas 9 3.1.2 Lean Canvas 11 3.1.3 BusinessModel Canvas for User Experience 13 3.2 Canvases für die Steuerung von Softwareprojekten 14 3.2.1 Lean Software Engineering Canvas 15 4 Erarbeitung von Kundenwünschen mit Canvases 17 4.1 Die Einteilung von Kundenwünschen nach dem Kano-Modell 17 4.2 Das Customer Interview Canvas 19 5 Iterationsplanung im Softwareprojekt mit Canvases 21 5.1 Das Planning Game 21 5.2 Das Iteration Planning Canvas 22 6 Studie zum Einsatz von Canvases in Softwareprojekten 25 6.1 Entwicklung eines Fragebogens 25 6.2 Durchführung der Studie 27 6.3 Auswertung der Studie 28 6.4 Fazit 31 7 Variabilitätsanalyse 33 7.1 Feature-Modelle 33 7.2 Kategorisierung der Canvas-Felder im Zusammenhang mit Softwareprojektsteuerung 36 7.2.1 Felder für eine erste Vorstellung des Produkts 36 7.2.2 Felder für die Projektplanung in Iterationsschritten 39 7.2.3 Felder für separate Kundengespräache 42 7.3 Konfigurationsmöglichkeiten von Canvases im Softwareentwicklungskontext 43 7.4 Konfigurationsbeispiel 45 8 Möglichkeiten zur Bewertung der Vollständigkeit von Canvases 49 8.1 Bewertungsansätze 49 8.2 Diskussion geeigneter Bewertungskriterien 50 9 Schlussbetrachtung 55 9.1 Zusammenfassung 55 9.2 Bewertung und Ausblick 56 Anhang 59 Literaturverzeichnis 71