Project Definition is not just the first substantial stage of your project. It is also the foundation upon which you will build your whole project.
The rewards for getting your Project Definition right are matched only by the penalties of getting it wrong.
So it’s time we took on defining your project with one of our giant guides.Rewards for getting your #Project Definition right are matched by penalties of getting it wrong Click To Tweet
Before we look at the how, though, perhaps we should start with the what…
And the why…
The answer to this question is easy. If you don’t know what your project is, you can’t make a well-reasoned decision about whether or not it’s the right project to do. This is as true for Agile projects as it is for more traditional methodologies.
Indeed, it doesn’t matter where you are on the Agile-Traditional scale, or whatever project methodology you choose, from PMBoK® to PRINCE2® or from Kanban to Scrum. Wherever you are, you need to know if doing your project will be a wiser decision than not doing it. Or doing a different one.
And, before you make that decision, you need to know what it is your project will be about. That’s your Project Definition.
Does this project make good business sense?
To do this, you need to do two things:
It is the balance between these two that will influence your Sponsor’s or Project Board’s decision to approve your project.
There are two principal parts of the answer to this question.
For starters, your project must align closely to your organization’s mission, vision, and strategy.
Note that this does not mean that the project must be a part of your primary strategy. An important aspect of strategic planning is building-in flexibility. So it’s vital to set up a portfolio of projects moving towards different futures. This will give your organization some resilience against events that may not match the scenario you are basing your main plan on.
But your project does need to fit with organization-wide strategic thinking. If it does not, then it will conflict And that will divert valuable resources and attention from what matters.
The second component is whether the project looks like it will deliver good value for the money, risk, and effort it needs.
You won’t be able to do this in detail during the Project Definition stage. This is because, for a full budget, you’ll need detailed plans and specifications. These will come in the Project Planning stage. But you should be able to:
Without it, you can’t understand the strategic contribution your project would make. Nor can you estimate the costs and benefits. In this article, we will focus on the first requirement for establishing ‘good business sense’:
The need to be absolutely clear what your project is, and what it is not
Being clear what your project is and is not is the purpose of your Project Definition. So, in this extended article, I’ll show you the ten essential components you’ll want in your Project Definition.
Let’s start by listing them. And then we can discuss each one in a little more detail.
If you’re in a hurry, you can click on any of them to go straight to that section.
So, with no further ado…
This is the over-arching aim of your project. It answers the question:
What do we want?
So your goal describes what your project is in the widest possible terms. It is also you marketing and recruitment statement. Because when anyone asks you what you are doing, the answer you’ll give is your goal. So make your goal valuable to your primary stakeholders (see below) and motivating to the people who will work on the project with you (see below).
You can find out more about project goals in our Video: ‘What is a Project Goal?’
After your goal, your objectives are the next most important part of your Project Definition.
They set out the criteria by which you’ll assess how well your project succeeded in the way you delivered your goal. They articulate the factors that matter to your stakeholders. Put another way, they answer the question:
How do we want to achieve out goal?
The three most commonly stated objectives are time, cost, and quality. Together these form the ‘Time-Cost-Quality Triangle’ – which is also known as ‘The Iron Triangle’.
So, you need to consult your stakeholders (see below) on:
You have probably heard of the SMART, or SMARTER, or SMARTEST formulations for crafting well structured objectives. These are the commonest memory aids. Although you’ll find plenty of variants, they most commonly stand for:
Determining the scope of your project is the hardest part of creating your Project Definition. In fact, I’d say it’s the most difficult part of Project Management*. The scope is all the things you will do within your project, or all the things it will create. We have a short video that will give you more of an answer to the question: ‘What is Project Scope?’
(* This is one of our Essential Project Management Rules)
Because your different stakeholders (see below) will have different ideas about what is vital, important, desirable, or unnecessary.
And pleasing some will mean upsetting others. Unless, that is, you have a limitless budget…
Which you won’t.
So, in the real world, as PT Barnum would have said if he’d been a Project Manager rather than a showman:
You can please all your stakeholders some of the time…
And you can please some of your stakeholders all of the time…
But you can’t please all your stakeholders all of the time*
So scoping is an exercise in negotiation and compromise. Your job is to maximize the the value you can generate with the resources you can secure.
(* This is another of our Essential Project Management Rules)#Project #scoping is an exercise in negotiation and compromise Click To Tweet
To help you navigate the challenging waters of project scoping, check out our feature article ‘How to Define Project Scope’.
For everything you decide you can and should do within your project budget (your scope – see above), there will be a load of things can’t or shouldn’t do.
The problem is that some stakeholders will assume from your project goal (see above) that these are a part of your project. So, if they find out they aren’t, they’ll be disappointed. More worrying, they’ll ask you to add them in, with the three words a project manager most fears:
Could you just…?
So, to avoid the dreaded specter of ‘scope creep’ you need to have a strong answer. The best is to have a signed-off project definition. And in it, you’ll need a list of Project Exclusions. These are potential items of scope, which you have explicitly excluded. These are the things you could do; but you won’t.The three words a #Project Manager most fears: 'Could you just...?' Click To Tweet text
In the US, your Scope (see above) will be articulated in terms of the things your project will produce. These are your Products or Deliverables.
In many other places, like the UK, scope refers to scope of work. There, Project Managers articulate scope in terms of the tasks, or activities, that produce the deliverables.
Both approaches are fine. If you do articulate your scope in terms of products, then you’ll still need to create a task list when you start planning. If your scope statement reflects tasks and activities, your project definition will need to include the things you’ll produce.
When you get to planning in detail, you’ll break these down into fine detail. But in the Project Definition Stage, your main deliverables will usually be enough.
Just click on the button below…I want the FREE Project Fundamentals course
When you want to define your project fully, you will need to consider some of the context within which it sits.
So your next consideration will be dependencies and constraints.
Dependencies are external factors that will interact with your project, affecting its progress, timing, resource selection and utilization, and technical capabilities. And dependencies work in both ways. So they are therefore sometimes referred to as inter-dependencies. This means that:
affect your project, but
Constraints are factors that will constrain, or limit, the choices you will be able to make. Typical examples are:
There is no such thing as a project, without risk.
Risk arises from uncertainty, complexity, pressure, and novelty. And projects have all of these. If Tim Lister is right, and I believe he is, then:
Risk Management is how grown-ups manage projects
If you are going to manage your project in an adult way, you have to start as you mean to go on, with a thorough assessment of the risks. Remember, the reason for the Project definition stage is to inform robust decision-making. And any go/no-go decision must be informed by a realistic assessment of the risks.
Issues are like risks. Risks have an uncertainty to them. They or may not happen. Issues will happen – or have happened already. So you need to deal wth them during the project definition stage, or see the case for your project undermined from Day 1.
Uncertainties and assumptions are close cousins of risk.
They are three ways of explaining the same underlying insight. But, often, some things are most easily uncovered through one mode of thinking.
If risk management is how adults manage projects, then sophisticated adults manage them through careful stakeholder engagement. Your stakeholders will determine the success or not of your project*. So, defining your stakeholder group, and their respective concerns, is effectively defining your project.
At this stage of your project, I’d suggest you follow four steps:
(* This is another of our Essential Project Management Rules)
The last of our components of your Project Definition is the team you’ll deploy to deliver it. At this stage, you aren’t recruiting. But you do need to think about the range and depth of skills, expertise, and experience you will need. This will inform your set up of the project.
I’d include in this, some early thoughts about the kind of governance arrangements that will be appropriate. This will need to take account of the level of risk (see above), the scale of the project, and the importance of the goal (see above).
Is this an absolutely comprehensive list of things to consider in your Project Definition?
But it’s a very good start… And certainly more comprehensive than many I’ve seen applied. More to the point, there is a lot more information to learn about the process of creating each of these components. That’s why we have built our most innovative program to date.
Together these allow you learn and do at the same time – or to simply learn how to Define your Project, and put the tools aside for when you need them.
Dr Mike Clayton is one of the most successful and in-demand project management trainers in the UK. He is author of 14 best-selling books, including four about project management. He is also a prolific blogger and contributor to ProjectManager.com and Project, the journal of the Association for Project Management. Between 1990 and 2002, Mike was a successful project manager, leading large project teams and delivering complex projects. In 2016, Mike launched OnlinePMCourses.
Please log in again. The login page will open in a new tab. After logging in you can close it and return to this page.