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.

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.

EPC-projektin hallinta ja johtaminen

Tämän diplomityön tavoitteena oli tutkia erään projektiliiketoimintaa harjoittavan yrityksen toimintajärjestelmää. Työn lähtökohtana oli yrityksen toimittamien projektien laajuuden nopea kasvu lähivuosien aikana. Työssä tutkittiin yrityksen nykyistä toimintajärjestelmää ja sen ohjeistusta nimen omaan EPC (engineering procurement construction) projekteissa. Toimintajärjestelmän ohjeistusta tutkittiin yrityksessä tehdyillä henkilöhaastatteluilla sekä vertaamalla olemassa olevia ohjeita ja kuvauksia projektin hallinnan ja johtamisen teorioihin. Teoriat, joihin yrityksen toimintajärjestelmää työssä verrattiin olivat Project Management Institute:n, Project Management Body of Knowledge ja International standard ISO 10006, Quality Management guidelines to quality in project management. Työn teoriaosassa käsiteltiin projektin hallintaa ja johtamista, projektin eri vaiheita, projektin organisointia ja ositusta sekä projektikulttuuria. Työn tuloksena luotiin käsitys siitä, mitä osaprosesseja EPC-projektin hallintaan ja johtamiseen kohdeyrityksessä liittyy. Prosesseja tutkimalla muodostettiin käsitys yrityksen toimintajärjestelmän ohjeistuksen tasosta ja esitettiin tältä pohjalta mahdollisuuksia toimintajärjestelmän kehittämiseksi. Yhtenä työn keskeisimmistä tuloksista esitettiin EPC-projektin projektikuvaus.

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.

Management of interdependency in project portfolio

Project management has evolved in recent decades. Project portfolio management, together with multi project management, is an emerging area in the project management field in practice, and correspondingly in academic research and forums. In multi project management, projects cannot be handled isolated from each other, as they often have interdependencies that have to be taken into account. If the interdependencies between projects are evaluated during the selection process, the success rate of the project portfolio is increased. Interdependencies can be human resources, technological, and/or market based. Despite of the fact that interdependency as a phenomenon has roots in the 1960s and is related to famous management theories, it has not been much studied, although in practice most companies use it to great extent. There exists some research on interdependency, but prior publications have not emphasized the phenomenon per se, because a practical orientation practitioner techniques prevails in the literature. This research applies the method triangulation, electronic surveys and multiple case study. The research concentrates on small to large companies in Estonia and Finland, mainly in construction, engineering, ICT, and machinery industries. The literature review reveals that interdependencies are deeply involved in R&D and innovation. Survey analysis shows that companies are aware of interdependency issues in general, but they i have lack of detailed knowledge to use it thoroughly. Empirical evidence also indicates that interdependency techniques influence the success rate and other efficiency aspects to different extents. There are a lot of similarities in interdependency related managerial issues in companies of varying sizes and countries in Northern Europe. Differences found in the study are for instance the fact that smaller companies face more difficulties in implementing and evaluating interdependency procedures. Country differences between Estonia and Finland stem from working solutions to manage interdependencies on a daily basis.historical and cultural reasons, such as the special features of a transition country compared to a mature country. An overview of the dominant problems, best practices, and commonly used techniques associated with interdependency is provided in the study. Empirical findings show that many interdependency techniques are not used in practice. A multiple case study was performed in the study to find out how interdependencies are managed in real life on a daily basis. The results show that interdependencies are mostly managed in an informal manner. A description of managing the interdependencies and implementation procedures is given. Interdependency procedures are hard to implement, especially in smaller companies. Companies have difficulties in implementing interdependency procedures and evaluating them. The study contains detailed results on how companies have implemented working solutions to manage interdependencies on a daily basis

Project Resource Management in R&D Public Sector Organization

In R&D organizations multiple projects are executed concurrently. Problems arises in managing shared resources since they are needed by multiple projects simultaneously. The objective of this thesis was to study how the project and resource management could be developed in a public sector R&D organization. The qualitative research was carried out in the Magnetic Measurements section at CERN where the section measures magnets for particle accelerators and builds state of the art measurement devices for various needs. Hence, the R&D and measurement projects are very time consuming and very complex. Based on the previous research and the requirements from the organization the best alter- native for resource management was to build a project management information system. A centralized database was constructed and on top of it was built an application for interacting and visualizing the project data. The application allows handling project data, which works as a basis for resource planning before and during the projects are executed. It is one way to standardize the work-flow of projects, which strengthens the project process. Additionally, it was noted that the inner customer’s database, the measurement system and the new application needed to be integrated. Further integration ensures that the project data is received efficiently from customers and available not only within the application but also during the concrete work. The research results introduced a new integrated application, which centralizes the project information flow with better visibility.

Project Charter, Scope, and Time Management In the Movie Industry

This thesis explores how the project charter development, project scope management, and project time management are executed in a Finnish movie production. The deviations and analogies between a case movie production and best practices suggested in PMBOK are presented. Empirical material from the case is gathered with two semi-structured interviews with a producer and a line producer. The interview data is categorized according to PMBOK knowledge areas. The analysis is complemented with movie industry specific norms found in popular movie production guides. The described and observed methods are linked together and the relationship between them is discussed. The project charter development, which is referred as a green light process in the movie industry, is mostly analogous between all areas. The deviations are in the level of formality. The green lighting in the case movie was accomplished without bureaucratic reports described in movie production guides. The empirical material shows that project management conventions and movie industry employ similar methods especially in scope management. Project management practices introduce a work breakdown structure (WBS) method, and movie production accomplishes the same task by developing a shooting script. Time management of the case movie deviates on most parts from the methods suggested in PMBOK. The major deviation is resource management. PMBOK suggests creating a resource breakdown structure. The case movie production accomplished this through budgeting process. Furthermore the popular movie production guides also disregard resource management as sovereign process. However the activity listing is quite analogous between the case movie and PMBOK. The final key observation is that although there is a broad set of effective and detailed movie industry specific methods, a comprehensive methodology that would cover the whole production process, such as Prince2 or Scrum, seems to be missing from the movie industry.

Project charter, scope, and time management in the movie industry

This thesis explores how the project charter development, project scope management, and project time management are executed in a Finnish movie production. The deviations and analogies between a case movie production and best practices suggested in PMBOK are presented. Empirical material from the case is gathered with two semi-structured interviews with a producer and a line producer. The interview data is categorized according to PMBOK knowledge areas. The analysis is complemented with movie industry specific norms found in popular movie production guides. The described and observed methods are linked together and the relationship between them is discussed. The project charter development, which is referred as a green light process in the movie industry, is mostly analogous between all areas. The deviations are in the level of formality. The green lighting in the case movie was accomplished without bureaucratic reports described in movie production guides. The empirical material shows that project management conventions and movie industry employ similar methods especially in scope management. Project management practices introduce a work breakdown structure (WBS) method, and movie production accomplishes the same task by developing a shooting script. Time management of the case movie deviates on most parts from the methods suggested in PMBOK. The major deviation is resource management. PMBOK suggests creating a resource breakdown structure. The case movie production accomplished this through budgeting process. Furthermore the popular movie production guides also disregard resource management as sovereign process. However the activity listing is quite analogous between the case movie and PMBOK. The final key observation is that although there is a broad set of effective and detailed movie industry specific methods, a comprehensive methodology that would cover the whole production process, such as Prince2 or Scrum, seems to be missing from the movie industry.

Release Process Effectiveness - Case of Operating Room Management Software

Työn päätavoitteena oli tuoda esiin tärkeimmät julkistamisprosessin tehokkuuteen vaikuttavat tekijät. Tutkimuksessa tarkasteltiin aihetta julkistamisprojektien vetäjän näkökulmasta. Kirjallinen selvitys kattaa keskeisimmät ohjelmistoprosessin, palvelun laadun sekä projektihallinnan teoriat. Kokeellisena aineistona käytettiin asiakkailta ja myynnin sekä käyttöönoton organisaatioilta tullutta palautetta ja asiantuntijahaastatteluita. Case-tuotteena tarkasteltiin suuren kansainvälisen yrityksen jälleenmyymää leikkaussalihallinnan ohjelmistoa. Tärkeimpiä julkistamisprosessin tehokkuuteen vaikuttavia tekijöitä ovat tiekartan ja julkistamispakettien sisällön hallinta, projektin aikataulujen pitäminen, rehellinen ja nopea kommunikaatio myyntikanavaan ja asiakkaille, sekä hyvin toteutettu testaus. Työssä käydään läpi esimerkkistrategioita kehittymiseen näillä alueilla.

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ää.

Procurement in Project Implementation

Tutkimus keskittyy hankintatoimen kehittämiseen osana laitosprojektien toteutusta. Työ pohjautuu empiiriseltä taustaltaan Pöyry Oyj:n projektiliiketoimintaan ja työn tarkastelunäkökulmaksi onvalittu projektihallinnosta vastaavan yrityksen näkökulma. Tutkimus on hyvin käytännönläheinen ¿ se lähtee hankinnan ja sen seurannan ongelmista ja pyrkii tarjoamaan niihin uudenlaisia ratkaisuja. Pohjimmiltaan tutkimus kuuluu teollisuustalouden piiriin, vaikka tietojärjestelmätieteellä on vahva tukirooli. Työn tavoitteet ja tulokset liittyvät teollisuustaloudelle ominaisesti yrityksen toiminnan kehittämiseen, käytetyt välineet ja ratkaisut puolestaan hyödyntävät tietojärjestelmätieteen antamia mahdollisuuksia. Tutkimuksessa on käytetty konstruktiivista tutkimusotetta, jonka mukaisesti on luotu innovatiivisia konstruktioita ratkaisemaan aitoja reaalimaailman ongelmia ja tätä kautta tuotettu kontribuutioita teollisuustaloudelle. Tavoitteena oli järjestää hankintatoimi ja sen seuranta suurissa laitosprojekteissa tehokkaammin. Tätä varten uudistettiin ensin projektihallinnon ja hankintatoimen toimintaohjeet vastaamaan paremmin nykyajan vaatimuksia. Toimintaohjeiden perusteella ryhdyttiin toteuttamaan hankintaohjelmistoa, joka pystyisi kattamaan kaikki toimintaohjeissa kuvatut piirteet. Lopulta hankintaohjelmisto toi mukanaan uusia piirteitä projektihallintoon ja hankintatoimeen ja nämä sisällytettiin toimintaohjeisiin. Tähän kehitystyöhön ryhdyttiin, jotta laitosprojektien projektihallinto ja hankintatoimi toimisivat paremmin, eli pienemmin kustannuksin tuottaen projekteissa tarvittavat tulokset nopeammin, tarkemmin ja laadukkaammin. Tutkimuksella on kolmenlaisia tuloksia: hankintatoimen parannetut metodit, hankintaohjelmiston pohjana olevat toiminta- ja laskentamallit sekä implementaationa hankintasovellus. Uudistetut projekti- ja hankintaohjeet kuvaavat hankintatoiminnan parannettuja metodeja. Hankintaohjelmistoasuunnitellessa ja kehitettäessä tehdyt kuvaukset sisältävät uusia malleja niin hankintaprosessille kuin hankinnan seuraamiseksi suurissa laitosprojekteissa. Itse ohjelmisto on tuloksena implementaatio, joka perustuu parannettuihin hankintametodeihin ja uusiin toiminta- ja laskentamalleihin. Uudistetut projekti- ja hankintaohjeet ovat olleet käytössä Pöyry Oyj:ssä vuodesta 1991. Vuosien varrella nämä toimintaohjeet ovat auttaneet ja tukeneet satojen laitosprojektientoteutusta ja ylläpitäneet Pöyry Oyj:n kilpailukykyä kansainvälisenä projektitalona. Hankintasovellus puolestaan on ollut käytössä useissa projekteissa ja sen on havaittu pienentävän hankintatoimen suoria työkustannuksia laitosprojekteissa. Sovelluksen katsotaan myös tuovan epäsuoria kustannussäästöjä parempien hankintapäätösten muodossa, mutta näiden säästöjen suuruutta ei pystytä luotettavasti arvioimaan.