Business Development Efforts and Performance Improvements in SMEs Case Study of Business Development Projects Implemented in SME

Under the circumstances of the increasing market pressure, enterprises try to improve their competitive position by development efforts, and a business development project is one tool for that. There are not many answers to the question of how the development projects launched to improve the business performance in SMEs have succeeded. Theacademic interest in the business development project success has mainly focused on projects implemented in larger organisations rather than in SMEs. The previous studies on the business success of SMEs have mainly focused on new business ventures rather than on existing SMEs. However, nowadays a large number of business development projects are undertaken in existing SMEs, where they can pose a great challenge. This study focuses on business development success in SMEs thathave already established their business. The objective of the present study is to gain a deep understanding on business development project success in the SME-context and to identify the dimensions and factors affecting the project success. Further, the aim is to clarify how the business development projects implemented in SMEs have affected their performance. The empirical evidence is based on multiple case study. This study builds a framework for a generic theory of business development success in the SME-context, based on literature from the areas ofproject and change management, entrepreneurship and small business management, as well as performance measurement, and on empirical evidence from SMES. The framework consists of five success dimensions: entrepreneurial, project preparation, change management, project management and project success. The framework provides a systematic way for analysing the business development project and its impact on the performance and on the performing company. This case evidence indicates that successful business development projects have a balanced, high performance concerning all the dimensions. Good performance in one dimension is not enoughfor the project success, but it gives a good ground for the other dimensions. The other way round, poor performance in one success dimension affects the others, leading to poor performance of the project. In the SME-context the business development project success seems to be dependent on several interrelated dimensions and factors. Success in one area leads to success in other areas, and so creates an upward success spiral. Failure in one area seems to lead to failure in other areas, creating a downward failure spiral. The study indicates that the internal business development projects have affected the SMEs' performance widely also on areas and functions not initially targeted. The implications cover all thesuccess categories: the project efficiency, the impact on the customer, the business success and the future potentiality. With successful cases, the success tends to spread out to areas and functions not mentioned as the project goals, andwith unsuccessful cases the failure seems to spread out widely to the SMEs' other functions. This study also indicates that the most important key factors for successful business development project implementation are the strength of intention, business ability, knowledge, motivation and participation of the employees, as well as adequate and well-timed training provided to the employees.

Learning in Product Development Projects - Responding to challenges in global industrial company

Verkostoitunut kansainvälinen tuotekehitys on tärkeä osa menestystä nykypäivän muuttuvassa yritysmaailmassa. Toimintojen tehostamiseksi myös projektitoiminnot on sopeutettava kansainväliseen toimintaympäristöön. Kilpailukyvyn säilyttämiseksi projektitoimintoja on lisäksi jatkuvasti tehostettava. Yhtenäkeinona nähdään projektioppiminen, jota voidaan edistää monin eri tavoin. Tässätyössä keskitytään projektitiedonhallinnan kehittämisen tuomiin oppimismahdollisuuksiin. Kirjallisuudessa kerrotaan, että projektitiedon jakaminen ja sen hyödyntäminen seuraavissa projekteissa on eräs projektioppimisen edellytyksistä. Tämäon otettu keskeiseksi näkökulmaksi tässä tutkimuksessa. Lisäksi tutkimusalueen rajaamiseksi työ tarkastelee erityisesti projektioppimista kansainvälisten tuotekehitysprojektien välillä. Työn tavoitteena on esitellä keskeisiä projektioppimisen haasteita ja etsiä konkreettinen ratkaisu vastaamaan näihin haasteisiin. Tuotekehitystoiminnot ja kansainvälinen hajautettu projektiorganisaatio kohtaavat lisäksi erityisiä haasteita, kuten tiedon hajautuneisuus, projektihenkilöstön vaihtuvuus, tiedon luottamuksellisuus ja maantieteelliset haasteet (esim. aikavyöhykkeet ja toimipisteen sijainti). Nämä erityishaasteet on otettu huomioon ratkaisua etsittäessä. Haasteisiin päädyttiin vastaamaan tietotekniikkapohjaisella ratkaisulla, joka suunniteltiin erityisesti huomioiden esimerkkiorganisaation tarpeet ja haasteet. Työssä tarkastellaan suunnitellun ratkaisun vaikutusta projektioppimiseen ja kuinka se vastaa havaittuihin haasteisiin. Tuloksissa huomattiin, että projektioppimista tapahtui, vaikka oppimista oli vaikea suoranaisesti huomata tutkimusorganisaation jäsenten keskuudessa. Projektioppimista voidaan kuitenkin sanoa tapahtuvan, jos projektitieto on helposti koko projektiryhmän saatavilla ja se on hyvin järjesteltyä. Muun muassa nämä ehdot täyttyivät. Projektioppiminen nähdään yleisesti haastavana kehitysalueena esimerkkiorganisaatiossa. Suuri osa tietämyksestä on niin sanottua hiljaistatietoa, jota on hankala tai mahdoton saattaa kirjalliseen muotoon. Näin olleen tiedon siirtäminen jää suurelta osin henkilökohtaisen vuorovaikutuksen varaan. Siitä huolimatta projektioppimista on mahdollista kehittää erilaisin toimintamallein ja menetelmin. Kehitys vaatii kuitenkin resursseja, pitkäjänteisyyttä ja aikaa. Monet muutokset voivat vaatia myös organisaatiokulttuurin muutoksen ja vaikuttamista organisaation jäseniin. Motivaatio, positiiviset mielikuvat ja selkeät strategiset tavoitteet luovat vakaan pohjan projektioppimisen kehittämiselle.

Planning and control of internal development projects in a fast changing environment: Case study

Tutkimuksen tarkoituksena on kuvata ja ymmärtää kuinka sisäisiä kehityshankkeita voidaan hallita onnistuneesti kun toimitaan nopeasti muuttuvassa ympäristössä. Tutkimus kuvailee etenkin projekteille tärkeitä menestymistekijöitä, kuten suunnittelu, kontrollointi ja päätöksenteko. Tutkimus selvittää yleisimmät ongelma-alueet case-organisaation sisäisten kehityshankkeiden hallinnassa. Tutkimus on luonteeltaan laadullinen tutkimus, jossa tutkimusmenetelmänä on käytetty tapaustutkimusta. Empiirisessa osassa käsittellään case-organisaation sisäisiä informaatioteknologia-hankkeita (IT) ja uusien konseptien kehityshankkeita (NCD). iSisäisten kehityshankkeiden erilaisuuden ymmärtäminen oli tutkimuksen tärkein tulos. Tutkimuksen empiirinen osio osoitti sen, että epävarmuudella on erittäin suuri vaikutus projektihallintaan sekä projektin kontrollointiin. Case-organisaation IT-projektien onnistuminen riippuu organisaatiomuu-toksen onnistumisesta. Asiakkaisiin ja markkinoihin liittyvät epävarmuudet ovat vaikuttavimmat NCD projektien epävarmuuksista. Näillä epävarmuuk-sil­la on vaikutusta projektihallintaan jonka myötä NCD projektit juuttuvat useim­mi­ten noidankehiin tai ne lopetetaan jo aikaisessa vaiheessa.

On Effort Estimation in Software Projects

Software engineering is criticized as not being engineering or 'well-developed' science at all. Software engineers seem not to know exactly how long their projects will last, what they will cost, and will the software work properly after release. Measurements have to be taken in software projects to improve this situation. It is of limited use to only collect metrics afterwards. The values of the relevant metrics have to be predicted, too. The predictions (i.e. estimates) form the basis for proper project management. One of the most painful problems in software projects is effort estimation. It has a clear and central effect on other project attributes like cost and schedule, and to product attributes like size and quality. Effort estimation can be used for several purposes. In this thesis only the effort estimation in software projects for project management purposes is discussed. There is a short introduction to the measurement issues, and some metrics relevantin estimation context are presented. Effort estimation methods are covered quite broadly. The main new contribution in this thesis is the new estimation model that has been created. It takes use of the basic concepts of Function Point Analysis, but avoids the problems and pitfalls found in the method. It is relativelyeasy to use and learn. Effort estimation accuracy has significantly improved after taking this model into use. A major innovation related to the new estimationmodel is the identified need for hierarchical software size measurement. The author of this thesis has developed a three level solution for the estimation model. All currently used size metrics are static in nature, but this new proposed metric is dynamic. It takes use of the increased understanding of the nature of the work as specification and design work proceeds. It thus 'grows up' along with software projects. The effort estimation model development is not possible without gathering and analyzing history data. However, there are many problems with data in software engineering. A major roadblock is the amount and quality of data available. This thesis shows some useful techniques that have been successful in gathering and analyzing the data needed. An estimation process is needed to ensure that methods are used in a proper way, estimates are stored, reported and analyzed properly, and they are used for project management activities. A higher mechanism called measurement framework is also introduced shortly. The purpose of the framework is to define and maintain a measurement or estimationprocess. Without a proper framework, the estimation capability of an organization declines. It requires effort even to maintain an achieved level of estimationaccuracy. Estimation results in several successive releases are analyzed. It isclearly seen that the new estimation model works and the estimation improvementactions have been successful. The calibration of the hierarchical model is a critical activity. An example is shown to shed more light on the calibration and the model itself. There are also remarks about the sensitivity of the model. Finally, an example of usage is shown.

Agile Methods in Small Software Projects

Agile software development methods are attempting to provide an answer to the software development industry's need of lighter weight, more agile processes that offer the possibility to react to changes during the software development process. The objective of this thesis is to analyze and experiment the possibility of using agile methods or practices also in small software projects, even in projects containing only one developer. In the practical part of the thesis a small software project was executed with some agile methods and practices that in the theoretical part of the thesis were found possible to be applied to the project. In the project a Bluetooth proxy application that is run in the S60 smartphone platform and PC was developed further to contain some new features. As a result it was found that certain agile practices can be useful even in the very small projects. The selection of the suitable practices depends on the project and the size of the project team.

Selected Aspects Related to Pre-development Stages of International Software projects. Case of Finland and Russia

The question of Pilot Project creation, due to support pre-development stage of software product elaboration, nowadays might be used as an approach, which allows improving the whole scheme of information technology project running. This subject is not new, but till now no model has been presented, which gives deep description of this important stage on the early phase of project. This Master's Thesis represents the research's results and findings concerning the pre-development study from the Software Engineering point of view. The aspects of feasibility study, pilot prototype developments are analyzed in this paper. As the result, the technique of Pilot Project is formulated and scheme has been presented. The experimental part is focused on particular area Pilot Project scheme's implementation- Internationally Distributed Software projects. The specific characteristic, aspects, obstacles, advantages and disadvantages are considered on the example of cross border region of Russia and Finland. The real case of Pilot Project technique implementation is given.

Business Process Modeling in Software Requirements Engineering for Small and Medium Software Projects

Vaatimusmäärittelyn tavoitteena on luoda halutun järjestelmän kokonaisen, yhtenäisen vaatimusluettelon vaatimusten määrittämiseksi käsitteellisellä tasolla. Liiketoimintaprosessien mallintaminen on varsin hyödyllinen vaatimusmäärittelyn varhaisissa vaiheissa. Tämä työ tutkii liiketoimintaprosessien mallintamista tietojärjestelmien kehittämistä varten. Nykyään on olemassa erilaisia liiketoimintaprosessien mallintamiseen tarkoitettuja tekniikoita. Tämä työ tarkastaa liiketoimintaprosessien mallintamisen periaatteet ja näkökohdat sekä eri mallinnustekniikoita. Uusi menetelmä, joka on suunniteltu erityisesti pienille ja keskisuurille ohjelmistoprojekteille, on kehitetty prosessinäkökohtien ja UML-kaavioiden perusteella.

Clean development mechanism and joint implementation in China and Russia as related to industrial energy projects

Being highly discussed the problem of climate change and global warming has been keeping importance for several of decades. As a response to the world’s need in solution for climate change disasters, the United Nations Framework Convention on Climate Change was adopted in 1992 and supplemented with the Kyoto protocol in 1997. This work is aimed to give better understanding of the Convention, Kyoto Protocol with its mechanisms and their function, related to energy projects in such case countries, as Russia and China, in order to assist evaluation of projects cost-effectiveness. It provides basic information about the Convention and the Protocol with their regulations, overview of present situation and future post-Kyoto forecasts, while the most attention is concentrated on the clean development mechanism and joint implementation step-by-step project cycles and specific regulations in given countries. The current study disclosed that CDM and JI project cycles are resulting in a complicated process. By the moment it requires step-by-step following of a number of methodologies, spending time and finance to particular project development. Uncertainties about post-Kyoto period bring additional risk to the projects and complicate any business decision concerning Kyoto Protocol.

Introducing Continuous Integration for C and C++ Software Development Projects on Linux Platform

Software integration is a stage in a software development process to assemble separate components to produce a single product. It is important to manage the risks involved and being able to integrate smoothly, because software cannot be released without integrating it first. Furthermore, it has been shown that the integration and testing phase can make up 40 % of the overall project costs. These issues can be mitigated by using a software engineering practice called continuous integration. This thesis work presents how continuous integration is introduced to the author's employer organisation. This includes studying how the continuous integration process works and creating the technical basis to start using the process on future projects. The implemented system supports software written in C and C++ programming languages on Linux platform, but the general concepts can be applied to any programming language and platform by selecting the appropriate tools. The results demonstrate in detail what issues need to be solved when the process is acquired in a corporate environment. Additionally, they provide an implementation and process description suitable to the organisation. The results show that continuous integration can reduce the risks involved in a software process and increase the quality of the product as well.

Project owner’s and outside engineering consultant’s role in power plant implementation projects

The purpose of this study was to investigate the nature of co-operation between a project owner and an outside engineering consultant in combined heat and power plant implementation projects. Moreover, as another focal subject of the study was to familiarize the purchasing behavior of the energy producer and how an outside engineering consultant participated into different stages of the purchasing process. The study was carried out as a multiple case study including altogether six Finnish power plant implementation projects that had been taken into commercial use during 1995 – 2015. By adjusting the findings of empirical interview data and comparing those to the theoretical framework concerning, among others, Finnish energy production, engineering consulting businesses, delivery methods of construction project and finally the purchasing process, it can be concluded that especially in the power plant implementation projects in the past have a great influence to decisions made during the project. The role of the main engineering consultant is to act as an assistant, who helps to achieve the project goals successfully rather than an advisor who only knows how the project should be conducted. At least in these five project cases this was the case, meaning that the final decision power always remaining with project owner.

Evaluating the success of software development projects in Russia, Ukraine, and Belarus

The size and complexity of projects in the software development are growing very fast. At the same time, the proportion of successful projects is still quite low according to the previous research. Although almost every project's team knows main areas of responsibility which would help to finish project on time and on budget, this knowledge is rarely used in practice. So it is important to evaluate the success of existing software development projects and to suggest a method for evaluating success chances which can be used in the software development projects. The main aim of this study is to evaluate the success of projects in the selected geographical region (Russia-Ukraine-Belarus). The second aim is to compare existing models of success prediction and to determine their strengths and weaknesses. Research was done as an empirical study. A survey with structured forms and theme-based interviews were used as the data collection methods. The information gathering was done in two stages. At the first stage, project manager or someone with similar responsibilities answered the questions over Internet. At the second stage, the participant was interviewed; his or her answers were discussed and refined. It made possible to get accurate information about each project and to avoid errors. It was found out that there are many problems in the software development projects. These problems are widely known and were discussed in literature many times. The research showed that most of the projects have problems with schedule, requirements, architecture, quality, and budget. Comparison of two models of success prediction presented that The Standish Group overestimates problems in project. At the same time, McConnell's model can help to identify problems in time and avoid troubles in future. A framework for evaluating success chances in distributed projects was suggested. The framework is similar to The Standish Group model but it was customized for distributed projects.

Coaching agile methods in research and development projects

Agile coaching of a project team is one way to aid learning of the agile methods. The objective of this thesis is to present the agile coaching plan and to follow how complying the plan affects to the project teams. Furthermore, the agile methods are followed how they work in the projects. Two projects are used to help the research. From the thesis point of view, the task for the first project is to coach the project team and two new coaches. The task for the second project is also to coach the project team, but this time so that one of the new coaches acts as the coach. The agile methods Scrum process and Extreme programming are utilized by the projects. In the latter, the test driven development, continuous integration and pair programming are concentrated more precisely. The results of the work are based on the observations from the projects and the analysis derived from the observations. The results are divided to the effects of the coaching and to functionality of the agile methods in the projects. Because of the small sample set, the results are directional. The presented plan, to coach the agile methods, needs developing, but the results of the functionality of the agile methods are encouraging.