Senin, 24 Oktober 2011
Principle 3: Ensure separation of stakeholder management and project decision making activities
07.59 |
Diposting oleh
Unknown
The decision making effectiveness of a committee can be thought of as being inversely proportional to its size. Not only can large committees fail to make timely decisions, those it does make are often ill considered because of the particular group dynamics at play.
As project decision making forums grow in size, they tend to morph into stakeholder management groups. When numbers increase, the detailed understanding of each attendee of the critical project issues reduces. Many of those present attend not to make decisions but as a way of finding out what is happening on the project. Not only is there insufficient time for each person to make their point, but those with the most valid input must compete for time and influence with those with only a peripheral involvement in the project. Further not all present will have the same level of understanding of the issues and so time is wasted bringing everyone up to speed on the particular issues being discussed. Hence, to all intents and purposes, large project committees are constituted more as a stakeholder management forum than a project decision making forum. This is a major issue when the project is depending upon the committee to make timely decisions.
There is no question that both activities, project decision making and stakeholder management, are essential to the success of the project. The issue is that they are two separate activities and need to be treated as such. This is the third principle of effective project governance. If this separation can be achieved, it will avoid clogging the decision making forum with numerous stakeholders by constraining its membership to only those select stakeholders absolutely central to its success.
There is always the concern that this solution will lead to a further problem if disgruntled stakeholders do not consider their needs are being met. Whatever stakeholder management mechanism that is put in place must adequately address the needs of all project stakeholders. It will need to capture their input and views and address their concerns to their satisfaction. This can be achieved in part by chairing of any key stakeholder groups by the chair of the Project Board. This ensures that stakeholders have the project owner (or SRO) to champion their issues and concerns within the Project Board.
Langganan:
Posting Komentar (Atom)
Statistik
Translate
Blog Archive
-
▼
2011
(1064)
-
▼
Oktober
(834)
-
▼
Okt 24
(256)
- Etymology of the word
- Modeling
- Animation
- Rendering
- form•Z on the small and big screen
- Overview
- History
- Transporter
- Modeler
- Product family
- Drafting Assistant
- Animation tools
- Surfacing
- Cobalt (CAD program)
- There is no one way to practice design methods. Jo...
- Current State of Design Methods
- Significance of Design Management
- Proliferation of Information Technologies
- Significance of Proliferation of Information Techn...
- Significance of Emergence of Design Research and D...
- Professional Design Practice
- Significance of Role of Professional Design Practice
- Design Management
- Alternative View
- Background of Design Methods
- Where Process Meets Method
- Emergence of Design Research and Design Studies
- Design methods
- Globalization and governance controversy
- Internet governance
- Formation and growth of the network
- Governors
- Roles
- Elements
- Principle 4: Ensure separation of project governan...
- Additional and complementary principles of governa...
- Additional principles exist where projects are mul...
- Principle 1: Ensure a single point of accountabili...
- Principle 2: Service delivery ownership determines...
- Principle 3: Ensure separation of stakeholder mana...
- Project governance
- Three pillars of project governance
- Professional certification
- Frameworks
- Problems with IT governance
- Corporate governance of information technology
- Definitions
- Background
- Domination by large organizations
- Administration
- Membership
- Recommendations and Certifications
- History
- Areas of responsibility
- Website management team
- Governance models
- World Wide Web Consortium
- Webmaster
- Website governance
- Effective separation
- Flexible presentation
- Reusability
- Web template
- Template uses
- History
- Web syndication as a commercial model
- Web syndication and e-commerce
- Web syndication
- Motivation
- Representational state transfer (REST)
- Automated design methodologies
- Criticisms
- Big Web services
- Web API
- Remote procedure calls
- Service-oriented architecture
- Web service
- Web document
- Advanced
- Security Considerations
- Client Side + Server Side
- Basic
- Web development as an industry
- Client Side Coding
- Server Side Coding
- Best practices
- Changes and updates
- Web development
- Web design
- Advantages
- Disadvantages
- Web content management system
- Capabilities
- Online processing (called "frying" systems)
- Role of information management
- Four stages
- Five stages
- Governance rather than workflow
- Web content lifecycle
- Career
-
▼
Okt 24
(256)
-
▼
Oktober
(834)
0 komentar:
Posting Komentar