41 resultados para project work
Resumo:
The management of port-related supply chains is challenging due to the complex and heterogeneous operations of the ports with several actors and processes. That is why the importance of information sharing is emphasised in the ports. However, the information exchange between different port-related actors is often cumbersome and it still involves a lot of manual work and paper. Major ports and port-related actors usually have advanced information systems in daily use but these systems are seldom interoperable with each other, which prevents economies of scale to be reached. Smaller ports and companies might not be equipped with electronic data transmission at all. This is the final report of the Mobile port (MOPO) project, which has sought ways to improve the management and control of port-related sea and inland traffic with the aid of ICT technologies. The project has studied port community systems (PCS) used worldwide, evaluated the suitability of a PCS for the Finnish port operating environment and created a pilot solution of a Finnish PCS in the port of HaminaKotka. Further, the dry port concept and its influences on the transportation system have been explored. The Mobile Port project comprised of several literature reviews, interviews of over 50 port-related logistics and/or ICT professionals, two different kinds of simulation models as well as designing and implementing of the pilot solution of the Finnish PCS. The results of these multiple studies are summarised in this report. Furthermore, recommendations for future actions and the topics for further studies are addressed in the report. The study revealed that the information sharing in a typical Finnish port-related supply chain contains several bottlenecks that cause delays in shipments and waste resources. The study showed that many of these bottlenecks could be solved by building a port community system for the Finnish port community. Almost 30 different kinds of potential services or service entities of a Finnish PCS were found out during the study. The basic requirements, structure, interfaces and operation model of the Finnish PCS were also defined in the study. On the basis of the results of the study, a pilot solution of the Finnish PCS was implemented in the port of HaminaKotka. The pilot solution includes a Portconnect portal for the Finnish port community system (available at https://www.portconnect.fi) and two pilot applications, which are a service for handling the information flows concerning the movements of railway wagons and a service for handling the information flows between Finnish ports and Finland-Russian border. The study also showed that port community systems can be used to improve the environmental aspects of logistics in two different ways: 1) PCSs can bring direct environmental benefits and 2) PCSs can be used as an environmental tool in a port community. On the basis of the study, the development of the Finnish port community system should be continued by surveying other potential applications for the Finnish PCS. It is also important to study if there is need and resources to extend the Finnish PCS to operate in several ports or even on a national level. In the long run, it could be reasonable to clarify whether there would be possibilities to connect the Finnish PCS as a part of Baltic Sea wide, European-wide or even worldwide maritime and port-related network in order to get the best benefit from the system
Resumo:
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.
Resumo:
In the 21st century, agile project management (APM) has emerged as a major evolutionary step in the area of software project management. APM is defined as a conceptual framework, consisting of various methods such as Scrum, quick respond to change, better customer collaboration, minimum coverage of documentation and extreme programming (XP) that facilitates to produce working software in multiple iterations with team work. Because agile project management has become more popular in the software industry in recent years, it constitutes an interesting and comprehensive research topic. This thesis presents a systematic literature review (SLR) of published research articles concerning agile project management. Based on a predefined search strategy, 273 such articles were identified, of which 44 were included in the review. The selected 44 articles were published between years 2005 and 2012. The thesis defines a review process by developing a review protocol and presenting the results of the review. The results are expected to provide researchers, software man
Resumo:
Presentation at Open Repositories 2014, Helsinki, Finland, June 9-13, 2014
Resumo:
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.
Resumo:
Process management refers to improving the key functions of a company. The main functions of the case company - project management, procurement, finance, and human resource - use their own separate systems. The case company is in the process of changing its software. Different functions will use the same system in the future. This software change causes changes in some of the company’s processes. Project cash flow forecasting process is one of the changing processes. Cash flow forecasting ensures the sufficiency of money and prepares for possible changes in the future. This will help to ensure the company’s viability. The purpose of the research is to describe a new project cash flow forecasting process. In addition, the aim is to analyze the impacts of the process change, with regard to the project control department’s workload and resources through the process measurement, and how the impacts take the department’s future operations into account. The research is based on process management. Processes, their descriptions, and the way the process management uses the information, are discussed in the theory part of this research. The theory part is based on literature and articles. Project cash flow and forecasting-related benefits are also discussed. After this, the project cash flow forecasting as-is and to-be processes are described by utilizing information, obtained from the theoretical part, as well as the know-how of the project control department’s personnel. Written descriptions and cross-functional flowcharts are used for descriptions. Process measurement is based on interviews with the personnel – mainly cost controllers and department managers. The process change and the integration of two processes will allow work time for other things, for example, analysis of costs. In addition to the quality of the cash flow information will improve compared to the as-is process. Analyzing the department’s other main processes, department’s roles, and their responsibilities should be checked and redesigned. This way, there will be an opportunity to achieve the best possible efficiency and cost savings.
Resumo:
The presentation consists of work-in-progress metrics of #digitalkoot, the crowdsourcing project launched by National Library of Finland
Resumo:
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.
Resumo:
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.
Resumo:
As unregistered grassroots charities do not appear in official statistics in China, they tend to remain unnoticed by scholars. Also as they operate unofficially and avoid publicity, their work is usually not reported by the media. In this research I explore the grassroots charity activity of one pop music fan club from the viewpoint of trust as a sociological concept. I will also establish the general situation on charity in China. By using textual analysis on internet blogs and discussion forums I map the charity project from the discussion of the original idea to the execution and follow up phase. I study the roles the fan club members assume during the project as anonymous participants of internet conversations, as well as concrete active charity volunteers outside of the virtual world. I establish parties, other than the fan club, which are involved in the charity project. Interviews with one of the participant of the project in 2010, 2014 and 2015 bring valuable additional information and help in distributing the questionnaire survey. A quantitative questionnaire survey was distributed among the fan club members to get more detailed information on the motives and attitudes towards official and unofficial charity in China. Because of the inequality in China, the rural minority areas do not have similar educational opportunities as the mostly majority inhabited urban areas, even though the country officially has a nine year compulsory education. Grassroots charities can operate in relative freedom taking some of the government’s burden of social responsibilities if they are not criticizing the authorities. The problem with grassroots charity seems to be lack of sustainability. The lack of trust for authorities and official charities was the reason why the Jane Zhang fan club decided to conduct a charity case unofficially. As a group of people previously unknown to each other, they managed to build mutual trust to carry out the project transparently and successfully, though not sustainably. The internet has provided a new and effective platform for unofficial grassroots charities, who choose not to co-operate with official organisations. On grassroots level charities can have the transparency and trust that lack from official charities. I suggest, that interviewing the real persons behind the internet aliases and finding out what happened outside the discussion forums, would bring a more detailed and outspoken description of the project concerning of the contacts with the local authorities. Also travelling to the site and communicating with the local people in the village would establish how they have experienced the project.
Resumo:
The research topic of the work is: “Factors of innovation creation within functionally heterogeneous project teams”. The research question is “What are the factors of innovation creation within functionally heterogeneous project teams?” The subject of this research is to explore the teams of projects, aimed at creating innovations, and understand how innovation is generated through project team work within them in term of factors. In line with the purposes of this study, firstly, it was analyzed what factors of such teams’ work are affecting creating innovation positively and negatively on the base of chosen literature and a preliminary conceptional framework was formulated, and secondly, the research of the work of project teams in one of the divisions of ABB company has been done and other factors and interdependencies between them have been added to the conceptional framework. This final conceptional framework constitutes the essense of the work findings and can be used as a tool to analyze the innovation creation process in functionally heterogeneous project teams