No abstract

This article presents the savings in time and costs achieved by a transition from sequential to simultaneous product realization. Such a transition is not possible without prior well-organized teamwork or virtual teamwork. The article demonstrates the team structure in simultaneous product realization. A two-level team structure is suitable for small companies, with a core team on the first level and several project teams in simultaneous product realization loops on the second level. In order to ensure successful work of the core team and several project teams, appropriate communication tools are suggested and a communication matrix has been developed, defining information exchange during the execution of activities in simultaneous product realization. The communication matrix is used for identifying information system connections. The results of organizing teamwork and virtual teamwork are shown on a case study of simultaneous realization of a pedal assembly.

In today’s highly dynamic and unpredictable project environment, companies need to be able to manage changes quickly and effectively, otherwise, the final product will not be current and will only go to waste. Traditional project management approaches that focus on planning are no longer efficient and companies are forced to adopt new ways of working. As a result, more flexible agile project management (APM) approaches have emerged over the last decades. Originally developed for the software industry, APM is now increasingly recognized and adopted also by other industry sectors. However, due to some discipline-specific differences, the adoption of APM by non-software companies is challenging and requires many adjustments and high financial input. While the larger organizations have sufficient resources to make such a transition, small and medium-sized enterprises (SMEs) generally cannot afford to do so, and therefore need alternative strategies to increase their agility and stay competitive on the global market. In this paper, we present a case study of a Slovenian medium-sized manufacturing company that implemented only certain APM practices separately and not as part of a structured APM methodology, and still managed to achieve significant benefits: improved communication, faster detection of discrepancies, more effective problem-solving and greater flexibility. The results also suggest that APM practices, even when implemented separately, positively impact project success in terms of both efficiency and stakeholder satisfaction, and can thus help in establishing an economically, socially, and environmentally more sustainable workplace.

No abstract

Today, it can be maintained that the customer is a 'king' as he will buy only the products that satisfy his needs and wants. The companies of today are facing new challenges: global business and local operation, standardization, and individualization of products, demanding customers and fierce competition. The company wants to achieve shorter product development time, lower costs, high quality of the product, and finally, customer satisfaction. In order to achieve the set goals, the company has to take into account the customers wants and needs during the new-product-development process. This article presents the mode of description of processes that allow recognition of suitable natural systems and their transformation into technical systems and a model for management of development process. The phases of quality functions deployment (QFD) during the new product development process along with the location for collecting customer needs and wants are presented. A detailed description is given on information resources for obtaining data on customer needs; the methods for obtaining, structuring, and evaluation of the data obtained. The results of testing the proposed methodology of taking into account the voice of the customer in the process of developing a new Vario Flow product in a company that produces and sells medical equipment in domestic and foreign markets are also included.

When entering the global market, companies encounter several difficulties, the most severe being long product development times and too high costs of sequential product and process development. In order to overcome this problem, the companies will have to make a shift from sequential product development (which is wasteful regarding time and costs) to a project-driven concurrent product development as soon as possible. The article presents a procedure for project-driven concurrent product development by taking into account three strategic management methods: parallelness, standardization, and integration of product development processes. Also presented are the changes in organizational concept of the company, organization of processes, organization of work and organization of IT, which are required for a transition from sequential to concurrent product development. Finally, an analysis is presented on concurrent product development teams in a company; this analysis is a prerequisite for a transition to a new method of product development.

Project management of product/service orders has become a mode of operation in many companies. Although these are mostly cyclically recurring projects, risk management is very important for them. An extended risk-analysis model for new product/service projects is presented in this paper. Emphasis is on a solution developed in the Faculty of Mechanical Engineering in Ljubljana, Slovenia. The usual project activities risk analysis is based on evaluation of the probability that risk events occur and on evaluation of their consequences. A third parameter has been added in our model: an estimate of the incidence of risk events. On the basis of the calculated activity risk level, a project team prepares preventive and corrective measures that should be taken according to the status indicators. An important advantage of the proposed solution is that the project manager and his team members are timely warned of risk events and they can thus activate the envisaged preventive and corrective measures as necessary.

Agile development became very popular at the beginning of the 21st century when the Manifesto for Agile Software Development was released. Since then, it has been predominant in the software industry and has been increasingly transferred to the development of physical products due to its great success. There are many studies on Agile-Stage-Gate hybrids that combine agile Scrum and the traditional Stage-Gate model, however no research has been found that addresses a direct integration of Scrum into a concurrent product development model in a similar way. In this paper, we therefore examine the possibility of introducing Scrum into the concurrent product development and propose a Scrum framework for an Agile-Concurrent hybrid. We propose that the framework for concurrent development remains unchanged: the stages overlap and the track-and-loop approach is preserved, while Scrum is proposed for the execution of day-to-day work. The main advantage of the proposed hybrid is that after each iteration the customer reviews the results of an entire loop, not just of one stage, which enables a broader understanding of the progress and facilitates a more extensive feedback. A quicker resolution of discrepancies, and a faster and more effective response to change is thus ensured. In the paper, the needed organizational changes and potential implementation issues are also discussed.