Sverige har som mål att bli bäst i världen på att nyttja digitaliseringens möjligheter för att skapa effektiv verksamhet i offentlig sektor och en enklare vardag för privatpersoner och företag. År 2017 spenderades 59 miljarder svenska kronor på att digitalisera Sverige med hjälp av externa aktörer. Trots miljardsatsningen är Sveriges utvecklingstakt långsam i jämförelse med flera andra länder i Europa. Svenska myndigheten Riksrevisionen har dessutom identifierat att IT-projekt ofta drar över budget och konstaterar att offentliga verksamheter måste effektivisera sin IT-verksamhet. IT-projekt, inte bara i offentlig sektor, har visat en trend på att dra över budget eller tid och i ett försök att möta denna problematik har den agila filosofin och olika agila projektmodeller vuxit fram. Det agila projektförfarandet har överlag haft en positiv påverkan på IT-projekt och har anammats i en högre utsträckning i den privata sektorn än den offentliga sektorn.  Då det läggs flera miljarder på upphandlingar av IT har vi sett det som viktigt att samverkan med extern part fungerar bra och att projekten effektiviseras. Eftersom den agila projektmodellen visat sig ha en positiv påverkan på IT-projekt har denna studie därför undersökt vilka förutsättningar som finns för att driva IT-projekt agilt mot offentlig sektor. Upphandlingsprocessen och hur den påverkar möjligheten att tillämpa en agil projektmodell har fått särskilt mycket uppmärksamhet i vår studie då lagen om offentlig upphandling (SFS 2016:1145) innebär att den kravspecifikation som skrivs av den upphandlande parten blir svårföränderlig. I vår fallstudie har vi undersökt ett implementationsprojekt i en offentlig verksamhet som drivits med en agil ansats av en extern leverantör i privat sektor. Genom att intervjua respondenter på leverantören, som var involverade i projektet, har vi tillämpat ett leverantörsperspektiv i vår undersökning för att kartlägga upplevda utmaningar i projekt mot offentlig verksamhet. Utifrån empirin har vi kommit fram till att upphandlingsförfarandet lett till att det uppstått (1) utmaningar vid ändring kravspecifikation och att bevisa uppfyllelse av krav, (2) kommunikationssvårigheter mellan Kunden och Leverantören gällande krav och (3) upplevd bristande förståelse för kraven av kunden. Vissa organisatoriska karaktärsdrag för offentlig verksamhet har också identifierats som bidragande till kommunikationssvårigheter mellan Kunden och Leverantören gällande krav. Den agila filosofin förespråkar ett nära samarbete med intressenter och förutsätter förändringar av kravspecifikationen genomgående i projektet. Slutsatsen är således att upphandlingsprocessen, i det studerade projektet, har påverkat möjligheterna för att driva IT-projekt agilt. / Sweden has the goal of becoming best in the world of utilizing the possibilities created by digitalization to create an effective public sector and an easier everyday life for individuals and companies. During 2017, Sweden spent roughly 59 billion Swedish crowns on digitalization with help of external actors. Although these billions of Swedish crowns are spent, the country’s development pace is slower than other European countries. The Swedish authority Riksrevisionen has conducted an audit where they have identified that IT-projects often runs over budget and states that the public sector must streamline its use and procurement of IT. IT-projects have shown a trend of budget overruns and not meeting deadlines, not only in the public sector. In an attempt to turn the trend, the agile philosophy and different agile project models was formed. The agile approach has overall had a positive effect on IT-project and has been embraced in the private sector to a larger degree than the public sector. We see cooperation between external supplier and the actor procuring information systems as well as the streamlining of IT-projects as a critical aspect of the Swedish digitalization. Since the agile approach has shown positive effects of IT-projects, this study has aimed to examine what prerequisites are present in the public sector for running projects in accordance of the agile philosophy. The procurement process and how it affects these prerequisites has received a lot of focus since the procurement law (SFS: 2016:1145) in Sweden implicates that the requirement specification, created by the contracting actor, is difficult to change. In our case study, we have examined an implementation project in the public sector, led by an information system supplier in the private sector. We gathered qualitative data by interviewing employees of the supplier, involved in the project, effectively applying a supplier perspective to map perceived challenges in delivering information systems to the public sector. From the qualitative data we concluded that the procurement process has led to (1) difficulties with changing the requirement specification and proving fulfilment of requirements, (2) communication challenges between the customer and the supplier regarding requirements and (3) experienced lack of comprehension of requirements by the customer. Some organizational characteristics for the public sector have also been identified as a possible cause of communication challenges. The agile philosophy advocates close collaboration with stakeholders and expects changes to the requirement specification throughout the project. The conclusion is thus that the procurement process, in the studied project, has affected the prerequisites to run a project with an agile approach in a negative way.

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 software / The 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

Choosing the Software Development Methodology is the very first step of any project; thus,has been a hot topic among, both, practitioners and academic people. After using plandrivensoftware development methodologies software development researchers came up withthe idea of agile software development methodologies as a masterpiece. Although, failurestories of some teams brought about fading the idea that agile methodologies are thebest recipe for any kind of development project. Considering the lack of studies in helpingpractitioners to select the most appropriate agile software methodology, this study aims atprovide the software development manager with a thorough knowledge of agile methodologiesand the criteria that should be considered, while selecting one of them. A case study is used asan empirical support. / Program: Magisterutbildning i informatik

Greitas internetinių svetainių skaičiaus padidėjimas per paskutinius keletą metų rodo informacijos, pasiekiamos internetu, svarbą. Daug įmonių kuria internetines svetaines, bet jie susiduria su problemomis, susijusiomis su reikalavimų pasikeitimais kūrimo eigoje. Šiame darbe nagrinėjama Agile požiūrio pritaikymo galimybės internetinėms svetainėms kurti. Darbe atlikta jau esamų metodų analizė, kuri parodė, kad internetinių svetainių kūrimui nėra visiškai tinkamo metodo, todėl darbo uždavinys - sukurti metodą, paremtą Scrum ir FDD savybėmis internetinių svetainių kūrimui. / A fast increase in the number of web sites the last years, shows the importance of information existing in web sites giving the possibility for users to have access to it. Many companies create websites, but they face problems related with requirements changing until the developing process completes. In this work you will find analysis of software development methods. Agile approach allows changing requirements even in last phase of the developing process. Creating a web site does not follow one single path and there is no ideal method creating a web site. In this dissertation will be analyzed a method for web sites development based on Agile approach.

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

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 software / The 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

Made available in DSpace on 2016-03-15T19:37:56Z (GMT). No. of bitstreams: 1 KHAOHUN SHIA.pdf: 2242262 bytes, checksum: 97a46586e1ac55fd1097f77a932ad878 (MD5) Previous issue date: 2015-08-25 / In a competitive market of software, companies seek an agile development process with quality. Faced with this challenge, the companies target is a certification to prove the ability to produce a high quality product by following a defined process, for example, Capability Maturity Model Integration for Development (CMMI-DEV). To achieve this goal, the company hires experts to change the existing process, which represents a high cost for small and medium-sized businesses. The assumption in this work is to evaluate the possibility of using an agile methodology which adheres to CMMI-DEV. Feature Driven Development (FDD) was the agile methodology selected to assess their adherence to Project Planning area of CMMI-DEV. The evaluation of specific practices was automated by the multi-agent system with two ontologies. The first of them is the Ontology CMMI/FDD, which defines the concepts and the relationship of FDD with these specific practices. The second is the Ontology of Project Planning Document that defines the concepts used in sections of the Project Planning documents. The mapping between the specific practices and implementation was performed by intelligent mapping agents. The results obtained shown that it is possible to automate the process of evaluation of specific practices by the evidences in sections of the documents, reducing the costs involved in hiring a specialist of CMMI. The evaluation of Intelligent Agents of Specific Practices shown that the FDD partially attends to the specific practices, being necessary to change the two documents elaborated from the FDD Document (Project Plan and List of Functionality) and add three auxiliary documents (Risk Management, Data Management and Training Management) to meet all the specific practices of the Project Planning Area of the CMMI-DEV. / Em um mercado competitivo de desenvolvimento de software, as empresas buscam um processo ágil com qualidade. Diante desse desafio, procuram uma certificação para comprovar a capacidade de produzir com qualidade, seguindo um processo definido, por exemplo, o Capability Maturity Model Integration for Development (CMMI-DEV). Para atingir essa meta, a empresa contrata especialistas para alterar o processo existente, o que representa um alto custo para empresas de pequeno e médio porte. A hipótese neste trabalho é avaliar a possibilidade de utilizar uma metodologia ágil aderente ao CMMI-DEV. O Desenvolvimento Guiado por Funcionalidades (FDD) é a metodologia ágil selecionada para computar a sua aderência em relação à área de Planejamento de Projetos do CMMI-DEV. A avaliação das práticas específicas foi automatizada por um sistema multiagentes com duas ontologias. A primeira delas é a ontologia CMMI/FDD, que define os conceitos e a relação do FDD com essas práticas específicas. A segunda é a ontologia dos Documentos do Planejamento de Projeto, que define os conceitos utilizados nas seções dos documentos do Planejamento de Projeto. O mapeamento entre a prática específica e a implementação nas seções de documentação foi realizado pelos Agentes Inteligentes de Mapeamento. Os resultados obtidos mostram que é possível automatizar o processo de avaliação das práticas específicas, mostrando as evidências nas seções dos documentos, reduzindo os custos envolvidos na contratação de um especialista em CMMI. A avaliação dos Agentes Inteligentes de Práticas Específicas mostra que o FDD atende parcialmente às práticas específicas, sendo necessário alterar os dois documentos elaborados a partir do documento do FDD (Plano de Projeto e Lista de Funcionalidade) e adicionar três documentos auxiliares (Gestão de Risco, Gestão de Dados e Gestão de Treinamento) para satisfazer a todas as práticas específicas da área de Planejamento de Projeto.

Computer science in general and software engineering in specific is changing very fast. Software engineers are constantly using more innovative and more efficient ways to develop new software than in the past. This continuous evolution of software development methodologies has a great impact on both the software developed and the environment that the developers work-in. Agile software development methodologies are used to overcome many issues in the software development processes. One of the issues which still exists and needs to be addressed is the preparation of proper documentation along with the software. The work presented in this dissertation focuses on software documentation. The work starts by a thorough literature review which focuses on different aspects of software documentation and different agile methodologies. The thesis focuses on finding out the challenges that the developers faces during their development process. Two major questions addressed in the thesis. First one is to find the motivation to document in agile envirionment, whih is based on the hypothesis that there do exist a motivation. The second question is that how should documentation be produced such that we could avoid maximum possible potential problems. These questions are addressed with the help of different perspectives of the stockholders (i.e. developers and users) and the existing methods for documentation. A questionnaire was developed based on the nine categories of documentation, like user documents and system documents etc.. It included different questions related to the types of documents created in software development processes, the software development stage at which the documents are created and the importance of the documents. Questions from this questionnaire are then posted on agile specific discussion forums. Where many experienced and fresh practitioners participated in the discussion. We had a detailed discussion on every component of documentation and problems were identified by the practitioners. The questionnaire was also sent to different companies practicing agile methodology. we received about 14 responses as it was detailed questionnaire with about 34 questions. The responses of the discussion forum and survey are then analyzed and conclusions were drawn. The conclusions include that all the participants consider software documentation very important to the success of a software development project. the question of motivation is answered from the literature and opinions we received from experienced practitioners. While seven factor are identified that affect your documentation, to help solve the question of how should documentation be done.

These days there are a lot of methodologies which can be used for IS/ICT implementation projects. Apart from traditional rigorous methodologies such as Rational Unified Process (RUP), there are also agile methodologies, which are characterized by positive approach to change and iterative development with very short iterations. One of these methodologies is OpenUP, which combines both agile and rigorous principles. OpenUP covers the most important factors necessary to focus on during software development, but on the other hand it also respects the fact that each project is unique. That is why it offers the possibility to extend or customize its content for specific requirements. The main objective of this diploma is to localize and customize OpenUP methodology for the projects which are running within the courses of software engineering at the University of Economics in Prague. The result if this customization and localization is a methodology suitable for small software projects called MMSP. This diploma also pursues other objectives like to find and characterize tools suitable for administration and customization of the methodology. These objectives were achieved by deep analysis of various sources about OpenUP methodology, information system development projects and methodologies of IS/ICT development. The resulting methodology was not only based on these information but it also results from experiences and best practices from the projects at the University of Economics in Prague and from consultations with experts in practice. The key benefit of this diploma is a complete Czech localized methodology MMSP which can be used both for school and real projects of IS/ICT development. MMSP is available in a form that can be easily embraced, further customized and administrated.

The main aim of this piece of work is to propose an adjustment to the ICE methodology with an increased applicability for small projects. The emphasis is especially given to the most important areas of the methodology that can be easily adjusted or simplified. The theoretical part of this paper consists of four main chapters. The first chapter is called "Project and Project Management". This chapter holistically explains the meaning of project and project management terms. It describes a project from a general point of view and looks at its individual components. The second chapter so called "Methodology" explores particular project management methodologies. It focuses on two basic project lifecycle models along with an analysis of traditional and agile methodologies. The third "Small Project Methodologies" chapter examines the modified methodologies suitable for management of small projects. The final chapter of the theoretical part is the "ICE Methodology Analysis". The analysis represents the key pillar for this work without which the practical part could not be concluded. The practical part of this piece of work focuses on specifics of the ICE methodology modification in accordance with the analysis carried out in the theoretical part. The basis for this modification is represented by the general methodology framework for small projects. The general framework is fully based on the analysis undertaken in the theoretical part of this paper and plays a significant role in the ICE methodology modification process. The main areas of the ICE methodology modification are defined in "The ICE Methodology for Small Projects - Simplification Proposal". The practical part's conclusion presents the unmodified and modified ICE methodology comparison.