Working capital management in the small and medium-sized enterprises Case: Project-based business environment in Flowrox Oy

This Master´s thesis illustrates how growing a business ties up the company´s working capital and what the cost of committed capital. In order to manage a company´s working capital in rapid business growth phase, the thesis suggests that by monitoring and managing the operating and cash conversion cycles of customers´ projects, a company can find ways to secure the required amount of capital. The research method of this thesis was based on literature reviews and case study research. The theoretical review presents the concepts of working capital and provides the background for understanding how to improve working capital management. The company in subject is a global small and medium-sized enterprise that manufactures pumps and valves for demanding process conditions. The company is expanding, which creates lots of challenges. This thesis concentrates to the company´s working capital management and its efficiency through the supply chain and value chain perspective. The main elements of working capital management are inventory management, accounts receivable management and accounts payable management. Prepayments also play a significant role, particularly in project-based businesses. Developing companies´ working capital management requires knowledge from different kind of key operations´ in the company, like purchasing, production, sales, logistics and financing. The perspective to develop and describe working capital management is an operational. After literature reviews the thesis present pilot projects that formed the basis of a model to monitor working capital in the case company. Based on analysis and pilot projects, the thesis introduces a rough model for monitoring capital commitments in short time period. With the model the company can more efficiently monitor and manage their customer projects.

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.

Innovation Project Portfolio Management

Companies today are forced to innovate in order to remain within business. Such innovation projects undertaken by the companies are defined in this study as creative ideas which have been managed through “Stage-Gate” innovation process. This process is used to manage innovation projects as they proceed from being newly created to ready for launching/implementing. This has ensured that the companies manage the innovation project right. However, with so many new creative ideas the companies can come up within limited resources, the companies must rely on Innovation Project Portfolio Management (IPPM) to ensure that they are managing only the right innovation projects. Although, there are many tools and techniques available for use within Project Portfolio Management, there is still no consensus on which are the most effective and no standard framework has been established especially for IPPM. Thus, this study proposes a practical framework for which individual innovative organization can follow as a guideline to manage its innovation project portfolio. The study theoretically first addresses the key differences between project portfolio management of innovation projects and other traditional projects - one of which is the stage nature of innovation projects due to their unclear objectives from the beginning compare to clearly established objectives of traditional projects. Secondly, different tools and techniques which can be used are examined based on the three goals of IPPM: (1) Maximizing the Value of Innovation Project Portfolio: Financial Methods, Decision Trees, Scoring Models and Checklists; (2) Balancing Innovation Project Portfolio: Visual Representations; and (3) Aligning Innovation Project Portfolio with Strategy: Bottom-Up (Scoring Models with Strategic Criteria) and Top-Down (Strategic Buckets). Finally, the two approaches in which IPPM can be integrated with Stage-Gate innovation process are discussed: (1) Gates- Dominated; and (2) Portfolio Reviews-Dominated. Practically, this study investigates IPPM of a case organization, and through analysis of the case study results proposes a practical framework for case organization to improve its current management of innovation project portfolio. This framework is then generalized to propose a final practical framework or guideline for which an innovative organization can follow to manage its innovation project portfolio.

Teaching project: a low-cost swine model for chest tube insertion training

Objective: to describe and evaluate the acceptance of a low-cost chest tube insertion porcine model in a medical education project in the southwest of Paraná, Brazil. Methods: we developed a low-cost and low technology porcine model for teaching chest tube insertion and used it in a teaching project. Medical trainees - students and residents - received theoretical instructions about the procedure and performed thoracic drainage in this porcine model. After performing the procedure, the participants filled a feedback questionnaire about the proposed experimental model. This study presents the model and analyzes the questionnaire responses. Results: seventy-nine medical trainees used and evaluated the model. The anatomical correlation between the porcine model and human anatomy was considered high and averaged 8.1±1.0 among trainees. All study participants approved the low-cost porcine model for chest tube insertion. Conclusion: the presented low-cost porcine model for chest tube insertion training was feasible and had good acceptability among trainees. This model has potential use as a teaching tool in medical education.

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.