What is a project?


“You should go and see Brian about that, it’s his project”

Brian may just be the expert in the company that deals with all enquiries and issues regarding a specialist product or service.  Therefore, it's seen as ‘his project’.

Sometimes we prefix the name of an operational service with the word ‘project’.  It’s part of the companies business as usual activities; however, it brands the service as being specialized for a particular focus area.

The term ‘project’ is used in many contexts.  Sometimes it’s used to indicate a particular area of day to day business that is the specific responsibility of a named individual.

Then we use the term when we talk about introducing change into the business.  Either with new product development, improving a current service, or maybe removing a product or service from the business.

Confusing, isn’t it?

Which is why in our PRINCE2® training, we use a very specific description of the term ‘project’

A project is “a temporary organization that is created to deliver one or more business products according to an agreed Business Case”

This puts it very firmly in the change management area of the business.  The project only exists to introduce something into the business which is different to the current situation.  When this new product is used, a change will occur that has some benefit to the organization.

Whether the justification of the amount of time, money, and effort consumed is worthwhile and viable against the benefits is considered in the business case.

One of the benefits of using a project management framework like PRINCE2® is that it brings clarity to these terms, so everyone understands what they mean.  This reduces confusing and makes for more effective communication in the business.

 

What is PRINCE2®

Business change can be quite tricky to achieve successfully. 

Latest research shows that up to 70% of change initiatives fail.

There are many reasons why this figure is so high, and even some debate about the figure itself.   However, the fact remains that when we try to introduce change into our business, it can be difficult to achieve without the right controls and processes in place.

That’s where PRINCE2® comes in.

The acronym PRINCE comes from the expression “PRojectsINControlled Environments”

The number 2 denotes that this is the 2nd full version of the framework, and we are currently working with the 6th edition as it's revised to keep inline with current business practices.

There are four main areas that form the PRINCE2® framework;

  • Principles
  • Processes
  • Themes
  • The project environment
1.      Principles

Theses are 7 areas of best practice guidance that help us make decisions about what to do on our project.  Simply put, if we are following all 7 principles on our project, we are following PRINCE2®

2.      Processes

A process is a managed group of activities that takes defined inputs and transforms them into specified outputs.  PRINCE2® has 7 processes that are executed in the different lifecycle phases of a project.  There are named processes that help us during pre-project, initiation, delivery stages and the final delivery stage of the project.  They guide us into what we should be doing during these phases.

3.      Themes

Referred to as the aspects of project management, the themes define the different areas of focus for managing the project.  There are 7 defined within PRINCE2®, Organization, Business Case, Plans, Risk, Quality, Progress, and Change.  They give us the mechanisms by which we can effectively control the project in these areas.

4.      The project environment

Arguably the most important element of the framework is its ability to fit any project environment of any size in any industry.  There are many myths about PRINCE2® and its suitability for small projects, Agile projects, or even projects outside of information technology.  The reality is that by ensuring you follow the minimum applicable guidance, you can tailor the framework to suit any project.

So, you have an idea

We all have them occasionally, it’s whether we do anything about them that makes the difference. 

Sometimes we dismiss them out of hand because we can’t be bothered to follow them up, as a cursory glance shows a lot of time and effort needed for not much return.  Other times, we seem to chase and chase ideas and make them happen, regardless of the costs or consequences.

There seems no logic behind how we approach our ideas in this way, but there is some intelligence here if we know what we are looking for.

Where do they come from?

None of us live in a vacuum.

We build our lives around the situations we find ourselves in and our abilities as individuals.  We might get ideas from what we know we are good and what we are not so good at — yet.  We see opportunities and threats in our world that might wish to do something about, and so ideas are born to help us.

Our individual worlds are also surrounded by everything else that happens around us that we have little or no control over.  External factors that we need to respond to, so we comply with legislation or policy.  Economic factors that might open up new emerging markets or close down ones we are in already.

Wherever they come from, we need a process to evaluate them to see if they are worthwhile and viable.

Picture this

What is it you have thought of?

Define what you want to end with after all the work is done.  Draw a picture, if necessary, or at least a mind map of the idea and its major parts.

This helps with defining the levels of quality you are expecting and starts to define the scope of the work you will need to do before you finish.

Why are we doing this?

Often asked too late in the project, it’s quite handy to have an idea of why early on.  What’s happened that requires this work to take place?  From the factors mentioned earlier, this helps clarify why we are doing this project.

How much?

This is a tricky one at this stage of analysis because it's early thinking, so a full detailed cost profile is unlikely.  However, we may have a rough idea of outline cost from simple research, or we may have a budget figure in mind.

It's not just about the money though, time is also important as the amount invested in bringing the idea to life.  Is this a quick win, or is it looking like a significant amount of time is needed and is it constrained?

That looks a bit dodgy

With change comes uncertainty.

The ‘what if’ scenarios.

Not all uncertainty brings disaster though, some events can give a positive outcome if they happen.  It’s useful to put some thought into them though at this point, just in case there are some huge impact events we can think of that effect the viability of the idea.

Help achieve the goals

When we have finished the project, will the result help us move closer to our goals?

Why do something that doesn’t help you achieve these? You will just be investing time, money, and effort into something that will be effectively useless.  A complete waste.

Worthwhile and viable

It may seem like a lot to think about; however, it can be done relatively quickly depending on the idea and what you are trying to achieve.

What I want to end up is just an idea of the time, cost, scope, quality, risk, and benefits that will be the objectives of the project if we go ahead.

This helps with the decision of whether this a worthwhile and viable idea before investing more resources.

It's how we tell the difference between ideas we can chase and those we can dismiss.