MVD Quarterly Report on Building Project, 2nd Quarter, FY06

A quarterly report from the Iowa Department of Transportation regarding building project status.

Motor Vehicle Division Quarterly Report on Building Project 3rd Quarter, FY 06

A quarterly report from the Iowa Department of Transportation regarding the Motor Vehicle Division building project status.

MVD Quarterly Report on Building Project, 4th Quarter, FY06

A quarterly report from the Iowa Department of Transportation regarding building project status.

MVD Quarterly Report on Building Project, 1st Quarter, FY07

A quarterly report from the Iowa Department of Transportation regarding building project status.

Progress of the Building Project for the Motor Vehicle Division, 2006

Pursuant to Section 1 of House File 466 of the 81st General Assembly, the Iowa Department of Transportation (DOT) is required to make quarterly reports to the Legislative Council regarding the progress of the building project for the Motor Vehicle Division. Progress of the Building Project for the Motor Vehicle Division. A report to the Iowa Legislature, per Section 1 of House File 466 of the 81st General Assembly.

MVD Quarterly Report on Building Project quarter ending March 31, 2007

Pursuant to Section 1 of House File 466 of the 81st General Assembly, the Iowa Department of Transportation (DOT) is required to make quarterly reports to the Legislative Council regarding the progress of the building project for the Motor Vehicle Division and to inform the General Assembly of any significant delays or unanticipated expenditures. During the quarter ending March 31, 2007, the project progressed as planned. The project is on schedule and no unanticipated expenditures have been made.

Quarterly Report of the Building Project for the Motor Vehicle Division

Pursuant to Section 1 of House File 466 of the 81st General Assembly, the Iowa Department of Transportation is required to make quarterly reports to the Legislative Council regarding the progress of the building project for the Motor Vehicle Division. During the quarter ending June 30, 2007, the project was delayed by two weeks. The Motor Vehicle Division moved into the new Ankeny facility on June 22 and was operational Monday, June 25. The driver's license stations reopened as scheduled Tuesday, June 26, at the Ankeny facility as well as the Oliver Plaza renewal location.

Building Environmental Management System for Laboratory Products Manufacturing Company according ISO 14001-standard

Tutkielman tavoitteena on rakentaa toimiva ympäristöjärjestelmä Thermo Fisher Scientific Oy:lle. Tutkimuksen tarkoituksena on myös löytää kahdelle täysin erilaiselle toiminnalle yhtenäinen ympäristöjärjestelmä, jonka avulla pystytään ottamaan huomioon molempien toimipaikkojen hieman erilaiset vaatimukset. Lisäksi tavoitteena on muodostaa ympäristöjärjestelmälle oma organisaatio, jonka avulla ympäristöjärjestelmän integrointi yrityksen prosesseihin voidaan suorittaa sujuvasti. Aluksi tutkimusongelmaa lähestytään teoreettisesta näkökulmasta,jossa tarkastellaan ympäristöjärjestelmän historiaa, rakennetta, etuja sekä ISO 14001–standardin rakennetta ja sen etenemistä ympäristöjärjestelmän rakentamisen yhteydessä aina kolmannen osapuolen sertifiointiin asti. Empiria osa alkaa alustavalla ympäristökatselmuksella, jossa selvitetään ympäristöasioiden hoidon nykytaso ja luodaan pohja koko ympäristöjärjestelmän luomiselle, jonka vankimpana perustana on ympäristöpolitiikka. Johdon hyväksymä ympäristöpolitiikka varmistaa johdon sitoutumisen järjestelmään. Ympäristöjärjestelmän toimintarakenteen muodostaminen kahdelle erilaiselle toiminnalle onnistui tutkimuksessa kiitettävästi. Se miten ympäristöjärjestelmä toimii todellisuudessa, tullaan näkemään käytännön kokemuksien yhteydessä.

Product Development Management. Experiment for New Type of Project Management.

Tuotekehityksestä ja sen johtamisesta on tullut erittäin tärkeä osa tietoliikenneteollisuutta. Jatkuva teknologinen kehitys ja lyhentyneet tuotteiden elinkaaret ovat saaneet yritykset panostamaan tuotekehitysprosesseihin ja johtamiseen. Erityisesti nopeatempoiset ja lyhytkestoiset projektit onkin koettu ongelmallisiksi. Diplomityön tavoitteena oli tutkia teoriassa uusien tuotteiden tuotekehitystä, tuotekehitysprosesseja sekä projektijohtamista. Käytännön osuudessa oli tavoitteena kehittää kokeellinen tuotekehitysmalli nopeatempoisten ja lyhytkestoisten tuotekehitysprojektien tarpeisiin muuttuvissa ja epävarmoissa olosuhteissa. Tavoitteena oli myös käyttää ja analysoida kehitettyä kokeellista tuotekehitysmallia lyhytkestoisen tuotekehitysprojektin yhteydessä. Työn tuloksena saatiin ohjelmistotuote vaadituilla ominaisuuksilla vaaditussa ajassa ja todettiin projektissa käytetyn kokeellisen tuotekehitysmallin osoittautuneen toimivaksi. Jatkotutkimuksia tarvitaan selvittämään mallin sopivuutta ja sen kehityskohteita erilaisten tuotekehitysprojektien kohdalla.

Enhancement of R&D project management system

Stora Enso has research centres in Finland, Sweden and Germany. The research centres use PIMS as a research project invoicing and monitoring system. Possible reorganization and new financing model for R&D functions have been considered and the project management system should be developed to support the new operation model. The objective of this thesis is to find a model for R&D project management, and to present the project management system of Stora Enso, and to discuss if the current system could be developed to respond to the new needs or should it be replaced with another system. The theoretical part of the study describes challenges in R&D project management, and presents different project characteristics, and methods for managing R&D project portfolio. It is also described how the project management system can support project monitoring and controlling, and how inter-project learning can be enhanced. The empirical part of the study presents the current project management system of Stora Enso and how the system should be developed to support Stora Enso’s R&D functions better. In conclusion, it is stated that there is no relevant reason to replace PIMS with another system, because PIMS can be developed to support R&D project management better with a hybrid system. It is also suggested that the new financing model should not be implemented before more comprehensive analysis of its effects is conducted.

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.

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 Management Tools in Agile Embedded Systems Development

Agile methods have become increasingly popular in the field of software engineering. While agile methods are now generally considered applicable to software projects of many different kinds, they have not been widely adopted in embedded systems development. This is partly due to the natural constraints that are present in embedded systems development (e.g. hardware–software interdependencies) that challenge the utilization of agile values, principles and practices. The research in agile embedded systems development has been very limited, and this thesis tackles an even less researched theme related to it: the suitability of different project management tools in agile embedded systems development. The thesis covers the basic aspects of many different agile tool types from physical tools, such as task boards and cards, to web-based agile tools that offer all-round solutions for application lifecycle management. In addition to these two extremities, there is also a wide range of lighter agile tools that focus on the core agile practices, such as backlog management. Also other non-agile tools, such as bug trackers, can be used to support agile development, for instance, with plug-ins. To investigate the special tool requirements in agile embedded development, the author observed tool related issues and solutions in a case study involving three different companies operating in the field of embedded systems development. All three companies had a distinct situation in the beginning of the case and thus the tool solutions varied from a backlog spreadsheet built from scratch to plug-in development for an already existing agile software tool. Detailed reports are presented of all three tool cases. Based on the knowledge gathered from agile tools and the case study experiences, it is concluded that there are tool related issues in the pilot phase, such as backlog management and user motivation. These can be overcome in various ways epending on the type of a team in question. Finally, five principles are formed to give guidelines for tool selection and usage in agile embedded systems development.

Operational Flexibility: A Model for Effective Project Management

The aim of this study is to investigate the role of operational flexibility for effective project management in the construction industry. The specific objectives are to: a) Identify the determinants of operational flexibility potential in construction project management b) Investigate the contribution of each of the determinants to operational flexibility potential in the construction industry c) Investigate on the moderating factors of operational flexibility potential in a construction project environment d) Investigate whether moderated operational flexibility potential mediates the path between predictors and effective construction project management e) Develop and test a conceptual model of achieving operational flexibility for effective project management The purpose of this study is to findout ways to utilize flexibility inorder to manage uncertain project environment and ultimately achieve effective project management. In what configuration these operational flexibility determinants are demanded by construction project environment in order to achieve project success. This research was conducted in three phases, namely: (i) exploratory phase (ii) questionnaire development phase; and (iii) data collection and analysis phase. The study needs firm level analysis and therefore real estate developers who are members of CREDAI, Kerala Chapter were considered. This study provides a framework on the functioning of operational flexibility, offering guidance to researchers and practitioners for discovering means to gain operational flexibility in construction firms. The findings provide an empirical understanding on kinds of resources and capabilities a construction firm must accumulate to respond flexibly to the changing project environment offering practitioners insights into practices that build firms operational flexibility potential. Firms are dealing with complex, continuous changing and uncertain environments due trends of globalization, technical changes and innovations and changes in the customers’ needs and expectations. To cope with the increasingly uncertain and quickly changing environment firms strive for flexibility. To achieve the level of flexibility that adds value to the customers, firms should look to flexibility from a day to day operational perspective. Each dimension of operational flexibility is derived from competences and capabilities. In this thesis only the influence on customer satisfaction and learning exploitation of flexibility dimensions which directly add value in the customers eyes are studied to answer the followingresearch questions: “What is the impact of operational flexibility on customer satisfaction?.” What are the predictors of operational flexibility in construction industry? .These questions can only be answered after answering the questions like “Why do firms need operational flexibility?” and “how can firms achieve operational flexibility?” in the context of the construction industry. The need for construction firms to be flexible, via the effective utilization of organizational resources and capabilities for improved responsiveness, is important because of the increasing rate of changes in the business environment within which they operate. Achieving operational flexibility is also important because it has a significant correlation with a project effectiveness and hence a firm’s turnover. It is essential for academics and practitioners to recognize that the attainment of operational flexibility involves different types namely: (i) Modification (ii) new product development and (iii) demand management requires different configurations of predictors (i.e., resources, capabilities and strategies). Construction firms should consider these relationships and implement appropriate management practices for developing and configuring the right kind of resources, capabilities and strategies towards achieving different operational flexibility types.