This is a report concerning the software development project Eldflugan, a system developed by eight students at Linköping University. It addresses experience from developing a web-based e-commerce using Scrum, an agile development method, which was used throughout the project. The teams work, how Scrum was applied with both advantages and disadvantages is being lifted. Different development environments have been used due to separate issues and opportunities, which is described. The database management systems, MySQL, and the local version, SQLite, are discussed as well as AJAX and PJAX, tools for giving the users a better and faster experience. To prepare Eldflugan for entering the e-commerce market, a marketing plan including environmental scanning, a SWOT analysis and a STP, has been made. Ethical aspects such as legal, use and handling of personal information and how it is communicated are also being addressed. Finally the report discusses product weaknesses, future opportunities, implementation difficulties and how those could have been prevented. It was found that Scrum is best used when it is utilized fully and a risk analysis can prevent unexpected problems to surface.

This master thesis deals with problems of information technology projects and their solutions using agile project management. Based on an analysis of the company and its projects is suggested solution using agile methods.

For a long time there has been issues about time estimation in IT-projects. Despite the fact that we went from the traditional waterfall model to the agile methods, the challenges of time estimation has continued. The agile methods do not solve the problems. A technique that agile teams have chosen to apply in order to solve this problem is planning poker. The technique is based on a method that includes a number of steps for implementation. This study is conducted to investigate whether methods such as planning poker for time estimation provide agile team support to make safer time estimates in agile IT-projects. The study also investigates how the process of planning poker is applied in practice. The study is based on interviews and a literature study that has compiled in a result that has been analysed. The result shows that agile teams choose to modify the prescribed method of planning poker to streamline the process as they find that some steps in the prescribed method are unnecessary. This result differences from earlier research where praxis is that you follow all steps of the prescribed method. Further a number of challenges that comes at an adaptation of the technique are identified. The result also shows that planning poker creates better discussion and understanding of matters for the agile team.

This master thesis focuses on the agile methods description and their use in creating of company strategic material. The main part of this thesis consist of the SCRUM and Kanban method. The work contribution is an optimization of the document creation process. The solution proposed is implemented through the MS SharePoint server with mind mapping module and Kanban board module. Thanks to this solution, company project can be managed in a more effective, faster and higher quality way.

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.

The theme of this thesis is how to implement an existing software development methodology in small company. The main aim of the thesis is to choose and adapt one of existing methodology and implement it in the real enterprise environment, therefore the first step is analyze existing (current) state in this environment and consequently propose the best way of implementing and establishing the chosen methodology. The first chapter of the thesis deals with theoretical background devoted to history of software development methodologies and explains the meaning of software development and describes its goals and parts. Existing trends in the area of software development methodologies are also described in this chapter. The next part of the thesis is focused on most widely used methodologies and approaches in this area. Some of possible methodologies for small companies are described and presented with the view of making process of selection easier. Next logical step of this work is analyzing the current state of development process of client and choosing appropriate methodology for implementation. The last chapter deals with project of implementation that consists of several steps divided into three main phases. The aim of the first phase of the project is to propose solution to establishing new methodology. It is followed by the phase implementing this solution in real enterprise environment. The project of implementation concludes with verification of results through real pilot project.

No description available.

The main objective of this work is to propose a software development methodology which will reflect both issues -- design of User Experience (UX) and its implementation. The second objective is to compare the current software development methodologies. The third objective is to describe the work environment and the principles of that environment to fully implement this methodology. The fourth objective is to test the methodology in practice and validate its performance on my own startup. The fifth objective is to analyze companies which are focusing on similar product as my startup and their approach to UX development. First I will take look at waterfall methodology and then at modern agile methodologies such as Scrum, Kanban and Lean management, which are now becoming standard in software development. I will describe issues with the integration of UX into software development. The next section will introduce my own methodology, which is based on Scrum. The methodology consists of general principles of Lean and Agile management and the management, which is sometimes called "freedom at work". Then I will use the proposed methodology on my own startup project and will evaluate its use in practice. In last part I will analyze development process with focus on UX in projects Medium and Facebook. Thesis combines knowledge from Lean and agile management, economy and cognitive science to show the way to succeed in today services with great UX.

This thesis deals with the issue of project management in the development of custom software, particularly PRINCE2 methodology and agile approaches to software development. The work is divided into two parts. The first part is theoretical. It describes the basic concepts of project management, project history and characterizes the selected software development methodologies. The classical methods are represented by waterfall and spiral models. In the context of the agile methods are described Scrum, Extreme Programming, Kanban and Scrumban. Regarding the standards of project management this thesis describes in detail the methodology PRINCE2 which at the end of the theoretical part will be compared to the standards of PMI and IPMA. The second part is practical and describes an adaptation of PRINCE2 for small projects and helps to decide which tools of PRINCE2 are required for small projects use and which ones can be ignored. In this thesis the process of managing product delivery within the PRINCE2 methodology is replaced by the agile methodology Scrumban that is adapted for a software development within analyzed organization. The thesis focuses on a more detailed description of the methodology Scrumban, established metrics and motivation within the development team.

The aim of the study is to compare traditional and agile approaches to project management, analyze particular projects in selected company and propose recommendations for t for implementing agile and traditional approaches. Thesis is focused on IT project management, specifically in in the field of developing software products and services. The theoretical part is devoted to project management and the characteristics of the basic concepts. Furthermore it deals with the traditional methods and agile approach to project management and differences between them. Theoretical knowledge is then applied in the practical part in a corporate environment. Major differences between traditional waterfall and agile approach are compared using the examples of real projects. In conclusion, there are basic problems in implementation of agile methods in corporations and recommendations for their implementation.