Learn how to be the safe pair of hands in your organisation, consistently delivering exceptional projects on time and to budget.
The steep rise in demand for good project managers in recent years has been mirrored by the publication of book after book setting out the formal processes and mechanics of project management. Whether they are textbooks or books aimed at the practitioner, they all usually cover the same ground - the ABCs of project management, you might call it.
But anyone who has ever managed a project or overseen the management of a project in the real world knows that there is a significant difference between mastering the ABCs and mastering the practice of project management itself.
It's not that the formal methodologies don't work, but rather that it's only half of the picture. To go from good to great in project management, you need to shift your focus back to the real basics of management.
In this illuminating book, Richard Newton, a successful project manager with twenty years' experience, will show you several ways you can elevate your game.
Topics covered include:
What is successful delivery?
Communications – learning to understand who the customers are, what they want, and how best to communicate with them
What actually is your project? Understanding the importance of scope and how best to define it
How to get your project started
Optimal personal styles for project managers
Managing your project
Getting the best out of your project team
A quick survey of the most important tools and techniques
When to constructively kill a project
Whether you are just starting out in project management, or have a few years under your belt and want to achieve real mastery, The Project Manager will deliver.
Table of contents
- FT Press Financial Times
- 1. Some basics
2. Listening and talking
- The most important chapter in the book
- Your audience – who you must listen and talk to
Listening – learning to understand what the customer wants
- Listening lesson 1 – Make assumptions explicit
- Listening lesson 2 – Understand the scope
- Listening lesson 3 – Understand customer requirements and how they convert into a project
- Listening lesson 4 – Keep checking
- Listening lesson 5 – Customer needs go beyond requirements specification
- Listening lesson 6 – Remember it’s not your project
Communicating with your audience
- Lessons 1–4: Your planning and approach to communications
Lessons 5–11: The style and method of communications
- Communication lesson 5 – Use your audience’s specialist language where appropriate
- Communication lesson 6 – Avoid too much project management jargon
- Communication lesson 7 – Clarify what you mean by risks
- Communication lesson 8 – Present complex information in a clear way
- Communication lesson 9 – Tailor communications to the audience
- Communication lesson 10 – Effectively communicate with senior audiences
- Communication lesson 11 – Do not rely on e-mails
- Communication lesson 12 – Be specific
- Communication lesson 13 – Present key factual information in whole messages at discrete time intervals
- Lessons 14–17: Rules to underpin all communications
3. What actually is your project?
- The importance of understanding scope
The key scoping questions
- Scoping question 1 – What is the overall objective of the project?
- Scoping question 2 – What are the deliverables?
- Subsidiary question 2a – Are there deliverables required by the project which it is explicitly not responsible for?
- Subsidiary question 2b – Are you working to deliver a finite set of deliverables or provide some business capability?
- Subsidiary question 2c – Are you working to deliver a set of independent deliverables or an integrated end-to-end solution?
- Subsidiary question 2d – How will the quality of deliverables be determined?
- Scoping question 3 – Are you working to implement a specific solution, or to solve a problem?
- Subsidiary question 3a – Are you responsible for the delivery of deliverables or for achieving the business benefits?
- Scoping question 4 – How is the customer going to measure success at the end of the project?
- Scoping question 5 – What, from the customer’s viewpoint, can flex?
- Subsidiary question 5a – Do you want predictability or speed?
- Scoping question 6 – Are there any other constraints on the project?
- Subsidiary question 6a – Are there any currently known issues, risks or opportunities?
- Subsidiary question 6b – Are there any external considerations?
- Scoping question 7 – How does your customer want to work with you?
- Subsidiary Question 7a – How will decisions be made on the project?
- Subsidiary question 7b – Can your sponsor allocate all the resources the project requires or do other stakeholders need to be involved?
- Subsidiary question 7c – How high is the project in your customer’s overall priorities?
- Subsidiary question 7d – Who can legitimately put requirements upon the project?
- Scoping question 8 – Are there any implicit requirements, assumptions or needs that the customer has that are not defined in the scope or requirements documents?
4. Some key traits
- The sense of ownership and involvement
Good judgement – project management style
- Judgement 1 – What is in scope?
- Judgement 2 – What should be in the plan?
- Judgement 3 – Which elements of project management process to apply and which to ignore
- Judgement 4 – When to escalate
- Judgement 5 – When to get into the detail and when to skim
- Judgement 6 – When to do and when to delegate
- Judgement 7 – Who can you trust in your project team?
- Judgement 8 – What is an acceptable level of risk?
- Judgement 9 – What is an acceptable level of parallel activity?
- Judgement 10 – What is an acceptable level of change?
- Judgement 11 – When should you enforce the change management process?
- Judgement 12 – When is it reasonable to progress based on an assumption?
- Judgement 13 – How many levels of project management organisation do you need?
- Judgement 14 – When to consider broader stakeholder groups
- Judgement 15 – When is the project complete?
- Project management judgements – summary
- A touch of creativity
- 5. Getting your project started
6. Personal styles
- Styles to avoid
Styles to encourage
- Attribute 1 – Having empathy with your customer
- Attribute 2 – Displaying both management and leadership skills
- Attribute 3 – The ability to handle stress
- Attribute 4 – Respect for people
- Attribute 5 – Dynamism and positivism
- Attribute 6 – Networking skills
- Attribute 7 – Political sensitivity
- Attribute 8 – Having sufficient presence
- Attribute 9 – A sense of humour
- Attribute 10 – Being sensitive to your environment
- Attribute 11 – Adapting your style to the situation
- 7. Managing your project
8. The team
Getting the best from the project team
- Tasks 1–4: Getting the basics right – right people, right skills, right tasks
Tasks 5–9: Motivating and building the team
- Management task 5 – The line management challenge – aligning objectives and motivation
- Management task 6 – Building the team
- Management task 7 – Ensure there is personal development for team members
- Management task 8 – Ensuring people have a home to go back to
- Management task 9 – Be aware of team dynamics and team politics
- Tasks 10–14: Project team management challenges
- Tasks 15–16: The broader context
- Getting the best from the project team
9. The limits of knowledge
- The generalist vs the specialist
- What should project managers not do?
- Specialist skills that should be recognised as not being the project manager’s job
10. The mechanics of project management
The project manager’s toolkit
- Skills 1–7: The core project management mechanics
- Skills 8–13: Supporting mechanics
- What more can you learn?
- The project manager’s toolkit
- 11. Knowing when to say ‘no’
12. Closing thoughts
- Quick reference guide – summary contents
- Chapter 1 – Some basics
- Chapter 2 – Listening and talking
- Chapter 3 – What actually is your project?
- Chapter 4 – Some key traits
- Chapter 5 – Getting your project started
- Chapter 6 – Personal styles
- Chapter 7 – Managing your project
- Chapter 8 – The team
- Chapter 9 – The limits of knowledge
- Chapter 10 – The mechanics of project management
- Chapter 11 – Knowing when to say ‘no’
- Title: The Project Manager: Mastering the art of delivery
- Release date: April 2005
- Publisher(s): Pearson Business
- ISBN: None
You might also like
Project Manager: Careers in IT project management
This book is a highly accessible guide to being a project manager (PM), particularly a project …
Computational Thinking - A beginner's guide to problem-solving and programming
Computational thinking (CT) is a timeless, transferable skill that enables you to think more clearly and …
The GuruBook is an inspiring collection of 45 articles and interviews with well-known thought leaders and …
A Guide to the Project Management Body of Knowledge (PMBOK® Guide), Fifth Edition
A Guide to the Project Management Body of Knowledge (PMBOK ®