Topic
Project stakeholder
About: Project stakeholder is a research topic. Over the lifetime, 3317 publications have been published within this topic receiving 110056 citations. The topic is also known as: Project stakeholder.
Papers published on a yearly basis
Papers
More filters
TL;DR: In this paper, a comprehensive literature review is given, analysis and synthesis of most interesting material is made, and applicable practical guidelines are defined, and a special accent on present situation in context of project management in Croatia.
102 citations
TL;DR: The Project Management Maturity Model (ProMMM) as discussed by the authors is a benchmarking framework for measuring project management capability in any type of industry, including those responsible for facilities management projects.
Abstract: Many businesses recognise project management as a core competence and seek to deliver benefits to the business through effective management of projects. But how can an organisation know whether its project management processes are adequate? Can a business compare itself with best practice or its competitors? Is there an accepted benchmark for organisational project management capability? The Project Management Maturity Model (ProMMM) has been developed to meet these needs. It describes four levels of increasing project management capability (Naive, Novice, Normalised and Natural), with each ProMMM level further defined in terms of four attributes, namely culture, process, experience and application. It presents a generic benchmarking framework applicable to project‐based organisations in any type of industry, including those responsible for facilities management projects, and does not presume any prior level of project management capability. ProMMM allows organisations to assess their project management capability against agreed criteria, set realistic targets for improvement, and measure progress towards enhanced capability. This paper outlines the structure of the ProMMM framework, and presents a case study where ProMMM has been used to support development of effective project management.
101 citations
TL;DR: Examination of the mindset of software development project managers in regard to how they ‘define’ a successful project in order to arrive at a richer perspective of ‘success’ from the perspective of project managers suggests delivering a system that meets customer/user requirements and works as intended through work that provides a sense quality and personal achievement are important aspects that lead to a project being considered a success.
101 citations
TL;DR: In this article, the authors examine the relationships between safety leaderships of project owners, contractors and subcontractors and discover leadership dimensions which significantly impact construction safety performance, and establish clear leadership impacting paths from owners to site supervisors of subcontractors in construction projects.
100 citations
02 Dec 1996
TL;DR: Endeavors' solution architecture achieves its goals and design strategies through application of five key design strategies by maintaining multiple object model layers and implementing the architecture as a set of highly componentized, lightweight, transportable, concurrent elements.
Abstract: As software projects evolve, possibly differing in size, complexity, scope and purpose, the development processes that support the project must evolve to reflect these changes. For a distributed project, maintaining proper communications, coordinating between project stakeholders, and maintaining managerial control become increasingly important and, unfortunately, increasingly difficult. The Endeavors system is an open, distributed process modeling and execution infrastructure that addresses communication, coordination, and control issues. Complex processes may require: (a) distribution of people and processes; event based and intermediate format integration of external tools; a low entry barrier through ease of use and incremental adoption; ability to customize and reuse objects, tools, and policies; and dynamic change of runtime processes, objects, and behaviors. Endeavors' solution architecture achieves these goals through application of five key design strategies: (1) maintaining multiple object model layers; (2) implementing the architecture as a set of highly componentized, lightweight, transportable, concurrent elements; (3) providing customization capabilities for each layer of the object model; (4) using a reflexive object model to support dynamic change; and (5) allowing dynamic loading and changing of objects including loading of executable handlers, new object types, and extensions. We discuss these goals and design strategies, describe the architecture, and describe the current status of the project and its relevance to its own development.
100 citations