Standardization of project management processes

Software development is a discipline that is almost as old as the history of computers. With the advent of the Internet and all of its related technologies, software development has been on high demand. But, and especially in SME (small and medium enterprise), this was not accompanied with a comparable effort to develop a set of sustainable and standardized activities of project management, which lead to increasing inefficiencies and costs. Given the actual economic situation, it makes sense to engage in an effort to reduce said inefficiencies and rising costs. For that end, this work will analyze the current state of software development’s project management processes on a Portuguese SME, along with its problems and inefficiencies in an effort to create a standardized model to manage software development, with special attention given to critical success factors in an agile software development environment, while using the best practices in process modeling. This work also aims to create guidelines to correctly integrate these changes in the existing IS structure of a company.

An essay on agile project management practices

The main goals for the current dissertation is to research on how practices and concepts from Agile Project Management can be applied in a non-IT context and to discover which aspects should be considered when deciding if whether an Agile approach should be implemented or not. Previous studies reflect on the adoption for the identified context. However, the recognition of these practices and concepts by the Project Management field of studies still remains unresolved. The adoption of Agile Project Management emerges as a manifestation against traditional approaches, mainly due to their inability of accepting requirements’ changes. Therefore, these practices and concepts can be considered in order to reduce the risks concerning the increase of competition and innovation – which does not apply to the IT sector solely. The current study reviews the literature on Agile Project Management and its adoption across different sectors in order to assess which practices and concepts can be applied on a non-IT context. Nine different methods are reviewed, where two of these show a higher relevance – Scrum and Extreme Programming. The identified practices and concepts can be separated into four different groups: Cultural and Organizational Structures, Process, Practices, and Artefacts. A framework based on the work by Boehm & Turner in 2004 is developed in order to support the decision of adopting agile methods. A survey intended for project managers was carried in order to assess the implementation of the identified practices and concepts and to evaluate which variables have the highest importance on the developed decision support framework. It is concluded that New Product Development is the project type with the highest potential to implement an agile approach and that the Project Final Product’s Innovativeness, Competitiveness, and the Project Member’s Experience and Autonomy are the most important aspects to consider an implementation of an Agile approach.

Soil Nitrogen and Carbon Management Project, 2002

Report produced by Iowa Departmment of Agriculture and Land Stewardship

Project controlling and risk management in German machine and plant engineering industry

Tutkielman tavoitteena on määritellä projektikontrolloinnin ja - riskijohtamisen roolit ja toiminnot saksalaisissa kone- ja tehdassuunnitteluteollisuusyrityksissä. Tämä on kvalitatiivinen tutkielma, jossa käytetään voimakkaasti kuvailevia metodeita. Materiaali tutkimuksen empiiriseen osaan kerättiin kyselykaavakkeen avulla. Kyselykaavakkeiden tulokset käsiteltiin Microsoft Office Access- ohjelmalla ja analysoitiin Microsoft Office Excel- ohjelmalla ja Pivot table- työkalun avulla. Tutkimustulokset osoittavat, että asianmukaisessa projektikontrollointi- ja riskijohtamismetodien käytössä ja käyttötiheydessä esiintyy puutteita saksalaisissa kone- ja tehdassuunnitteluteollisuusyrityksissä. Tehostamalla ja keskittymällä enemmän projektikontrollointi- ja riskijohtamismetodeihin ja prosesseihin sekä projektien että yritysten suorituskyky paranisi.

Factors of customer project profitability in an engineering industrial enterprise

The purpose of the study is to find factors affecting projects' profitability in project business. The issue is approached from customer profitability and project management point of view. The study has been made for a big Finnish company acting in a global market place. The research method is quantitative. Research hypotheses are based on the literature. The used database is originated from the company's ERP- (enterprise resource planning) and project financial follow-up —system. The findings of the study supported the hypotheses weakly. Obviously profitability fluctuated depending on a customer and a project manager. The reasons could not be justified with the variables used in the research.

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.

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.