Browsing by Subject "agile software development"

Sort by: Order: Results:

Now showing items 1-3 of 3
  • Yaman, Sezin; Mikkonen, Tommi; Suomela, Riku (IEEE, 2018)
    EUROMICRO Conference Proceedings
    Software companies need capabilities to evaluate the user value and the success of their products. This is especially crucial for highly competitive markets, such as the mobile game industry, where thousands of new games are introduced every month. Game companies often run continuous experiments as an integrated part of the overall development process. This paper presents a game company’s journey on experimentation, and describes how the experiments are used at different stages of the development cycle to produce reliable, meaningful data for developers as well as how to balance between different data collection methods. Our study indicates that experiments are important in all stages of the development in different forms. Early stages in the development experiments can be run with proxy users due to lack of real users, whereas later in the development Key Performance Indicator (KPI) metrics play the most important role in experiments. Establishing concrete goals for the experiments, balancing between qualitative and quantitative data collection, experimentation throughout the development process with the guidance of an efficient leadership appears to be the key to success.
  • Maaranniitty, Saija (Helsingin yliopisto, 2020)
    Agile software development promotes self-organizing teams, close collaboration with client and team members, short iterative development cycles, response to changing requirements and continuous feedback. Originally agile methods were developed for small teams. As large organisations had a need for agile software development methods supporting several teams and collaboration between them, scaled agile development methods were developed. They promise increased productivity and quality, higher customer engagement and alignment between all levels of the enterprise. This thesis focuses on the software developers perceptions on team performance in Scaled Agile environment. More specifically this thesis studies how team performance is perceived to be impacted in organization that has adopted Scaled Agile Framework (SAFE). The study was designed to acquire descriptive knowledge through empirical studies. This thesis is based on an investigation of a single case company based in Finland. The data for analysis was collected from semi-structured interviews with 5 experienced developers. The findings show that several factors impact software developers team performance experience. By investigating the point of view of practitioners, we observed that team performance is a concept that evolves over time and is prone to be influenced by surrounding environment. This understanding can be used to adjust software development method related practices and organizational factors. This study provides pieces of advice on what kind of practices support or hamper team performance and how to improve them.
  • Fagerholm, Fabian; Sanchez Guinea, Alejandro; Mäenpää, Hanna; Münch, Jürgen (2017)
    Context:Development of software-intensive products and services increasingly occurs by continuously deploying product or service increments, such as new features and enhancements, to customers. Product and service developers must continuously find out what customers want by direct customer feedback and usage behaviour observation. Objective: This paper examines the preconditions for setting up an experimentation system for continuous customer experiments. It describes the RIGHT Model for Continuous Experimentation (Rapid Iterative value creation Gained through High-frequency Testing), illustrating the building blocks required for such a system. Method: An initial model for continuous experimentation is analytically derived from prior work. The model is matched against empirical case study findings from two startup companies and further developed. Results: Building blocks for a continuous experimentation system and infrastructure are presented. Conclusions: A suitable experimentation system requires at least the ability to release minimum viable products or features with suitable instrumentation, design and manage experiment plans, link experiment results with a product roadmap, and manage a flexible business strategy. The main challenges are proper, rapid design of experiments, advanced instrumentation of software to collect, analyse, and store relevant data, and the integration of experiment results in both the product development cycle and the software development process.