Implementointimetodologia ja projektinhallinta menestyksekkään konsultointitoiminnan tekijöinä Case: ADVOCORP OY

Työn teettäjä yrityksen ADVOCORP Oy:n tavoitteena oli löytää ja nimetä näkökulmia, joihin sen toiminnankehityssuunnitelmassa olisi osattava ottaa kantaa. Suurin osa kuluista syntyy projektityöstä. Pienessä (noin 10 henkilön) yrityksessä korostuu oikeisiin asioihin keskittyminen. Tässä työssä tarkastellaan käytössä olevan projektimetodologian sopivuutta nykyisiin asiakasprojekteihin. Lisäksi laadullisen projektin- ja tiedonhallinnan kautta pyritään tunnistamaan ja nimeämään toiminnankehityskohteita. Tuloksena esitetään ohjeellinen lausunto kehityssuunnitelman tekemiseksi yrityksessä. ADVOCORP Oy:n projektimetodologia perustuu Adaytumin julkaisemaan Planning-projektien läpivientiin suunniteltuun implementointimetodologiaan. Projektimetodologian tarkoitus on tarjota etukäteen suunniteltu malli toimitusprosessien systemaattiseksi läpiviemiseksi. Konsultoinnin ollessa yrityksen toimiala, työssä lähdetään liikkeelle tekijöiden tarkastelusta, joihin onnistunut konsultointityö perustuu. Projektimetodologian kehittämisen ohella työssä tarkennetaan nykyisen metodologiamallin sisältökuvausta ja eri projektivaiheissa toimitettavia asioita.

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.

Knowledge creation and transfer in an iterative project environment

This Master’s Thesis examines knowledge creation and transfer processes in an iterative project environment. The aim is to understand how knowledge is created and transferred during an actual iterative implementation project which takes place in International Business Machines (IBM). The second aim is to create and develop new working methods that support more effective knowledge creation and transfer for future iterative implementation projects. The research methodology in this thesis is qualitative. Using focus group interviews as a research method provides qualitative information and introduces the experiences of the individuals participating in the project. This study found that the following factors affect knowledge creation and transfer in an iterative, multinational, and multi-organizational implementation project: shared vision and common goal, trust, open communication, social capital, and network density. All of these received both theoretical and empirical support. As for future projects, strengthening these factors was found to be the key for more effective knowledge creation and transfer.

The Management of Intellectual Capital in the Early Phases of Project Marketing

This study aims at enhancing understanding and deriving new constructs about the management of intellectual capital in the early phases of project marketing. The research methodology employed is deductive; conceptual reasoning is based on existing literature. The study's knowledge base is drawn from the bodies of literature dealing with project, relationship, and industrial marketing, as well as from the literature dealing with mechanical engineering, network approach, systems selling, R&D, project portfolio, strategic, financial, and knowledge management. As a result, three processes, 32 summaries and 19 conclusions give to the management of intellectual capital meaning in the context of project marketing. These conclusions and synthesis are proposed to improve the existing concepts and models in project marketing.

Improving Product Information Management in Global Project Based Manufacturing

The transition of project based manufacturing business, even more into global networks, sets up challenges for companies to manage their business in this new operating environment. One way to tackle these challenges is the successful management of product information through an extended product’s lifecycle. Thus, one objective of this research is to find ways how product information management in global project based manufacturing can be improved. Another objective is to find a solution how the target company can improve its product information management in the offer-to-procurement business process. Due to the nature of the topic, the study follows constructive research methodology with qualitative methods. By combining literature related to this topic a framework is created to improve product information management in global project based manufacturing. The improvement process in this framework is based on a systematic approach from the current state towards target state. A general aim for improvements should be the integrated product and project lifecycle information management through Lean approach. This introduced framework is applied to the target company through two case projects. Data for building view of current state and analysis is collected mostly by theme interviews and also utilizing other material from the target company. Used tools help to analyzing was the BPMN and the Trace matrix for business chains. Results of the improvement process are collected in a solution proposal which contain the strategic target state as well as long and short term objectives. The strategic target state is defined as controlled customization. Also during the improvement process are created the Information requirements chart in the offer-to-procurement business process, and the Project related initial information questionnaire to customer.

Creating risk measurement model to project portfolio management in construction company

This thesis was carried out as a case study of a company YIT in order to clarify the sev-erest risks for the company and to build a method for project portfolio evaluation. The target organization creates new living environment by constructing residential buildings, business premises, infrastructure and entire areas worth for EUR 1.9 billion in the year 2013. Company has noted project portfolio management needs more information about the structure of project portfolio and possible influences of market shock situation. With interviews have been evaluated risks with biggest influence and most appropriate metrics to examine. The major risks for the company were evaluated by interviewing the executive staff. At the same time, the most appropriate risk metrics were considered. At the moment sales risk was estimated to have biggest impact on company‟s business. Therefore project port-folio evaluation model was created and three different scenarios for company‟s future were created in order to identify the scale of possible market shock situation. The created model is tested with public and descriptive figures of YIT in a one-year-long market shock and the impact on different metrics was evaluated. Study was conducted using con-structive research methodology. Results indicate that company has notable sales risk in certain sections of business portfolio.

Lean Six Sigma in a Manufacturing Lead Time Improvement Project

The objective of this research is to demonstrate the use of Lean Six Sigma methodology in a manufacturing lead time improvement project. Moreover, the goal is to develop working solutions for the target company to improve its manufacturing lead time. The theoretical background is achieved through exploring the literature of Six Sigma, Lean and Lean Six Sigma. The development will be done in collaboration with the related stakeholders, by following the Lean Six Sigma improvement process DMAIC and by analyzing the process data from the target company. The focus of this research is in demonstrating how to use Lean Six Sigma improvement process DMAIC in practice, rather than in comparing Lean Six Sigma to other improvement methodologies. In order to validate the manufacturing system’s current state, improvement potential and solutions, statistical tools such as linear regression analysis were used. This ensured that all the decisions were as heavily based on actual data as possible. As a result of this research, a set of solutions were developed and implemented in the target company. These solutions included batch size reduction, bottleneck shift, first-in first-out queuing and shifting a data entry task from production planners to line workers. With the use of these solutions, the target company was able to reduce its manufacturing lead time by over one third.

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.

Development of Project Logistics in Engineering, Procurement and Construction Projects

The aim of this Master’s Thesis is to develop project logistics functions in large scale en-gineering, procurement and construction projects. The background of the research topic is compounded from two separate subjects; OPAL Program and case study of an actual EPC project. The purpose is to examine Project Logistics process in accordance with OPAL Program as well as logistics process in focus EPC project. Both entities are researched by using the case study research methodology. Logistics process of the focus EPC project is described as well as presented and in addi-tion, logistics related findings and observations are introduced. Significant findings and observations are found from logistics costs as well as shipment volume estimations in the early phase of the focus ECP project. A notable finding is also that because goods were transported as readily assembled as possible it caused expensive oversized cargo deliveries. From findings and observation of the focus EPC project it can be derived that logistics has to be involved in the early sales phase in order to receive more accurate logistics cost esti-mations for project deliveries. It is also noticed that in order to obtain savings in logistics costs, oversized deliveries must be avoided.