IT Programme Delivery

/IT Programme Delivery
IT Programme Delivery 2017-07-11T14:59:01+00:00

I am and have been managing major Programmes and Projects for my Clients. Here are some fundamental definitions and thoughts around my management style of these programmes and projects, which are based on my company’s way of working.

Programmes and projects are different

For both programmes and projects it is the outcomes that matter, not their outputs. Outputs are specified deliverables that are delivered within time, cost and quality constraints. Outcomes are the effects of change, which trigger the benefits for the programme or project.

Projects can exist in two environments:

• Standalone as part of overall corporate management

• As a part of a programme

A programme is a portfolio of projects and non-project activities that are co-ordinated and managed as a unit such that they achieve outcomes and realise benefits. The realisation of the benefits is usually managed within the scope of the programme and as such, they require active management of business change. Those who fill programme roles must show the required competencies and have the necessary skills and experience to achieve the change. A programme management approach lends itself to complex changes with delivery and benefits phased over time.

A project is a finite piece of work (it has a beginning and end). It’s undertaken in stages and carried out within defined cost and time constraints directed at achieving a stated objective. The realisation of the benefits doesn’t normally form part of the scope of a project. In a programme context, the realisation of the benefits is overseen through the programme sponsor and manager; in a non-programme context, these benefits are overseen by the part of the organisation which initiated the project. A project management approach lends itself to situations where delivery of the final output is not phased.

Effective programme and project management relies on four aspects;

• Accountability tells us what a person is accountable for doing and who they are accountable to.

• Methods and procedures are used if consistency in undertaking an activity adds value; if consistency does not add value, procedures are not needed.

• Systems and tools should make the operation of the procedures more effective and efficient.

• Culture sets the tone for how the accountabilities, procedure and tools are used in practice. For example, a culture of “distrust” will lead to more people being accountable for checking your work which leads to more complex procedures and tools.

Publishing procedures and providing tools is essential to effective programme and project management– but there’s a lot more to it. It is the way in which they are used that makes the difference. This is why it can be difficult to transfer a procedure from one organisation to another or, indeed, why something may stop working in an organisation that has undergone radical change.

Strategic partners or simply suppliers?

June 1st, 2016|0 Comments

To IT buyers, strategic partners are vendors that have gone beyond effective delivery of systems and services to become consistently transparent, responsive and trusted collaborators [...]

Customer-centricity explained – what it means to be customer-centric

April 3rd, 2016|0 Comments

Customer-centricity: what is it and what does it even mean to be customer-centric? Does it matter to define it or look at how people define [...]

What are the future Customer Service Trends?

February 6th, 2016|0 Comments

Here are some ideas from Gartner of what the future of customer service and customer experience could look like. Customers are being smarter and smarter, and [...]

Ensuring the best IT service providers deliver the best IT service

January 28th, 2016|0 Comments

‘Service Integration’ is the integration of different IT service elements into a coherent set of end-to-end services bound by Operating Level Agreements (OLAs) and service [...]