916 resultados para ICT Project Portfolio Management
Resumo:
Työn tavoitteena oli kuvata projektihallintaa tutkimusympäristössä ja kartoittaa siihen liittyviä erityisominaisuuksia, ongelmia ja kehittämistarpeita. Projektihallinnan kehittämistarpeita tarkasteltiin erityisesti projektipäällikön näkökulmasta. Yliopiston yksikköjä varten kehitettiin projektien hallintaa systematisoiva toimintamalli, joka perustuu projektin elinkaaren vaiheiden tunnistamiseen. Mallissa esitettiin projektin eri vaiheisiin kuuluvat johtamistehtävät. Tehtävien määrittelemiseksi tutustuttiin kirjallisuudessa esiteltävään projektihallinnan teoriaan, ja tehtävien määrittelyä täydennettiin yliopiston tutkimustoiminnan omilla erityisvaatimuksilla.Projektin tehtävien suorittamisen helpottamiseksi selvitettiin projektihallinnan menetelmiä, jotka soveltuvat parhaiten tutkimusprojektien hallintaan. Tärkeimmiksi koetut menetelmät kuvattiin tarkemmin. Esiteltyjen menetelmien avulla sekä projektin operatiivista että strategista johtamista voidaan parantaa. Menetelmien avulla myös projektin sisäistä tiedonvaihtoa voidaan tehostaa ja tiedottamista ulkopuolisille sidosryhmille yhdenmukaistaa.
Resumo:
Tutkimuksen tarkoituksena on tietohallinnon projektiportfolion hallinnan kehittäminen Metropolia ammattikorkeakoulussa. Portfolion hallinta kattaa projektiesitysten luomisen, projektien ja projektiesitysten arvioinnin ja priorisoinnin sekä projektien käynnistämisen. Painopisteenä arvioinnin ja priorisoinnin lisäksi on portfolion tarkastelu yhtenä kokonaisuutena. Tutkimus toteutettiin konstruktiivisena tutkimuksena, yhteistyössä Metropolia ammattikorkeakoulun kanssa. Tutkimusmenetelminä käytettiin kirjallisuuskatsausta, strukturoituahaastattelua ja kyselylomaketta. Kirjallisuuskatsaus kohdennettiin portfolion hallinnan prosessiin, siinä käytettäviin menetelmiin sekä projektien arviointikriteereihin. Metropoliassa tehtyjen haastattelujen ja kirjallisten kyselyjen avulla selvitettiin portfolion hallinnan nykytilannetta ja kehittämiskohteita. Haastattelemalla kahta julkishallinnon organisaatiota kartoitettiin portfolion hallinnan parhaita käytäntöjä. Tutkimuksen tuloksena on Metropolian tietohallinnon portfolion hallintaprosessi sekä sitä tukevat menetelmät ja projektien arviointikriteerit. Näiden avulla portfolio voidaan priorisoida yhtenäisesti ja systemaattisesti, huomioiden portfolion hallinnan tärkeimmät näkökulmat. Tutkimuksen tulokset ovat hyödynnettävissä Metropolian muissa yksiköissä tai vastaavanlaisissa organisaatioissa
Resumo:
Teknologisen edistyksellisyyden merkitys tuotteiden myynnille ja yrityksen menestykselle on viime vuosikymmenten kuluessa kasvanut huomattavasti. Tämän johdosta on myös mielenkiinto tutkimus- ja kehitystoimintaa (T&K-toimintaa) sekä sen johtamista kohtaan lisääntynyt huomattavasti. Tässä työssä tarkastellaan T&K-portfolion johtamisprosessissa käytettäviä menetelmiä sekä näiden soveltamista T&K-portfolion johtamisprosessin eri vaiheissa. Eri menetelmät ja niiden eri luokitteluja esitellään yleisellä tasolla sekä esitellään niiden käyttöä ja soveltuvuutta projektien valintaan, portfolion seurantaan ja yksittäisen projektin etenemisen seurantaan. Erilaisia T&K-portfolion johtamiseen käytettäviä menetelmiä ja työkaluja havaittiin olevan huomattava määrä. Menetelmien suuresta määrästä johtuen ei ole tarkoituksen mukaista pyrkiä käyttämään niitä kaikkia vaan pyrkiä löytämään kuhunkin tilanteeseen parhaiten soveltuvat menetelmät.
Resumo:
Coordenação de Aperfeiçoamento de Pessoal de Nível Superior (CAPES)
Resumo:
All’interno di questo elaborato di tesi verrà proposto un Modello di Valutazione e Selezione delle Iniziative commerciali, costruito nel corso dell’esperienza di stage presso la società Astaldi. Nella parte iniziale del lavoro, verranno presentati dei concetti teorici che costituiscono il presupposto e la base per la costruzione del Modello. Il background di riferimento è quello di un’azienda che lavora nel mondo delle costruzioni, sviluppando progetti complessi a livello internazionale. Nel primo capitolo, dopo una breve introduzione sul Project Management, si prenderà in esame l’ambiente multiproject, un ambiente nel quale gran parte delle aziende si trova ad operare e nel quale opera anche l’Astaldi. Successivamente, partendo da queste considerazioni legate all’ambiente multi-progetto, verranno descritte le potenzialità ed i vantaggi di un approccio Project Portfolio Management, come evoluzione naturale del Project Management. Nell’ambito del Project Portfolio Management, verrà analizzata l’importanza del processo di selezione dei progetti per la costruzione del portafoglio e le relative tecniche di selezione. Nel secondo capitolo verranno presentate le Misure e gli Indicatori di performance definiti in letteratura. Verranno anche introdotti dei possibili Indicatori di Valutazione, la cui misurazione è particolarmente legata al Project Life Cycle: questi verranno fatti propri all’interno del Modello presentato che darà come output, proprio un Indicatore di Valutazione ex-ante del progetto. Nel terzo capitolo verrà illustrata la società Astaldi al fine di comprendere il più possibile il contesto in cui e per cui si è costruito tale Modello. Nel quarto ed ultimo capitolo sarà analizzato il Modello stesso, descrivendo le modalità con cui è stato realizzato, le modalità operative per la sua applicazione ed alcuni esempi esplicativi del suo utilizzo.
Resumo:
Early project termination is one of the most difficult decisions to be made by Research and Development managers. While there is the risk of terminating good projects, there is also the opposite risk of not terminating bad projects and overspend resources in unproductive research. Criteria used for identifying these projects are common subject of research in Business Administration. In addition, companies might take important lessons from its interrupted projects that could improve their overall portfolio technical and commercial success. Finally, the set and weight of criteria, as well as the procedures companies use for achieve learning from cancelled projects may vary depending on the project type. This research intends to contribute to the understanding of policies applied to projects that were once considered attractive, but by some reason is not appreciated anymore. The research addressed the question: How companies deal with projects that become unattractive? More specifically, this research tried to answer the following questions: (1) Are projects killed or (otherwise) they die naturally by lack of resources? (2) What criteria are used to terminate projects during development? (3) How companies learn from the terminated projects to improve the overall portfolio performance? (4) Are the criteria and learning procedures different for different types of projects? In order to answer these questions, we performed a multiple case study with four companies that are reference in business administration and innovation: (1) Oxiteno, considered the base case, (2) Natura, the literal replication, (3) Mahle and (4) AES, the theoretical replications. The case studies were performed using a semi-structured protocol for interviews, which were recorded and analyzed for comparison. We found that the criteria companies use for selecting projects for termination are very similar to those anticipated by the literature, except for a criteria related to compliance. We have evidences to confirm that the set of criteria is not altered when dealing with different project types, however the weight they are applied indeed varies. We also found that learning with cancelled projects is yet very incipient, with very few structured formal procedures being described for capturing learning with early-terminated projects. However, we could observe that these procedures are more common when dealing with projects labeled as innovative, risky, big and costly, while those smaller and cheaper derivative projects aren\'t subject of a complete investigation on the learning they brought to the company. For these, the most common learning route is the informal, where the project team learns and passes the knowledge though interpersonal information exchange. We explain that as a matter of cost versus benefit of spending time to deeply investigate projects with little potential to bring new knowledge to the project team and the organization
Resumo:
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.
Resumo:
This study aims at enhancing understanding and deriving new constructs about the management of intellectual capital in the early phases of project marketing. The research methodology employed is deductive; conceptual reasoning is based on existing literature. The study's knowledge base is drawn from the bodies of literature dealing with project, relationship, and industrial marketing, as well as from the literature dealing with mechanical engineering, network approach, systems selling, R&D, project portfolio, strategic, financial, and knowledge management. As a result, three processes, 32 summaries and 19 conclusions give to the management of intellectual capital meaning in the context of project marketing. These conclusions and synthesis are proposed to improve the existing concepts and models in project marketing.
Resumo:
Liiketoiminnan organisoiminen projekteiksi on erittäin yleistä nykyisin. Suuri osa projekteista erityisesti IT-alalla epäonnistuu kuitenkin saavuttamaan tavoitteensa. Projektin menestys on tyypillisesti mitattu budjetin, aikataulun, laadun ja sidosryhmien tyytyväisyyden perusteella. Tämän Pro Gradu -tutkielman tarkoituksena on etsiä tyypillisimpiä syitä projektien epäonnistumiseen ja löytää projektien seurannan ja mittaamisen avulla keinoja näiden epäonnistumisten ehkäisemiseen. Tutkimusmenetelmänä on laadullinen tapaustutkimus. Empiirinen aineisto on kerätty haastattelujen, eri materiaalien analysoinnin ja havainnoinnin avulla. Teoriaosuus tarjoaa kattavan yhteenvedon projektiliiketoiminnan ja yksittäisten projektien johtamiseen sekä projektien seurantaan ja mittaamiseen aikaisemman kirjallisuuden perusteella. Empiirisessä osiossa suoritetaan analyysi Case -yrityksen projektien seurantaan ja valittuihin projekteihin. Analyysien, haastattelujen ja havainnoinnin pohjalta tehdään johtopäätökset tyypillisimmistä, ongelmia projekteissa aiheuttavista tekijöistä sekä näiden esiintymisestä projektin elinkaaren eri vaiheissa. Mahdolliset ongelmia ehkäisevät keinot esitetään myös. Ehdotuksia kehityskohteiksi esitetään lopuksi teorian ja empirian pohjalta.
Resumo:
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
Resumo:
Tämän tutkielman tavoitteena on tutkia kuinka roadmapping-tekniikkaa voidaan käyttää tarjonnan suunnittelun tukena uusien tuotteiden valmistamisen yhteydessä. Työ koostuu teoreettisesta ja käytännönläheisestä osasta. Teoreettinen runko on luotu selventämään kuinka tämän hetkisen tutkimus- ja kehitys projektit lopulta muodostavat tulevaisuuden tarjoaman. Menestyksekkään tuotetarjoaman luominen vaatii, sekä uusien teknologioiden kehittämistä, että markkinoilla olevien asiakkaiden tarpeiden ymmärtämistä. Asiakassuuntaisten tuotteiden kehittäminen vaatii toimintaympäristöstä ja asiakasrajapinnasta tulevien signaalien tunnistamista ja niiden ohjaamista tuote- ja teknologia platformeille. Strategia luodaan tukemaan päätöksentekoa prosessin eri vaiheissa. Yrityskohtainen osio koostuu analyysistä, joka on tehty teetetyn kyselyn ja haas-tattelujen pohjalta. Osana analyysia ovat Major project-yksikön tämänhetkinen tarjonnansuunnitteluprosessi, strategian soveltaminen, informaation kerääminen ja priorisointi, portfolionhallinta ja roadmap-tekniikan käyttö. Ratkaisussa on esitet-ty tarjonnan suunnitteluprosessi ja siihen liittyvät kriittiset komponentit. Roadmapping-tekniikkaaon luotu yhdistämään toimintaympäristö, tuotteet ja teknologia toisiinsa. Toimintaympäristö ja tuotteet on yhdistetty myös linked-grids-tekniikan avulla.
Resumo:
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.
Resumo:
The portfolio as a means of demonstrating personal skills has lately been gaining prominence among technology students. This is partially due to the introduction of electronic portfolios, or e-portfolios. As platforms for e-portfolio management with different approaches have been introduced, the learning cycle, traditional portfolio pedagogy, and learner centricity have sometimes been forgotten, and as a result, the tools have been used for the most part as data depositories. The purpose of this thesis is to show how the construction of e-portfolios of IT students can be supported by institutions through the usage of different tools that relate to study advising, teaching, and learning. The construction process is presented as a cycle based on learning theories. Actions related to the various phases of the e-portfolio construction process are supported by the implementation of software applications. To maximize learner-centricity and minimize the intervention of the institution, the evaluated and controlled actions for these practices can be separated from the e-portfolios, leaving the construction of the e-portfolio to students. The main contributions of this thesis are the implemented applications, which can be considered to support the e-portfolio construction by assisting in planning, organizing, and reflecting activities. Eventually, this supports the students in their construction of better and more extensive e-portfolios. The implemented tools include 1) JobSkillSearcher to help students’ recognition of the demands of the ICT industry regarding skills, 2) WebTUTOR to support students’ personal study planning, 3) Learning Styles to determine students' learning styles, and 4) MyPeerReview to provide a platform on which to carry out anonymous peer review processes in courses. The most visible outcome concerning the e-portfolio is its representation, meaning that one can use it to demonstrate personal achievements at the time of seeking a job and gaining employment. Testing the tools and the selected open-source e-portfolio application indicates that the degree of richness of e-portfolio content can be increased by using the implemented applications.
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.