Senin, 24 Oktober 2011
Additional principles exist where projects are multi-owned
08.00 |
Diposting oleh
Unknown
Multi-owned is defined as being a project where the board shares ultimate control with other parties. The principles are;
There should be formally agreed governance arrangements
There should be a single point of decision making for the project
There should be a clear and unambiguous allocation of authority for representing the project in contacts with owners, stakeholders and third parties
The project business case should include agreed, and current, definitions of project objectives, the role of each owner, their incentives, inputs, authority and responsibility
Each owner should assure itself that the legal competence and obligations and internal governance arrangements of co-owners, are compatible with its acceptable standards of governance for the project
There should be project authorisation points and limiting constraints to give owners the necessary degree of control over the project
There should be agreed recognition and allocation or sharing of rewards and risks taking into account ability to influence the outcome and creating incentives to foster co-operative behaviour
Project leadership should exploit synergies arising from multi-ownership and should actively manage potential sources of conflict or inefficiency
There should be a formal agreement that defines the process to be invoked and the consequences for assets and owners when a material change of ownership is considered
Reporting during both the project and the realisation of benefits should provide honest, timely, realistic and relevant data on progress, achievements, forecasts and risks to the extent required for good governance by owners
There should be a mechanism in place to invoke independent review or scrutiny when it is in the legitimate interests of one or more of the project owners.
There should be a dispute resolution process agreed between owners that does not endanger the achievement of project objectives. [4
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