Kristian Rautiainen
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Kristian Rautiainen has a total of 25 co-authors. Here are the top co-authors by number of shared publications:
C. Lassenius
Helsinki Univ. of Technol., Espoo, Finland
3 shared publicationsJ. Vahaniitty
Software Bus. & Eng. Inst., Helsinki Univ. of Technol., Espoo, Finland
3 shared publicationsCasper Lassenius
2 shared publicationsJarno Vähäniitty
2 shared publicationsM. Nissinen
Helsinki Univ. of Technol., Espoo, Finland
2 shared publications- Ville T. Heikkila
Aalto University, Finland
2 shared publications
Latest Publications
- 1 January 2011
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 15301605,p. 1-10
Supporting Scaling Agile with Portfolio Management: Case Paf.com
This paper is a descriptive case study of how one department at Paf, Paf.com, introduced portfolio management to help support scaling agile software development. Paf.com had experienced problems with long time-to-market due to thrashing, which was caused by frequently changing priorities due to an ad-hoc prioritization process and handovers. Also, there was lack of visibility into projects entering and progressing in the development pipeline. No structured way of starting projects was enforced company-wide, and too many parallel projects got started. As a result of introducing a structured portfolio management process, the number of ongoing projects has dramatically reduced, from over 200 to 30, reducing thrashing. Listing all projects in priority order in the Paf.com backlog provides visibility into what is currently ongoing, helping coordinate the work of multiple Scrum teams. The portfolio follow-up function provides progress data on the projects, helping managers make more informed decisions, considering the whole portfolio.
- 1 January 2011
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 15301605,p. 1-10
Supporting Scaling Agile with Portfolio Management: Case Paf.com
This paper is a descriptive case study of how one department at Paf, Paf.com, introduced portfolio management to help support scaling agile software development. Paf.com had experienced problems with long time-to-market due to thrashing, which was caused by frequently changing priorities due to an ad-hoc prioritization process and handovers. Also, there was lack of visibility into projects entering and progressing in the development pipeline. No structured way of starting projects was enforced company-wide, and too many parallel projects got started. As a result of introducing a structured portfolio management process, the number of ongoing projects has dramatically reduced, from over 200 to 30, reducing thrashing. Listing all projects in priority order in the Paf.com backlog provides visibility into what is currently ongoing, helping coordinate the work of multiple Scrum teams. The portfolio follow-up function provides progress data on the projects, helping managers make more informed decisions, considering the whole portfolio.
- 1 September 2010
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 289-296
A Revelatory Case Study on Scaling Agile Release Planning
A way to scale up agile release planning to meet the requirements of multi-team agile development is a practice called joint release planning. A software product company piloted the joint release planning method. The aim of the company was to improve coordination of work of multiple agile development teams who develop a large legacy software product. Another aim was to improve communication between product management and development. We conducted a case study to explore how the new release planning method was executed. We gathered data by observing two release planning events, observing event planning meetings, and by conducting surveys. The events were attended by approximately 140 stakeholders, including over 10 development teams, who spent several days in a common space. The participants liked the method and considered it efficient. This revelatory case study provides the first detailed empirical description of this emerging method for multi-team agile release planning.
- 1 September 2010
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 289-296
A Revelatory Case Study on Scaling Agile Release Planning
A way to scale up agile release planning to meet the requirements of multi-team agile development is a practice called joint release planning. A software product company piloted the joint release planning method. The aim of the company was to improve coordination of work of multiple agile development teams who develop a large legacy software product. Another aim was to improve communication between product management and development. We conducted a case study to explore how the new release planning method was executed. We gathered data by observing two release planning events, observing event planning meetings, and by conducting surveys. The events were attended by approximately 140 stakeholders, including over 10 development teams, who spent several days in a common space. The participants liked the method and considered it efficient. This revelatory case study provides the first detailed empirical description of this emerging method for multi-team agile release planning.
- 1 March 2010
- Published by IBM in IBM Journal of Research and Development
- Vol. 54 (2) , 1:1-1:12
Small software organizations need explicit project portfolio management
- 1 March 2010
- Published by IBM in IBM Journal of Research and Development
- Vol. 54 (2) , 1:1-1:12
Small software organizations need explicit project portfolio management
- 1 January 2010
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 15301605,p. 1-10
Rigorous Support for Flexible Planning of Product Releases - A Stakeholder-Centric Approach and Its Initial Evaluation
This paper addresses the problem of product release planning in iterative product development. We propose a method which combines decision, process, and tool support. The method, which is called SCERP, facilitates the active involvement of stakeholders in the different stages of the planning process. SCERP is flexible in the number of stakeholders involved, in the number of releases, in the number and definition of planning criteria, and in the selection of the best plan out of a set of optimized alternatives. A proof-of-concept of the method is given by a case study of release planning for a tool called Agilefant, which is developed with a process partially based on Scrum. The benefits of the method as demonstrated by the case study are: (i) better decisions by the product manager by relying on more objective information, (ii) more transparency of release decisions, and (iii) efficient tool support accompanying the whole process.
- 1 January 2010
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 15301605,p. 1-10
Rigorous Support for Flexible Planning of Product Releases - A Stakeholder-Centric Approach and Its Initial Evaluation
This paper addresses the problem of product release planning in iterative product development. We propose a method which combines decision, process, and tool support. The method, which is called SCERP, facilitates the active involvement of stakeholders in the different stages of the planning process. SCERP is flexible in the number of stakeholders involved, in the number of releases, in the number and definition of planning criteria, and in the selection of the best plan out of a set of optimized alternatives. A proof-of-concept of the method is given by a case study of release planning for a tool called Agilefant, which is developed with a process partially based on Scrum. The benefits of the method as demonstrated by the case study are: (i) better decisions by the product manager by relying on more objective information, (ii) more transparency of release decisions, and (iii) efficient tool support accompanying the whole process.
- 1 May 2009
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 36-39
Software development governance challenges of a middle-sized company in agile transition
We studied how a middle-sized Finnish company employing agile methods governs its software product development. Through observations and interviews we followed the trace from strategic plans in the form of roadmaps to various backlogs and all the way to daily work. The governance roles, responsibilities and deliverables seemed to be in place on different organizational levels. However, closer inspection revealed challenges in the practical implementation. There were too many roles and hierarchy levels with information consistency problems in between. Prioritization of the high-level goals was unclear and made it difficult to plan and organize development work based on business value. The trace from high-level goals to more detailed plans was easily corrupted due to poor planning practices. Progress monitoring of daily work was poorly done and not linked to high-level plans. Consequently, the required feedback loops were inadequate, making it impossible for management to take corrective actions in time.
- 1 May 2009
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 36-39
Software development governance challenges of a middle-sized company in agile transition
We studied how a middle-sized Finnish company employing agile methods governs its software product development. Through observations and interviews we followed the trace from strategic plans in the form of roadmaps to various backlogs and all the way to daily work. The governance roles, responsibilities and deliverables seemed to be in place on different organizational levels. However, closer inspection revealed challenges in the practical implementation. There were too many roles and hierarchy levels with information consistency problems in between. Prioritization of the high-level goals was unclear and made it difficult to plan and organize development work based on business value. The trace from high-level goals to more detailed plans was easily corrupted due to poor planning practices. Progress monitoring of daily work was poorly done and not linked to high-level plans. Consequently, the required feedback loops were inadequate, making it impossible for management to take corrective actions in time.
- 1 January 2009
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 300-305
Long-Term Planning of Development Efforts by Roadmapping – A Model and Experiences from Small Software Companies
Success in the software product business requires timely release of new products and upgrades with proper quality and the right features. For this, a systematic approach for managing the contents, timing and roles of future product releases as well as the product architecture is needed. In practice, such an approach is often missing, especially in small companies, due to inexperience, unclear priorities, time-to-market pressures, or the lack of suitable process infra-structure. In this paper, we present a model to visualize product roadmaps developed together with three small software companies and experiences from its use. The model depicts release and development schedules, the composition of individual releases, services that require attention from the developers, changes to the underlying technology and the planned resource usage. We also present lessons learned from the case companies and outline directions for future research.
- 1 January 2009
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 300-305
Long-Term Planning of Development Efforts by Roadmapping – A Model and Experiences from Small Software Companies
Success in the software product business requires timely release of new products and upgrades with proper quality and the right features. For this, a systematic approach for managing the contents, timing and roles of future product releases as well as the product architecture is needed. In practice, such an approach is often missing, especially in small companies, due to inexperience, unclear priorities, time-to-market pressures, or the lack of suitable process infra-structure. In this paper, we present a model to visualize product roadmaps developed together with three small software companies and experiences from its use. The model depicts release and development schedules, the composition of individual releases, services that require attention from the developers, changes to the underlying technology and the planned resource usage. We also present lessons learned from the case companies and outline directions for future research.
- Open Access
- 12 May 2008
- Published by Association for Computing Machinery (ACM)
- p. 25-28
Towards a conceptual framework and tool support for linking long-term product and business planning with agile software development
- 12 May 2008
- Published by Association for Computing Machinery (ACM)
- p. 25-28
Open AccessTowards a conceptual framework and tool support for linking long-term product and business planning with agile software development
- Open Access
- 12 May 2008
- Published by Association for Computing Machinery (ACM)
- p. 17-20
Integrating product family modeling with development management in agile methods
- 12 May 2008
- Published by Association for Computing Machinery (ACM)
- p. 17-20
Open AccessIntegrating product family modeling with development management in agile methods
- 10 December 2005
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 82-91
Exploratory testing: a multiple case study
Exploratory testing (ET) - simultaneous learning, test design, and test execution - is an applied practice in industry but lacks research. We present the current knowledge of ET based on existing literature and interviews with seven practitioners in three companies. Our interview data shows that the main reasons for using ET in the companies were the difficulties in designing test cases for complicated functionality and the need for testing from the end user's viewpoint. The perceived benefits of ET include the versatility of testing and the ability to quickly form an overall picture of system quality. We found some support for the claimed high defect detection efficiency of ET. The biggest shortcoming of ET was managing test coverage. Further quantitative research on the efficiency and effectiveness of ET is needed. To help focus ET efforts and help control test coverage, we must study planning, controlling and tracking ET.
- 10 December 2005
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 82-91
Exploratory testing: a multiple case study
Exploratory testing (ET) - simultaneous learning, test design, and test execution - is an applied practice in industry but lacks research. We present the current knowledge of ET based on existing literature and interviews with seven practitioners in three companies. Our interview data shows that the main reasons for using ET in the companies were the difficulties in designing test cases for complicated functionality and the need for testing from the end user's viewpoint. The perceived benefits of ET include the versatility of testing and the ability to quickly form an overall picture of system quality. We found some support for the claimed high defect detection efficiency of ET. The biggest shortcoming of ET was managing test coverage. Further quantitative research on the efficiency and effectiveness of ET is needed. To help focus ET efforts and help control test coverage, we must study planning, controlling and tracking ET.
- 25 August 2005
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- Vol. 1, 9 pp.-7053
Improving multi-project management in two product development organizations
We describe how two product development organizations have started improving their multi-project management. A typical problem in new product development (NPD) organizations is that too many projects are launched. NPD projects can range from advanced research to enhancements to existing product lines. Each type of project should have its own role and add its own contribution to the strategic mission and competitiveness of the company. The product strategy of a company should serve as the guideline for planning the right sequence, number, and mix of projects. Together with the product strategy, portfolio management should provide the basis for fund allocation and prioritization between the different types of projects. With a project classification system, the various needs of the different project types can be considered.
- 25 August 2005
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- Vol. 1, 9 pp.-7053
Improving multi-project management in two product development organizations
We describe how two product development organizations have started improving their multi-project management. A typical problem in new product development (NPD) organizations is that too many projects are launched. NPD projects can range from advanced research to enhancements to existing product lines. Each type of project should have its own role and add its own contribution to the strategic mission and competitiveness of the company. The product strategy of a company should serve as the guideline for planning the right sequence, number, and mix of projects. Together with the product strategy, portfolio management should provide the basis for fund allocation and prioritization between the different types of projects. With a project classification system, the various needs of the different project types can be considered.