Posted on

Project Lifecycle

The Management Pocketbooks Pocket Correspondence Course

Pocketblog has gone back to basics. This is part of an extended management course. This is our last blog before Christmas so may we wish everyone a happy and safe holiday and we’ll be back in 2022.


Implementing business strategy usually means starting one or more projects. Whilst nothing would please me more (as a former professional project manager) than to devote a series of blogs to a thorough description of project management, that is not the role of these blogs and also, The Project Management Pocketbook already covers that ground.

So I shall limit myself, in the next few blogs, to some of the essential models that a project manager will need. We will cover:

 

Four Stage Project

There are as many ways of representing the lifecycle of a project as project managers, but they all contain many of the same features, just different language for the stages, different choices of how detailed to be, and different graphical metaphors for how to draw it.

Here, we will use the version in the Project Management Pocketbook.

Project Lifecycle

Scoping

Define the purpose, aim, objectives and scope of the project to evaluate whether it makes good business sense and is therefore worth proceeding to the planning stage. Good business sense here means consistency with your organisation’s mission, vision and values, and a reasonable expectation that the benefits will exceed the costs.

Planning

Put together a detailed specification for what your project will produce and then use this as the basis to plan what you need to do, in what order, at what time, with what resources and allocating work to which people. Calculate the cost of your plan to create a budget and compare that with the benefits you will get if your project delivers to its specification and you can create a business case. You business case will guide your decision whether to invest in implementing your project.

Implementing

Now deliver your project, constantly monitoring for risks, changes, delays, overspends and the quality of your delivered products. Intervene where necessary to maintain control. At the end of the implementing stage, you can hand over the last of the things you have created to your customer, boss or client. Will they accept them? Only if they are fit for purpose.

Evaluating

How did it go? What did you learn? How did team members perform? Was it all worthwhile? Take this new knowledge into your next project and do that one even better.

Further Reading

From the Management Pocketbooks series:

  1. Project Management Pocketbook
Share this:
Posted on

Delegation: Double your Capacity

The Management Pocketbooks Pocket Correspondence Course

Pocketblog has gone back to basics. This is part of an extended management course.


Management is not about doing things: it is about getting things done. So a large part of your responsibility is allocating work among your team and developing people to take on more demanding challenges. Delegation – getting other people to do aspects of your work – is a part both of effective working and of developing people.

Whilst there are lots of poor reasons for delegating – like off-loading unpleasant tasks, or abdicating responsibility – there are many positive benefits to you, to your team, and to your organisation.

Exercise 1: The Reasons to Delegate?

Make a list of all of the good reasons to delegate. To help you, consider the question from three perspectives:

  1. How can you benefit?
  2. How can your team members benefit?
  3. How can your organisation benefit?

Failure to delegate

The problem is that many managers constantly find excuses for not delegating; even when they know they ought to for many of the reasons you have probably identified. What are yours?

Exercise 2: Excuses for Not Delegating

Here are some excuses I commonly encounter. For each of these, how would you counter the excuse?

  • “I’d be better off doing it myself”
  • “I don’t want to overload my staff”
  • “I don’t have the time to delegate”
  • “I know exactly how I want it done”
  • “If I ask him/her to do it, he/she will be nagging me every five minutes”

How to Delegate

Some people use these excuses simply because they don’t feel comfortable with the process of delegation. Indeed, many guides either make it seem like a big deal, or they miss out an important aspect of the process, leaving people wondering why it fails. So let’s look at the basic delegation process.

Delegation

Step 1. Matching

Understand the task, its level of importance and urgency, and the risks associated with it. Then consider the people available to you, and their abilities, strengths, preferences, and their existing commitments. Also think about their development routes. Now match the task to the most suitable person.

Step 2. Briefing

Brief effectively. Taking time to do this properly is an investment that will result in fewer interruptions, a greater chance of innovation and excellence, and a reduced chance of mistakes and failures.

Step 3. Commitment

After you have briefed and answered any questions, ask if they:

  • Understand the task required
  • Can carry out the task required – do they have the ability and availability?
  • Believe the resources and time allocated are sufficient for the task required

Then ask for their commitment to do the task required. In return, offer your commitment to support and monitor the process.

Step 4. Monitoring

An important part of risk management and of developing the person you have delegated to is to monitor their performance. Monitor more or less frequently, depending on your level of confidence and certainty, and the level of risk.  Remember: when you delegate a task, you retain responsibility for it.

Step 5. Feedback

When the job is done, offer objective feedback on performance and listen to what they have to say about their experience and any concerns. Recognise the work done and contribution made, reward it with thanks and praise, and highlight what the person can learn from their experience.

Further Reading

Share this: