University of Oulu

Building lean development pipeline : case Espoo verkkoneuvontapalvelu

Saved in:
Author: Puttonen, Jyrki1
Organizations: 1University of Oulu, Faculty of Information Technology and Electrical Engineering, Department of Information Processing Science, Information Processing Science
Format: ebook
Version: published version
Access: open
Online Access: PDF Full Text (PDF, 0.4 MB)
Persistent link: http://urn.fi/URN:NBN:fi:oulu-201504251424
Language: English
Published: Oulu : J. Puttonen, 2015
Publish Date: 2015-04-27
Physical Description: 47 p.
Thesis type: Master's thesis
Tutor: Tervonen, Ilkka
Reviewer: Tervonen, Ilkka
Mäntylä, Mika
Description:
Lean software development has become more and more popular. It is especially suited for development of Software as a Service -applications (SaaS). One reason for this is the way the SaaS -applications are released; they are usually released in fast cadence of iterations, in some cases even multiple times a day. This requires a new approach to the tools and methods used in software development. The objective of this thesis is to find out what requirements there are for development tools in context of small software development company. The lean software development has its roots in lean manufacturing. Many of the methods used in lean software development are somewhat similar to the methods of lean manufacturing. So it is relevant to know out what kind of methods and processes are used in lean manufacturing, and learn about their experiences, as it has been around from 1940s. Two high level requirements for development tools were derived from the methods and processes found in lean manufacturing and lean software development: - Every change must be reviewed and tested - Installation and update process must be automated Two different tools were then selected for implementation. These tools were then used as a part of for a new development process, which was focused for short lead time of new features using lean software development methodologies. This process was found out to be useful in internal acceptance, but there were problems in acceptance testing by the customer as the pace of changes were too fast.
see all

Subjects:
Copyright information: © Jyrki Puttonen, 2015. This publication is copyrighted. You may download, display and print it for your own personal use. Commercial use is prohibited.