Project Management Fundamentals for Data Analysts

“Oh. No… This is going to take WAY longer than I thought”

How many times have you said that to yourself in the past week? The past month? The past year?

Why’s it so hard to estimate how long a task will take? How many people it’ll take? Whether you’re able to add it to your to-do’s?

Almost every project runs over deadline. Why does this happen despite everyone’s best efforts? You’ve got a vague sense that there’s some underlying cause of why a simple request from someone might have little effect on your workload or deadlines in some cases, but in others the same request can cause a huge delay, or mean you’ll be working flat out for weeks to catch up.

What’s going on? Should we just shrug our shoulders and accept “that’s just the world of modern work”?

I don’t think so. Not at all.

There is a way for you to plan for the many curve-balls that come your way when managing a project. It’s possible to develop a sense of intuition about whether a project is about to be delayed, or how to mitigate problems as they arise. Even better, it’s possible to plan projects that head off many of the setbacks that others’ consider an unfathomable, inevitable occurrence.

Whether you’re managing a project, or are part of one, there’s fundamental principles at play. Once you learn about them, you’ll spot them happening all around you. I’ll bet that if you go check your inbox right now – there’s at least one message that’s about to affect the lead time, critical path, effort, overhead or capacity of the projects you’re juggling. And Data Analysts end up having to do a lot of juggling.

Once you know what these fundamental principles are, you can plan for or mitigate them. If a project really goes up in flames, you can apply the right fix to them. Just like you need to learn fundamental concepts in maths or physics to be able to extrapolate solutions to more complex problems, so too will learning about the fundamental concepts of project management help you for the rest of your career. Frankly, as astonishing as it is that we send high schoolers out into the world without any knowledge about how taxes work, bills, credit or managing a household budget, neither do most Data Analysts get ANY training on how to manage projects. None at all. Pretty crazy given that with the growth in data worldwide, data professionals are finding themselves embedded in, and often leading, pretty complex projects in novel areas.

Learning is of course a lifelong exercise, but I don’t think many Project Management resources lend themselves as a good first introduction to the topic. Courses are quite long, the material a bit dry or a lot of more advanced esoteric stuff packaged up with the basics to justify high price tags.

Project Management for Data Analysts book cover. Cartoonish drawing showing a laptop, with the left side on fire and icons showing 666 unread emails, a crying emoji, pennies, pie chart, a data dot pdf file and speech bubbles asking when the work will be done by. The right hand side shows a smiling face, cash, nice graphs, a thumbs up and speech bubbles saying thanks and fantastic!

In Project Management Fundamentals for Data Analysts, I’ve boiled the concepts down to the bare essentials which can be read in under 15 minutes – you can certainly fit that into your crazy schedule (and it will help your future schedule not be so chaotic!).

These concepts can be used to great effect on their own if you wish to never read another word on the topic. It’ll also provide a solid foundation if you want to dive deeper into more formal courses or sophisticated theory.

The book will soon be ready for sale. To be notified, sign up to the newsletter!

Sample content

Table of content 28 pages in total
What you can expect from this book	
The building blocks of projects	
Task duration vs lead time	
Dependencies & critical path	
Effort, overhead and capacity	
Effort	
Overhead	
Capacity	
How projects catch fire	
Working on too many projects	
Changing Project Scope	
Lead time	
Dependency	
Effort	
Not having contingency	
Lack of communication	
How to deal with all of this	
In conclusion	
A checklist	
A few last things...
You will get

A short read of less than 20 minutes
1st principles of project management
Ability to identify risks to project deadlines 
Free updates to any corrections (of course!)
Access to additional chapters that might get added to this edition


You won’t get

Deep project management theory
100% correct Project Management terminology (in order to avoid you or I having to get into deeper stuff)
How to use project management software


Once you understand the fundamental principles of project management, it will be much easier for you to run projects well and steer troublesome ones back to a safe path. 

I do give some “how to” advice, but treat these as illustrative examples only. It’s much more valuable for you to understand WHAT is happening, and then develop your own methods of HOW to manage it.
Dependencies & critical path
Many tasks require other tasks to be completed before they can begin, which creates a dependency.

Image showing how one lead time of a task follows after the previous is completed, joined by an arrow denoted as "dependency"

Not all tasks are dependent on one another, so you get a branching of task dependencies. The sequence of dependent tasks whose total lead times are the longest is what’s called  the critical path. 

Image showing the multiple branching dependant tasks, with the longest chain highlighted in red and denoted as "the critical path"

Don’t miss any updates, sign up below. I don’t post very often 🙂

* indicates required
Back to Top