Senin, 24 Oktober 2011
Principle 2: Service delivery ownership determines project ownership
07.59 |
Diposting oleh
Unknown
Organisations deliver services and utilise assets as platforms for the delivery of these services. It is therefore critical that the assets delivered by the project meet the service delivery needs of the organisation. If the project outputs do not support service delivery needs, as detailed in the business case, to be met in full, the project has to some degree failed – it has not achieved optimum value for money.
The only sure method of ensuring project outputs meet service delivery needs is for ownership of the project and its business case to reflect service delivery ownership. This is the second principle of effective project governance.
The organisation chart is normally sufficient to identify who in the organisation is accountable for the delivery of the service that the project will enable. It is important that the project owner, in their service delivery role, is as close to the service being delivered as possible. The corollary to this is that the ownership of the project does not reside with those delivering the asset. While the asset may be central to the provision of the services, it does not in itself constitute the service. This concept has implications in important aspects of the project. For instance, a service delivery focus necessitates a whole-of-life cost perspective since the service itself will have an associated ongoing, post-project, operational cost. A service delivery focus also recognises that at commissioning the asset must integrate into the existing service regime. On the other hand if a project is viewed as delivering an asset, the focus is on the capital cost of the asset and operational costs become a secondary consideration as does serviceability of the outcome.
The intention therefore is to determine the ownership of the project by identifying the owner of the service the project will deliver. This approach places the business at the heart of project delivery. While the business may be unable to deliver the project without assistance, it never-the-less is in the role of primary project decision maker, albeit supported as necessary by project delivery specialists. This ensures the project governance framework maintains a service delivery focus.
Principles 1 and 2 are focussed on the project's major stakeholder – the owner of the project. Projects have many stakeholders and an effective project governance framework must address their needs. The next principle deals with the manner in which this should occur.
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