Entrepreneurship in project management systems: proposal of a model and preliminary empirical evidence

This study analyzes the manifestation of the dimensions of Entrepreneurial Orientation (EO) and Project Management Systems (PMS). We used a qualitative approach to conduct exploratory research through a study in literature and a pilot case in a software company. Data was collected from semi structured interviews, documents, and records on file, then triangulated and treated with content analysis. The model proposed for the relationship between the types of PMS (ad hoc, Classic PM, innovation, entrepreneurship/intrapreneurship) and the dimensions of EO (innovativeness, risk-taking, proactiveness, competitive aggressiveness, and autonomy), was partially corroborated by empirical studies. New studies are suggested to validate the applicability and setup of the model.

COMP1205 Student Presentations U-X

Thursday 15th May Building 02A Room 2077, 15.00-16.45 Elena & Rikki Presenting: Groups: U, V, W, X Marking Groups: A, B, C, D Schedule and Topics 15.00-15.05: Introduction and protocol for the session 15.05-15.25 Group U: Digital Literacies 15.25-15.45 Group V: Will MOOCs destroy face-to-face University Education? 15.45-16.05 Group W: Groupwork and leadership skills in MMORPGs 16.05-16.25 Group X: Tools and techniques for agile project management 16.25-16.45: Wash-up: feedback session for presentation groups

Evaluación, instalación y configuración de herramientas de gestión de proyectos de desarrollo de software

Actualmente existen multitud de aplicaciones creadas para la gestión de proyectos software; cada una de ellas pretende dar solución y facilitar las tareas propias de los gestores y los desarrolladores pertenecientes a los equipos de desarrollo. Los equipos de desarrollo software suelen estar integrados por gran variedad de recursos, tanto humanos como materiales. Cada uno desempeña una función concreta en el proyecto, pudiendo no tener una dedicación plena al proyecto. Por eso, es necesario que dichos recursos sean compartidos entre la cartera proyectos existentes. Para resolver este planteamiento en las aplicaciones de gestión de proyectos, ha sido requisito fundamental que se puedan gestionar varios proyectos de forma simultánea (gestión multiproyecto), pudiendo repartir la dedicación de los recursos entre los proyectos existentes en la cartera. En la actualidad, existe un gran número de metodologías de gestión de proyectos, por lo que, en parte, el éxito del proyecto radica en la elección de la más adecuada. Entre todas las metodologías existentes, este estudio se ha centrado en las cada vez más utilizadas metodologías de gestión de proyectos ágiles; se describe en qué consisten, qué beneficios aportan frente a las metodologías clásicas y cuáles son las más utilizadas por sus ya contrastados beneficios y el valor que aportan a la gestión de proyectos. Por lo descrito anteriormente, otro requisito fundamental a la hora de valorar las aplicaciones de gestión de proyectos ha sido la capacidad de soportar y aplicar metodologías ágiles de gestión de proyectos. En este estudio también se ha tenido en cuenta el tipo de aplicación atendiendo a su instalación y acceso, y se ha realizado la diferenciación entre aplicaciones web- las cuales precisan ser instaladas en un servidor web y son accesibles desde cualquier dispositivo con navegador -, y aplicaciones de escritorio - las cuales precisan estar instaladas en un equipo de forma local y sólo pueden ser accedidas a ellas desde dicho equipo. En este estudio se han evaluado varias aplicaciones, intentando analizar el cumplimiento de las características comentadas anteriormente, dando como resultado tres aplicaciones seleccionadas siendo éstas las que pueden aportar más valor a la hora de gestionar una cartera de proyectos. ABSTRACT. At present, there are many applications aimed at managing software projects. Every application intends to solve and facilitate tasks to managers and developers belonging to the development teams. Software development teams are usually made up of many different human and material resources, each of them developing a specific task in the project and sometimes without a full dedication to the project. Therefore, these resources have to be shared within the existing project portfolio. To meet this need in project management applications, the main requirement is to be able to manage several projects simultaneously (multi-project management), thus allowing resources to be shared within the existing project portfolio. At present, there are a large number of project management methodologies and the success of the project lies in choosing the most appropriate one. Among all the existing methodologies, this study has focused on the increasingly used agile project management methodologies. The study describes the way they work, their added value in comparison traditional methodologies, and which ones are more often used due to their already verified benefits and value in managing projects. Taking into account the above-mention characteristics, another key requirement when assessing the project management applications has been their capacity to support and implement project management agile methodologies. This study has also taken into account the type of application according to its installation and access. A difference is established between web applications – which require to be installed in a web server and are accessible from any device with a web browser – and desktop applications, which must be installed in the equipment to be used and are only accessible from this equipment. The study has assessed several applications by analyzing the compliance with the above-mentioned characteristics and has chosen three applications that provide the management of the project portfolio with an added value.

Analisi dei principali vantaggi e barriere nell'applicazione di metodologie Agili nella gestione dei progetti all'interno del contesto manifatturiero.

Negli ultimi anni la forte evoluzione tecnologica ha avuto un impatto significativo su un ampio numero di settori ed in particolar modo sull’industria manifatturiera, specie in quelle aziende che hanno saputo cogliere le opportunità di business che essa ha generato. La forte dinamicità dei requisiti con cui si sono trovati a fare i conti gli sviluppatori software, ha portato alla stesura, poco più di vent’anni fa’, dell’oramai noto "Manifesto per lo Sviluppo Agile di Software" all’interno del quale sono introdotti i principi cardini che in un secondo momento hanno contribuito alla formazione dell’approccio Agile. Questa occasione ha senza dubbio cambiato radicalmente l’ottica con cui era sempre stato visto, almeno fino a quel momento, il classico processo utilizzato per concepire e successivamente sviluppare il codice: costituito da una sequenza di fasi predefinite, dove l’insieme dei requisiti era definito nella sua interezza, prima della fase di effettiva implementazione. Il metodo di lavoro più "tradizionale" non rappresenta un approccio sbagliato o inefficace ma è una modalità che si prestava bene ad essere impiegata in scenari dove il concetto di business assumeva connotati diversi rispetto a quello degli ultimi anni, caratterizzati da un’elevata incertezza, repentini cambiamenti e alta probabilità di dover ridefinire i requisiti, al contrario i cambiamenti avvenivano con una scarsa frequenza e per questo risultavano facilmente gestibili. La presente attività di tesi si propone di analizzare i maggiori vantaggi e le principali criticità, che l’impiego di metodologie Agile devono affrontare all’interno di un contesto manifatturiero ed in particolare in un caso di studio reale: un’iniziativa progettuale per la realizzazione di distinte di servizio e istruzioni di montaggio e smontaggio elettroniche all’interno dell’organizzazione Bonfiglioli S.P.A., una multinazionale leader nella produzione e nella vendita di riduttori e motoriduttori.

Agile CRM System Implementation Project

The application of information technology (IT) in customer relationship management (CRM) is growing rapidly as many companies implement CRM systems to support their numerous customer facing activities. However, failure rates of CRM projects remain notably high as they deliver scant solutions and poor user acceptance. As a consequence, it is justified to study previously researched CRM success factors and apply them to CRM system implementation. The aim of this master’s thesis was to get acquainted with relevant academic theories, frameworks and practices concerning CRM and agile development, and use them to generate a modified CRM project strategy to support the successful execution of the case company’s, Process Vision Oy, CRM implementation project. The empirical CRM system implementation project was conducted simultaneously with writing this thesis. Its theoretical findings could be transferred into practice through active participation in the CRM system development and deployment work. The project’s main goal was to produce and take into use a functioning CRM system. The goal was met, since at the time of printing this thesis the first system release was successfully published to its users at Process Vision’s marketing and sales departments. The key success elements in the CRM project were cyclic, iterative system development, customer oriented approach, user inclusion and flexible project management. Implying agile development practices ensured being able to quickly respond to changes arising during the progress of the CRM project. Throughout modelling of the core sales process formed a strong basis, on which the CRM system’s operational and analytical functionalities were built. End users were included in the initial specification of system requirements and they provided feedback on the system’s usage. To conclude, the chosen theoretical CRM roadmaps and agile development practices proved as beneficial in the successful planning and execution of the agile CRM system implementation project at Process Vision.

Management of interdependency in project portfolio

Project management has evolved in recent decades. Project portfolio management, together with multi project management, is an emerging area in the project management field in practice, and correspondingly in academic research and forums. In multi project management, projects cannot be handled isolated from each other, as they often have interdependencies that have to be taken into account. If the interdependencies between projects are evaluated during the selection process, the success rate of the project portfolio is increased. Interdependencies can be human resources, technological, and/or market based. Despite of the fact that interdependency as a phenomenon has roots in the 1960s and is related to famous management theories, it has not been much studied, although in practice most companies use it to great extent. There exists some research on interdependency, but prior publications have not emphasized the phenomenon per se, because a practical orientation practitioner techniques prevails in the literature. This research applies the method triangulation, electronic surveys and multiple case study. The research concentrates on small to large companies in Estonia and Finland, mainly in construction, engineering, ICT, and machinery industries. The literature review reveals that interdependencies are deeply involved in R&D and innovation. Survey analysis shows that companies are aware of interdependency issues in general, but they i have lack of detailed knowledge to use it thoroughly. Empirical evidence also indicates that interdependency techniques influence the success rate and other efficiency aspects to different extents. There are a lot of similarities in interdependency related managerial issues in companies of varying sizes and countries in Northern Europe. Differences found in the study are for instance the fact that smaller companies face more difficulties in implementing and evaluating interdependency procedures. Country differences between Estonia and Finland stem from working solutions to manage interdependencies on a daily basis.historical and cultural reasons, such as the special features of a transition country compared to a mature country. An overview of the dominant problems, best practices, and commonly used techniques associated with interdependency is provided in the study. Empirical findings show that many interdependency techniques are not used in practice. A multiple case study was performed in the study to find out how interdependencies are managed in real life on a daily basis. The results show that interdependencies are mostly managed in an informal manner. A description of managing the interdependencies and implementation procedures is given. Interdependency procedures are hard to implement, especially in smaller companies. Companies have difficulties in implementing interdependency procedures and evaluating them. The study contains detailed results on how companies have implemented working solutions to manage interdependencies on a daily basis

Towards increased productivity and quality in software development using agile, lean and collaborative approaches

Dagens programvaruindustri står inför alltmer komplicerade utmaningar i en värld där programvara är nästan allstädes närvarande i våra dagliga liv. Konsumenten vill ha produkter som är pålitliga, innovativa och rika i funktionalitet, men samtidigt också förmånliga. Utmaningen för oss inom IT-industrin är att skapa mer komplexa, innovativa lösningar till en lägre kostnad. Detta är en av orsakerna till att processförbättring som forskningsområde inte har minskat i betydelse. IT-proffs ställer sig frågan: “Hur håller vi våra löften till våra kunder, samtidigt som vi minimerar vår risk och ökar vår kvalitet och produktivitet?” Inom processförbättringsområdet finns det olika tillvägagångssätt. Traditionella processförbättringsmetoder för programvara som CMMI och SPICE fokuserar på kvalitets- och riskaspekten hos förbättringsprocessen. Mer lättviktiga metoder som t.ex. lättrörliga metoder (agile methods) och Lean-metoder fokuserar på att hålla löften och förbättra produktiviteten genom att minimera slöseri inom utvecklingsprocessen. Forskningen som presenteras i denna avhandling utfördes med ett specifikt mål framför ögonen: att förbättra kostnadseffektiviteten i arbetsmetoderna utan att kompromissa med kvaliteten. Den utmaningen attackerades från tre olika vinklar. För det första förbättras arbetsmetoderna genom att man introducerar lättrörliga metoder. För det andra bibehålls kvaliteten genom att man använder mätmetoder på produktnivå. För det tredje förbättras kunskapsspridningen inom stora företag genom metoder som sätter samarbete i centrum. Rörelsen bakom lättrörliga arbetsmetoder växte fram under 90-talet som en reaktion på de orealistiska krav som den tidigare förhärskande vattenfallsmetoden ställde på IT-branschen. Programutveckling är en kreativ process och skiljer sig från annan industri i det att den största delen av det dagliga arbetet går ut på att skapa något nytt som inte har funnits tidigare. Varje programutvecklare måste vara expert på sitt område och använder en stor del av sin arbetsdag till att skapa lösningar på problem som hon aldrig tidigare har löst. Trots att detta har varit ett välkänt faktum redan i många decennier, styrs ändå många programvaruprojekt som om de vore produktionslinjer i fabriker. Ett av målen för rörelsen bakom lättrörliga metoder är att lyfta fram just denna diskrepans mellan programutvecklingens innersta natur och sättet på vilket programvaruprojekt styrs. Lättrörliga arbetsmetoder har visat sig fungera väl i de sammanhang de skapades för, dvs. små, samlokaliserade team som jobbar i nära samarbete med en engagerad kund. I andra sammanhang, och speciellt i stora, geografiskt utspridda företag, är det mera utmanande att införa lättrörliga metoder. Vi har nalkats utmaningen genom att införa lättrörliga metoder med hjälp av pilotprojekt. Detta har två klara fördelar. För det första kan man inkrementellt samla kunskap om metoderna och deras samverkan med sammanhanget i fråga. På så sätt kan man lättare utveckla och anpassa metoderna till de specifika krav som sammanhanget ställer. För det andra kan man lättare överbrygga motstånd mot förändring genom att introducera kulturella förändringar varsamt och genom att målgruppen får direkt förstahandskontakt med de nya metoderna. Relevanta mätmetoder för produkter kan hjälpa programvaruutvecklingsteam att förbättra sina arbetsmetoder. När det gäller team som jobbar med lättrörliga och Lean-metoder kan en bra uppsättning mätmetoder vara avgörande för beslutsfattandet när man prioriterar listan över uppgifter som ska göras. Vårt fokus har legat på att stöda lättrörliga och Lean-team med interna produktmätmetoder för beslutsstöd gällande så kallad omfaktorering, dvs. kontinuerlig kvalitetsförbättring av programmets kod och design. Det kan vara svårt att ta ett beslut att omfaktorera, speciellt för lättrörliga och Lean-team, eftersom de förväntas kunna rättfärdiga sina prioriteter i termer av affärsvärde. Vi föreslår ett sätt att mäta designkvaliteten hos system som har utvecklats med hjälp av det så kallade modelldrivna paradigmet. Vi konstruerar även ett sätt att integrera denna mätmetod i lättrörliga och Lean-arbetsmetoder. En viktig del av alla processförbättringsinitiativ är att sprida kunskap om den nya programvaruprocessen. Detta gäller oavsett hurdan process man försöker introducera – vare sig processen är plandriven eller lättrörlig. Vi föreslår att metoder som baserar sig på samarbete när processen skapas och vidareutvecklas är ett bra sätt att stöda kunskapsspridning på. Vi ger en översikt över författarverktyg för processer på marknaden med det förslaget i åtanke.

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.

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.

Adaptive project planning and management based on best practices - COBRA system

Planning a project with proper considerations of all necessary factors and managing a project to ensure its successful implementation will face a lot of challenges. Initial stage in planning a project for bidding a project is costly, time consuming and usually with poor accuracy on cost and effort predictions. On the other hand, detailed information for previous projects may be buried in piles of archived documents which can be increasingly difficult to learn from the previous experiences. Project portfolio has been brought into this field aiming to improve the information sharing and management among different projects. However, the amount of information that could be shared is still limited to generic information. This paper, we report a recently developed software system COBRA to automatically generate a project plan with effort estimation of time and cost based on data collected from previous completed projects. To maximise the data sharing and management among different projects, we proposed a method of using product based planning from PRINCE2 methodology. (Automated Project Information Sharing and Management System -�COBRA) Keywords: project management, product based planning, best practice, PRINCE2

Investigating the effect of construction management strategies on project greenhouse gas emissions using interactive simulation

The challenges posed by global climate change are motivating the investigation of strategies that can reduce the life cycle greenhouse gas (GHG) emissions of products and processes. While new construction materials and technologies have received significant attention, there has been limited emphasis on understanding how construction processes can be best managed to reduce GHG emissions. Unexpected disruptive events tend to adversely impact construction costs and delay project completion. They also tend to increase project GHG emissions. The objective of this paper is to investigate ways in which project GHG emissions can be reduced by appropriate management of disruptive events. First, an empirical analysis of construction data from a specific highway construction project is used to illustrate the impact of unexpected schedule delays in increasing project GHG emissions. Next, a simulation based methodology is described to assess the effectiveness of alternative project management strategies in reducing GHG emissions. The contribution of this paper is that it explicitly considers projects emissions, in addition to cost and project duration, in developing project management strategies. Practical application of the method discussed in this paper will help construction firms reduce their project emissions through strategic project management, and without significant investment in new technology. In effect, this paper lays the foundation for best practices in construction management that will optimize project cost and duration, while minimizing GHG emissions.

BIM-lean synergies in the management on MEP works in public facilities of intensive use – a case study

21st Annual Conference of the International Group for Lean Construction – IGLC 21 – Fortaleza, Brazil

A Multi-Project Scheduling Procedure for Transportation Projects, Part II, HR-339, 1994

The Iowa Department of Transportation (IDOT) has been requiring Critical Path Method (CPM) schedules on some larger or more schedule sensitive projects. The Office of Construction's expectations for enhanced project control and improved communication of project objectives have not been fully met by the use of CPM. Recognizing that the current procedures might not be adequate for all projects, IDOT sponsored a research project to explore the state-of-the-art in transportation scheduling and identify opportunities for improvement. The first phase of this project identified a technique known as the Linear Scheduling Method (LSM) as an alternative to CPM on certain highway construction projects. LSM graphically displays the construction process with respect to the location and the time in which each activity occurs. The current phase of this project was implemented to allow the research team the opportunity to evaluate LSM on all small groups of diverse projects. Unlike the first phase of the project, the research team was closely involved in the project from early in the planning phase throughout the completion of the projects. The research strongly suggests that the linear scheduling technique has great potential as a project management tool for both contractors and IDOT personnel. However, before this technique can become a viable weapon in the project management arsenal, a software application needs to be developed. This application should bring to linear scheduling a degree of functionality as rich and as comprehensive as that found in microcomputer based CPM software on the market today. The research team recommends that the IDOT extend this research effort to include the development of a linear scheduling application.