Product Development Management. Experiment for New Type of Project Management.

Tuotekehityksestä ja sen johtamisesta on tullut erittäin tärkeä osa tietoliikenneteollisuutta. Jatkuva teknologinen kehitys ja lyhentyneet tuotteiden elinkaaret ovat saaneet yritykset panostamaan tuotekehitysprosesseihin ja johtamiseen. Erityisesti nopeatempoiset ja lyhytkestoiset projektit onkin koettu ongelmallisiksi. Diplomityön tavoitteena oli tutkia teoriassa uusien tuotteiden tuotekehitystä, tuotekehitysprosesseja sekä projektijohtamista. Käytännön osuudessa oli tavoitteena kehittää kokeellinen tuotekehitysmalli nopeatempoisten ja lyhytkestoisten tuotekehitysprojektien tarpeisiin muuttuvissa ja epävarmoissa olosuhteissa. Tavoitteena oli myös käyttää ja analysoida kehitettyä kokeellista tuotekehitysmallia lyhytkestoisen tuotekehitysprojektin yhteydessä. Työn tuloksena saatiin ohjelmistotuote vaadituilla ominaisuuksilla vaaditussa ajassa ja todettiin projektissa käytetyn kokeellisen tuotekehitysmallin osoittautuneen toimivaksi. Jatkotutkimuksia tarvitaan selvittämään mallin sopivuutta ja sen kehityskohteita erilaisten tuotekehitysprojektien kohdalla.

Enhancement of R&D project management system

Stora Enso has research centres in Finland, Sweden and Germany. The research centres use PIMS as a research project invoicing and monitoring system. Possible reorganization and new financing model for R&D functions have been considered and the project management system should be developed to support the new operation model. The objective of this thesis is to find a model for R&D project management, and to present the project management system of Stora Enso, and to discuss if the current system could be developed to respond to the new needs or should it be replaced with another system. The theoretical part of the study describes challenges in R&D project management, and presents different project characteristics, and methods for managing R&D project portfolio. It is also described how the project management system can support project monitoring and controlling, and how inter-project learning can be enhanced. The empirical part of the study presents the current project management system of Stora Enso and how the system should be developed to support Stora Enso’s R&D functions better. In conclusion, it is stated that there is no relevant reason to replace PIMS with another system, because PIMS can be developed to support R&D project management better with a hybrid system. It is also suggested that the new financing model should not be implemented before more comprehensive analysis of its effects is conducted.

De-escalation of commitment management strategy in IT project management methodology: case of ERP implementation project by IT consulting company

According to several surveys and observations, the percentage of successfully conducted IT projects without over-budgeting and delays in time schedule are extremely low. Many projects also are evaluated as failures in terms of delivered functionality. Nuldén (1996) compares IT projects with bad movies; after watching for 2 hours, one still tries to finish it even though one understands that it is a complete waste of time. The argument for that is 'I've already invested too much time to terminate it now'. The same happens with IT projects: sometimes the company continues wasting money on these projects for a long time, even though there are no expected benefits from these projects. Eventually these projects are terminated anyway, but until this moment, the company spends a lot. The situation described above is a consequence of “escalation of commitment” - project continuation even after a manager receives negative feedback of the project’s success probability. According to Keil and Mähring (2010), even though escalation can occur in any type of project, it is more common among complex technological projects, such as IT projects. Escalation of commitment very often results in runaway projects. In order to avoid it, managers use de-escalation strategies, which allow the resources to be used in more effective. These strategies lead to project termination or turning around, which stops the flow of wasted investments. Numbers of researches explore escalation of commitment phenomena based on experiments and business cases. Moreover, during the last decade several frameworks were proposed for de-escalation strategy. However, there is no evidence of successful implementation of the de-escalation of commitment strategy in the literature. In addition, despite that fact that IT project management methodologies are widely used in the companies, none of them cover the topic of escalation of commitment risks. At the same time, there are no researches proposing the way to implement de-escalation of commitment strategy into the existing project management methodology The research is focused on a single case of large ERP implementation project by the consulting company. Hence, the main deliverables of the study include suggestions of improvement in de-escalation methods and techniques in the project and in the company. Moreover, the way to implement these methods into existing project management methodology and into the company general policies is found.

Application of the scrum framework in non-software project management

Scrum is an agile project management approach that has been widely practiced in the software development projects. It has proven to increase quality, productivity, customer satisfaction, transparency and team morale among other benefits from its implementation. The concept of scrum is based on the concepts of incremental innovation strategies, lean manufacturing, kaizen, iterative development and so on and is usually contrasted with the linear development models such as the waterfall method in the software industry. The traditional approaches to project management such as the waterfall method imply intensive upfront planning and approval of the entire project. These sort of approaches work well in the well-defined stable environments where all the specifications of the project are known in the beginning. However, in the uncertain environments when a project requires continuous development and incorporation of new requirements, they do not tend to work well. The scrum framework was inspiraed by Nonaka’s article about new product developement and was later adopted by software development practitioners. This research explores conditions for and benefits of the application of scrum framework beyond software development projects. There are currently a few case studies on the scrum implementation in non-software projects, but there is a noticeable trend of it in the scrum practitioners’ community. The research is based on the real-life context multiple case study analysis of three different non-software projects. The results of the research showed that in order to succeed within scrum projects need to satisfy certain conditions – necessary and sufficient. Among them the key factors are uncertainty of the project environment, not well defined outcomes, commitment of the scrum teams and management support. The top advantages of scrum implementation identified in the present research include improved transparency, accountability, team morale, communications, cooperation and collaboration. Further researches are advised to be carried out in order to validate these findings on a larger sample and to focus on more specific areas of scrum project management implementation.

Lectio praecursoria : Systems between information and knowledge : in a memory management model of an extended enterprise

VTT Jouni Meriluodon valtio-opin alaan kuuluva väitöskirja Systems between information and knowledge : in a memory management model of an extended enterprise tarkastettiin 21.6.2011 Helsingin yliopistossa.

Working Capital Management Model in value chains

The objective of this Master’s thesis is to create a calculation model for working capital management in value chains. The study has been executed using literature review and constructive research methods. Constructive research methods were mainly modeling. The theory in this thesis is founded in research articles and management literature. The model is developed for students and researchers. They can use the model for working capital management and comparing firms to each other. The model can also be used to cash management. The model tells who benefits and who suffers most in the value chain. Companies and value chains cash flows can be seen. By using the model can be seen are the set targets really achieved. The amount of operational working capital can be observed. The model enables user to simulate the amount of working capital. The created model is based on cash conversion cycle, return on investment and cash flow forecasting. The model is tested with carefully considered figures which seem to be though realistic. The modeled value chain is literally a chain. Implementing this model requires from the user that he/she have some kind of understanding about working capital management and some figures from balance sheet and income statement. By using this model users can improve their knowledge about working capital management in value chains.

Project Management Tools in Agile Embedded Systems Development

Agile methods have become increasingly popular in the field of software engineering. While agile methods are now generally considered applicable to software projects of many different kinds, they have not been widely adopted in embedded systems development. This is partly due to the natural constraints that are present in embedded systems development (e.g. hardware–software interdependencies) that challenge the utilization of agile values, principles and practices. The research in agile embedded systems development has been very limited, and this thesis tackles an even less researched theme related to it: the suitability of different project management tools in agile embedded systems development. The thesis covers the basic aspects of many different agile tool types from physical tools, such as task boards and cards, to web-based agile tools that offer all-round solutions for application lifecycle management. In addition to these two extremities, there is also a wide range of lighter agile tools that focus on the core agile practices, such as backlog management. Also other non-agile tools, such as bug trackers, can be used to support agile development, for instance, with plug-ins. To investigate the special tool requirements in agile embedded development, the author observed tool related issues and solutions in a case study involving three different companies operating in the field of embedded systems development. All three companies had a distinct situation in the beginning of the case and thus the tool solutions varied from a backlog spreadsheet built from scratch to plug-in development for an already existing agile software tool. Detailed reports are presented of all three tool cases. Based on the knowledge gathered from agile tools and the case study experiences, it is concluded that there are tool related issues in the pilot phase, such as backlog management and user motivation. These can be overcome in various ways epending on the type of a team in question. Finally, five principles are formed to give guidelines for tool selection and usage in agile embedded systems development.

Development of project management procedures for customer project business

Objective of the thesis is to develop project management procedure for chilled beam projects. In organization is recognized that project management techniques could help in large and complex projects. Information sharing have been challenging in projects, so improvement of information sharing is one key topic of the thesis. Academic researches and literature are used to find suitable project management theories and methods. Main theories are related to phases of the project and project management tools. Practical knowledge of project management is collected from two project business oriented companies. Project management tools are chosen and modified to fulfill needs of the beam projects. Result of the thesis is proposed project management procedure, which includes phases of the chilled beam projects and project milestones. Project management procedure helps to recognize the most critical phases of the project and tools help to manage information of the project. Procedure increases knowledge of the project management techniques and tools. It also forms coherent project management working method among the chilled beam project group.

Projektijohtamisen kehittäminen puutuoteteollisuudessa

Tämän tutkimuksen tavoitteena on selvittää kuinka parannetaan ja kehitetään tuoteosakauppaan perustuvan toimitusprojektin projektinjohtamista ja sitä kautta projektin tehokkuutta projektinhallinnan keinoin. Toimitusprojektissa projektijohtamisesta vastaa käytännössä projektipäällikkö. Tutkimuksen tavoitteena on rakentaa tuoteosakauppaan perustuvaan toimitusprojektiin soveltuva projekti-päällikkövetoinen projektijohtamismalli. Tutkimusmetodina käytettiin case studya eli tapaustutkimusta. Teoriaosassa haettiin kirjallisuudesta tietoa projektista, toimitusprojektista, tuoteosakaupasta, projektijohtamisesta, projektipäällikön tehtävistä, rooleista ja ominaisuuksista, projektijohtamisesta ja suorituskyvystä sekä projektinhallinnan eri osa-alueista. Empiirisessä osassa suoritettiin haastattelututkimus kohdeyrityksessä. Haastattelun tarkoituksena oli tutkia kohdeyrityksen projektijohtamisen nykytilaa. Tämä tutkimus osoittaa, että tuoteosakauppaan perustuvan toimitusprojektin projektijohtamista pystytään parantamaan ja tehostamaan projektinhallinnan keinoin. Lisäksi löydettiin tekijät, jotka ovat hyvän projektijohtamisen takana. Tässä tutkimuksessa rakennettu projektijohtamismalli osoittaa, että projektinhallinnan osa-alueita hyödyntämällä pystytään rakentamaan toimiva projektijohtamismalli.

Evaluating the Maturity of Data Management Practices in a Major Energy Provider Company

Data is the most important asset of a company in the information age. Other assets, such as technology, facilities or products can be copied or reverse-engineered, employees can be brought over, but data remains unique to every company. As data management topics are slowly moving from unknown unknowns to known unknowns, tools to evaluate and manage data properly are developed and refined. Many projects are in progress today to develop various maturity models for evaluating information and data management practices. These maturity models come in many shapes and sizes: from short and concise ones meant for a quick assessment, to complex ones that call for an expert assessment by experienced consultants. In this paper several of them, made not only by external inter-organizational groups and authors, but also developed internally at a Major Energy Provider Company (MEPC) are juxtaposed and thoroughly analyzed. Apart from analyzing the available maturity models related to Data Management, this paper also selects the one with the most merit and describes and analyzes using it to perform a maturity assessment in MEPC. The utility of maturity models is two-fold: descriptive and prescriptive. Besides recording the current state of Data Management practices maturity by performing the assessments, this maturity model is also used to chart the way forward. Thus, after the current situation is presented, analysis and recommendations on how to improve it based on the definitions of higher levels of maturity are given. Generally, the main trend observed was the widening of the Data Management field to include more business and “soft” areas (as opposed to technical ones) and the change of focus towards business value of data, while assuming that the underlying IT systems for managing data are “ideal”, that is, left to the purely technical disciplines to design and maintain. This trend is not only present in Data Management but in other technological areas as well, where more and more attention is given to innovative use of technology, while acknowledging that the strategic importance of IT as such is diminishing.

Management of Nitrogen Oxides Reduction Project in a Cement Plant

The main aim of this study was to develop the project management framework model which would serve as the new model to follow for upcoming projects at the Lappeenranta cement plant. The other goal was to execute the SNCR (selective non catalytic reduction) project successfully so that the nitrogen oxides emissions are below the stated emission limit when the new emission limit comes into effect beginning in July, 2008. Nitrogen oxides, project management aspects, SNCR and the invested system are explained in the theory part. In the practical part of the study, the SNCR project in the Lappeenranta cement plant was executed and the findings were documented. In order to reach the aim of this study, a framework of project management was made. The framework is based on the executed SNCR project, previous projects in the cement plant and on the available literature relating to the subject matter. The developed project turned out to be successful.

Towards Inter-organizational Working Capital Management

Working capital is an investment which is tied up into the inventories and accounts receivable and which is released with accounts payable. Due to the current business landscape with tightened financial conditions and finance markets, organizations emphasize efficient working capital management. With efficient working capital management, a company can reduce the need of finance, free up cash, increase profitability, improve liquidity, increase the efficiency of operations, and decrease (financing) costs. From the perspective of an individual company, efficient working capital management means decreasing inventory levels by shortening the cycle time of inventories, decreasing accounts receivable by shortening the trade credit terms and effective collection procedures, and increasing the level of accounts payable by paying the suppliers later. From an inter-organizational perspective, however, working capital should not be sub-optimized by a single company but holistic view to working capital management through the supply chain should be adopted to create value and improve performance together. The purpose of this research is to take academic research as well as practical management towards inter-organizational working capital management. The thesis discusses the benefits as well as mechanisms of working capital management in the inter-organizational context and has two main objectives: (1) to examine the effect of inter-organizational working capital management on performance in the value chain context and (2) to develop models of working capital management for internal as well as inter-organizational value chains. The results of the archival research conducted in the value chain of the pulp and paper industry and the value chain of the automotive industry indicate that companies can increase relative profitability by managing working capital comprehensively by taking into account all three components, and holistically though the value chain. Companies in the value chain benefit from different strategies in working capital management depending on the position of the company in the value chain. This can be taken into account in inter-organizational working capital management. The effects of inter-organizational working capital management actions on the financing costs of working capital were studied via simulations. Simulations also show that the value chain and individual companies benefit from an inter-organizational view to working capital management. Inter-organizational working capital management actions include for example: shortening the cycle time of inventories, reducing product costs, shifting inventories, shortening payment terms, and considering the cost of capital. The thesis also provides solutions for the practical requirements for tools to control working capital. The design science part of the research introduces the adjusted cash conversion cycle (ACCC) model for internal value chains, as well as models for working capital management in the inter-organizational value chain context: the working capital management model (WCMM) and the financial cycle time model (FCTM) designed in corporation and product levels respectively. This research contributes to literature on working capital management and interorganizational accounting. The research gives a holistic, inter-organizational view to the management of working capital. It advances the knowledge in working capital management on operational level, increases knowledge in the recently risen theme of supply chainoriented, collaborative working capital management, combines management accounting research with supply chain management research, and contributes to the demand of practical inter-organizational accounting methods. In addition, the research has strong practical focus as new managerial methods are introduced.

Knowledge, processes and relationships in organizational change: Understanding how to facilitate management of intellectual capital in diverse organization structures and cultures.

This study examined relationships of organizational dependencies, change management and developed intellectual knowledge resources, in different intellectual capital based development programs on ICT-sector. Study was carried out in a research context, where high degree of external organizational contingencies existed and lots of changes in several development programs had taken place in the last years. From a scientific perspective the main contribution was that evidence between relationships of organizational dependencies, change model portfolio and developed knowledge resources could be suggested. From managerial perspective the primary implication was that in situations where sustainable competitive advantage is pursued by means of increasing knowledge based productivity of labor, firms should seek to pursue organizational settings where external dependencies have minimal amount of effect.

Performance measurement model for projects from a strategic management perspective

This research studied the project performance measurement from the perspective of strategic management. The objective was to find a generic model for project performance measurement that emphasizes strategy and decision making. Research followed the guidelines of a constructive research methodology. As a result, the study suggests a model that measures projects with multiple meters during and after projects. Measurement after the project is suggested to be linked to the strategic performance measures of a company. The measurement should be conducted with centralized project portfolio management e.g. using the project management office in the organization. Metrics, after the project, measure the project’s actual benefit realization. During the project, the metrics are universal and they measure the accomplished objectives relation to costs, schedule and internal resource usage. Outcomes of these measures should be forecasted by using qualitative or stochastic methods. Solid theoretical background for the model was found from the literature that covers the subjects of performance measurement, projects and uncertainty. The study states that the model can be implemented in companies. This statement is supported by empirical evidence from a single case study. The gathering of empiric evidence about the actual usefulness of the model in companies is left to be done by the evaluative research in the future.

Developing Processes and Learning in a Project-based Firm

Tämän diplomityön tavoitteena on kuvata tiedonkulkua projektiliiketoimintaa harjoittavassa yrityksessä sekä analysoida kuvausta määrittäen mahdolliset kehityskohdat. Työssätuotetut kuvaukset ja kehityskohtien määrittäminen toimivat pohjana yrityksen kehittäessä projektien hallintaansa tulevaisuudessa. Työssä valitaan tietojohtamisen näkökulma sopivaksi lähestymistavaksi yrityksen toiminnananalysointiin. Haastatteluin kerätyn tutkimusmateriaalin perusteella luodaan prosessikuvaukset jotka mallintavat tietovirtoja yrityksen projektien aikana tapahtuvien prosessien välillä. Kuvausta peilataan tietämyksen luomisen sekä projektien tietojohtamisen teoriaan ja määritetään kehityskohteita. Kehityskohteiden määrittämisen lisäksi ehdotetaan mahdollisia toimenpiteitä tiedon ja tietämyksen hallinnan kehittämiseksi. Kokemusten ja opittujen asioiden sekäpalautteen kerääminen projektien aikana sekä niiden jälkeen havaittiin tärkeimmäksi kehityskohdaksi. Näiden keräämisen voidaan todeta vaativan järjestelmällisyyttä jotta projektien onnistumiset sekä niissä saavutetut parannukset voidaan toistaa jatkossa ja virheet sekä epäonnistumiset sitä vastoin välttää.