1 |
Understanding Required Capabilities of Leading Users in Hospital Information System Development ProjectChiao, Hsiu 26 August 2011 (has links)
In order to response to the demands resulted from environmental changes, hospital launches various information system development projects. Different from most information system development projects in the past, which are leaded by developers, the leaders of those projects are physicians or administrators. Unfortunately, the observed project failure rates are high. Since those projects are highly related to the operational performance of hospital, there is a needed to investigate into this issue in depth. Among those factors contribute to high failure rates, one very important cause is that many project leaders are lacking of adequate capabilities. This study adopted case study approach. After interview the leaders, members, and developers of three projects, critical capabilities that project leader should possess are identified. I concluded that those non-IT background project leaders should possess at least five basic capabilities, including knowledge, project management ability, interpersonal skills, ability to distribute resources, and flexible capacity. I also identified their priority based on project characteristics. The results can serve as reference for project leader selection in hospital and basis for future studies in this area.
|
2 |
Identification of Owner’s Project Value InterestsGunby, Molly Gaynell 2010 December 1900 (has links)
Identifying the unique ways in which a project can add value to an owner’s organization
is an essential part of project delivery. Every project has defined requirements, such as
budget, schedule and engineering specifications that must be met; but there are other
attributes of a project that are not always immediately evident; yet, when implemented,
can add significant value. A delivered project that meets cost, schedule, engineering and
operational requirements is not necessarily a project that provides the most value
possible. To maximize the value of a project, it is first necessary to identify the ways in
which it can add value. Only after that can an effective strategy be developed to exploit
fully the value-adding potential of a project. However, because these value adding
attributes, or value interests, are not always driven by operational or engineering
requirements, they can be difficult to identify. Identification begins with understanding
what aspect of a project drives the value interests. Since a single owner may engage in
different types of projects and the value set of one may not be the value set of another, it
is logical then to conclude it is characteristics of the project itself, not the owner, that
drive the presence of value interest. It is this hypothesis, that project characteristics
drive value interests, which is presented and validated in this thesis. The hypothesis is supported through the development of a mathematical model in which the parameter
estimates show specific project characteristics are significant in explaining the
importance of individual value interests to a project. The model was developed through
binary logistic regression of industry survey data, and validated statistically and
empirically. A sensitivity analysis showed the key cost- and schedule-related value
interests are not significantly sensitive, and an examination of the parameter estimates
showed realistic and common sense relationships are present. The methodology
presented here shows that value interests are, indeed, driven by project characteristics.
However, there is neither a single characteristic nor a standard set of characteristics that
drive all value interests. Instead, each value interest has its own unique combination of
driving characteristics.
|
3 |
Enterprise system implementation projects : a study of the impact of contextual factors on critical success factorsVan Scoter, Diane J. 24 October 2011 (has links)
Critical success factors (CSFs) are those things that must be done correctly for a project to be successful; however, CSFs are not sufficient by themselves to guarantee success. CSFs, as identified in the literature, vary from study to study. In addition, previous studies have not typically included contextual details for the projects studied. As a result, it is difficult to know how the particulars of a project impact (or not) CSFs. Researchers have suggested that CSFs can be affected by contextual details. Knowledge about the effect of contextual factors on CSFs would allow organizational leaders and project managers to more effectively use resources to achieve project success.
Enterprise system implementation projects have exhibited high failure rates. Both Enterprise Resource Planning (ERP) and Electronic Health Record (EHR) system
implementations have proven to be challenging for organizations. For enterprise system implementation projects, a variety of contextual factors may be important. Examples of contextual factors include the number of software modules implemented, the number of sites undergoing implementation, the geographic dispersion of the sites, the number of people in the organization, and the percentage of personnel in the organization whose daily tasks are disrupted by the new enterprise system.
This research was designed to shed light on the role of contextual factors on CSFs for enterprise system implementation projects. A survey was created to evaluate the effects of contextual factors on CSF ratings. The survey included questions related to 17 CSFs, 14 of the CSFs included in the study have been well-cited in the project management literature. Three additional CSFs were also included in the study to capture important elements of change management, which more recent studies have shown to be relevant to enterprise system implementations. The survey included questions related to eight contextual variables for ERP projects and 11 contextual variables for EHR system projects.
The research focused on small to medium-size organizations, which have been less studied than larger organizations. The target respondents for the survey were enterprise system (ERP or EHR) project managers from software companies or consulting firms and government project managers whose implementation projects were within six months
of completion. Data were collected on 17 ERP projects and 26 EHR system implementation projects in 43 different organizations.
The survey data and subsequent analyses provided evidence that EHR system implementation projects are impacted by contextual factors. The results for the ERP implementations are not conclusive. The results suggest that contextual factors should be taken into consideration when determining how best to manage enterprise system implementations. In addition, the results of this research did not support previous research findings, which indicated that similar CSFs exist for ERP and EHR system projects. CSFs were found to vary substantially in a number of key areas, especially with respect to training. The User Training and Support CSF for the ERP projects included in this study was rated less important than prior research results suggest (Finney & Corbett, 2007). One of two CSFs included in the survey to capture change management requirements, Early Adopter/Super-user, was found to be an important CSF for the ERP projects included in this study.
The EHR system projects were found to be affected by contextual factors, with nine different instances of significant relationships identified between individual CSFs and one or more contextual factor. Eight of the 17 CSFs for the EHR system implementation projects in this study were affected by contextual factors. Contextual factors impacted the ERP and EHR system implementations quite differently, suggesting that more research is needed to better understand the phenomenon leading to these differences.
The findings from this research can be used by organizational leaders and project managers to more effectively achieve project success. These results provide project managers and organizational leaders in small and medium-size organizations with a much deeper and relevant understanding of the factors that are most important to manage in successfully implementing either ERP or EHR system projects. As this study focused on small and medium-size organizations and both ERP and EHR system implementation projects, the findings are relevant across a wide range of organizations. As smaller organizations have not typically been the focus of CSF research, this study makes an important contribution to the understanding of CSFs for both ERP and EHR system implementation projects.
More generally, this research also expands the broader body of knowledge on the identification of CSFs, as this study has provided empirical evidence for the important role played by contextual factors. Every project is carried out within a broader organizational setting. This broader organizational setting appears, based on the results of this study, to have a strong effect on the importance of CSFs for each specific project and as such, may explain some of the seemingly contradictory findings related to CSFs in the existing literature. While further research is needed to understand the means by which contextual factors impact CSFs, this study has provided a significant contribution in validating the relationship between contextual factors and CSFs for a broad range of enterprise system projects in a wide range of industries. / Graduation date: 2012
|
4 |
Factors Affecting the Inter-orginizational Collaborative Team Process and Team Performance / 影響跨組織合作團隊績效之研究郭芳瑜, Kuo, Fang-Yu Unknown Date (has links)
The goal of this dissertation was to explore the key factors and managerial mechanisms that influence performance of inter-organizational collaborative teams. Specifically, this research addressed five key constructs: inter-organizational collaboration relationships, project characteristics, team process, managerial mechanisms, and team performance of inter-organizational collaborative teams.
Data for this study was collected via semi-structured interviews within two stages. In the first stage, interviews were done with the executives, focusing on the inter-organizational relationships, managerial mechanisms and the performance of the inter-organizational collaborative team from strategic perspectives. The next stage involved with interviews with the team members to collect the information regarding team process more thoroughly.
The results suggested that (1) Inter-organizational relationships positively affect the inter-organizational team process. (2) Project Characteristics also play a role in the team process of inter-organizational collaboration. (3) Inter-organizational team process have positively influence on the performance of inter-organizational collaborative teams. (4) Managerial mechanisms, such as mutual learning, and organizational culture, also have influences on the team process and team performance of inter-organizational collaborative teams. However, we had few findings about the team incentives program or any other formal mechanisms that promote the team process and team performance.
|
5 |
軟體專案特性對專案管理與專案間互動的影響之研究-以趨勢科技之雲端運算專案為例 / Software project characteristics on project management and project the impact of interaction study:the case of Trend Micro Inc.陳彥甫 Unknown Date (has links)
隨著商業環境的快速變動,企業為因應市場快速變化,管理階層傾向於將專案規模縮小、目標明確來定義專案的範圍,以助於專案的執行,因此企業大多會執行一個以上的專案,然而專案彼此之間或多或少都會有些關聯與互動,良好的互動關係對於專案執行成效與企業均有其正面助益,因此本研究的目的在探討軟體專案特性對專案管理與專案間互動的影響之研究。
本研究以全球防毒軟體領導廠商-趨勢科技為例,其獨特的企業文化和指標性的企業管理模式,皆已成為國際型企業的典範。因此探討該公司運用雲端運算技術所成立的兩個專案進行研究,藉以探討專案特性、專案管理、專案間互動之關係。本研究經由個案訪談以及次級資料的分析探討,本研究之發現如下:
1.企業在執行軟體專案管理時,充分授權有助於激進式創新專案的開發進行。
2.領導者在軟體專案管理各階段所扮演的角色不同。當技術為外部來源時,領導者需要扮演協調溝通角色;當技術為內部來源時,領導者需要扮演技術支援角色。
3.企業在執行軟體專案管理時,會用師徒制來進行隱性知識的傳承;並利用文件管理系統來管理外顯知識。
4.當激進式創新的產品開發專案運用外部技術來源時,提供員工自我學習的空間,並透過知識分享討論會、知識管理系統、非正式溝通的多個群體協調活動,有助於專案間互動。 / In order to adapt to rapidly changing markets, cooperate managers tend to downsize the scales and define specific goals of projects for effective execution. Therefore, cooperates simultaneously deal with multiple projects which are inter-connected to each other. Good interactions benefit both projects and cooperate itself. Hence, the objective of this study is to investigate how the characteristics of software projects influence the managements and interactions of projects.
The study subject is Trend Macro Incorporated, the world-wide leading company of antivirus software. Its unique culture and foremost management style have become the model example of international companies. Therefore, this study investigated two projects of this company, which apply cloud computing, to explore the relationships of the characteristics, management and interactions within and between projects. By case interview and secondary databases, the main findings of this study are listed below.
1.Enterprise in the implementation of software project management, the fully authorized to contribute to the development of radical innovation projects carried out.
2.Leader in software project management role of the different stages. When the technology to external sources, the leaders need to play the role of coordination and communication. When the technology for internal sources, leaders need to play a technical support role.
3.Enterprise in the implementation of software project management, we will use the apprenticeship system to carry out transmission of tacit knowledge; and to use document management system to manage explicit knowledge.
4.When the radical innovation of the product development project the use of external technology sources, to provide space for staff self-learning and knowledge sharing through seminars, knowledge management systems, informal communication between the various groups of coordination activities to facilitate interaction between projects.
|
6 |
Styrning i vägprojekt: Med fokus på förutsättningar och risker : En kvalitativ flerfallsstudie inom Trafikverket / Managing road projects: focusing on conditions and risks : A qualitative multi-case study within TrafikverketJohnsson, Julia, Olin, Anna January 2020 (has links)
Bakgrund och problem: Projekt präglas vanligtvis av en otillräcklig måluppfyllelse, exempelvis gällande tid, kostnad och kvalitet. Detta går även att finna vid anläggnings- och infrastrukturprojekt, vilka dessutom är betydande för samhällets möjligheter för kommunikation och transport. Att infrastrukturprojekt, vilka bedrivs av den offentliga verksamheten Trafikverket, inte uppnår sina mål resulterar i förseningar och att skattepengar inte nyttjas maximalt. Detta tyder även på att projekten är svårstyrda utifrån de föränderliga förutsättningar och risker som präglar projekttypen, vilket gör det relevant att studera ämnet vidare. Syfte: Syftet med studien är att öka kunskapen om hur styrningen går tillväga vid vägprojekt med fokus på förutsättningar och risker. Detta utförs genom att beskriva hur Trafikverkets process styrs i vägprojekt och identifiera samt analysera förutsättningar och risker som kan påverka projekten. Metod: Studien är en kvalitativ flerfallsstudie inom Trafikverket. Det teoretiska materialet har erhållits från vetenskapliga artiklar, litteratur och rapporter. Det empiriska materialet är insamlat genom ett snöbollsurval där åtta respondenter inkluderades. Totalt genomfördes elva semistrukturerade intervjuer. Webbsidor och dokument är också en del av det empiriskt insamlade materialet. Vid genomförandet av studien har vi utgått ifrån forskningsetiska överväganden och kvalitetskriterier, i syfte att öka dess pålitlighet, trovärdighet, konfirmering och överförbarhet. Slutsats: Studien konstaterar att vägprojekt styrs utifrån en version av stage-gate-modellen och att det även finns inslag av den agila metoden angående riskhanteringen. Styrtriangelns tre dimensioner tid, kostnad och kvalitet utgör ett fokus inom vägprojekt, dimensionen kvalitet beskrivs däremot som innehåll. Förutom att styrtriangeln består av ett inre beroende finns även en yttre påverkan gentemot andra projekt. Detta innebär att ett projekts styrtriangel har en inverkan på ett annat projekts dimensioner, vilket är ett teoretiskt bidrag som studien belyst. Det identifierades även totalt åtta förutsättningar, sex risker och åtta faktorer som betraktas vara både förutsättningar och risker inom vägprojekt. Samtliga av dessa förutsättningar och risker styrs samt hanteras. Det redogörs för att dessa påverkar varandra, vilket styrningen av dem bör ta hänsyn till. Sammantaget fastställs det att styrningen av vägprojekt är komplext på grund av dessa samband och uppkomsten av oförutsägbara händelser. Detta bidrar till en praktisk och teoretisk kunskap angående styrningen med hänsyn till förutsättningar och risker eftersom dessa har studerats i samband med varandra. / Background and problem: Projects are usually characterized by insufficient goal fulfillment, regarding time, cost and quality for example. This can also be found in construction and infrastructure projects, which are important for society's opportunities for communication and transport. The fact that infrastructure projects, which are carried out by the public authority Trafikverket, do not achieve their goals, results in delays and that tax money is not used to the maximum. This also indicates that the projects are difficult to manage on the basis of the changing conditions and risks that characterize the project type, which makes it relevant to study the subject further. Purpose: The purpose of the study is to increase the knowledge of how management is used in road projects with a focus on conditions and risks. This is accomplished by describing how Trafikverkets process is managed in road projects and identifying and analyzing conditions and risks that can affect the projects. Method: The study is a qualitative multi-case study within Trafikverket. The theoretical material has been obtained from scientific articles, literature and reports. The empirical material was collected through a snowball selection in which eight respondents were included. In total, eleven semi-structured interviews were conducted. Web pages and documents are also part of the empirically collected material. In conducting the study, we included research ethical considerations and quality criteria, with the aim of increasing its reliability, credibility, confirmation and transferability. Conclusion: The study finds that road projects are managed based on a version of the stage-gate model and that there are also elements of the agile method regarding risk management. The three dimensions in the iron triangle time, cost and quality are a focus within road projects, but the quality dimension is described as content. In addition to the iron triangle consisting of an internal dependency, there is also an external influence on other projects. This means that one project's control triangle has an impact on another project's dimensions, which is a theoretical contribution that the study illustrated. A total of eight conditions, six risks and eight factors were also identified, which are considered to be both conditions and risks in road projects. All of these conditions and risks are managed. It is stated that these affect each other, which their management should take into account. Overall, it is determined that the management of road projects is complex due to these relationships and the occurrence of unpredictable events. This contributes to a practical and theoretical knowledge of the management with regard to the conditions and risks as these have been studied in conjunction with each other.
|
Page generated in 0.1137 seconds