Welcome to Manager Tools. Today's topic, Horseman's Law of Project Management, Part 1. Over the course of the last several years we've talked and joked about it many times

and in this cast we finally put the rest of details of horsemen's laws of project management.

Mark came up with it several years ago to help a group of

young managers get over the fear of working on fairly complex software development projects.

The concept is simple. All projects are simply tasks, done by people, within certain time frames.

Despite all the protestations to the contrary, no matter how complex a project they all boil down to who is responsible for doing something, what they're responsible for, and when they have to get it done by.

Complex tools can be helpful, but, you know, frankly only on really large projects.

We simply suggest you keep it simple with horseman's laws of project management.

Here we go. You know how long have we been doing podcast now?

Since we were five since we were five five, it feels like that sometimes.

Like three, three, over three years now?

Three and a half, three, three plus?

Okay, so after three and a half years we haven't had yet a cast on horseman's laws at all on the horse

laws which is kind of interesting in and of itself but yeah maybe we'll come

back to that but but I wonder if listeners also thought we'd ever, ever do one on horsemen's laws of project management.

Yeah, I, I think the reason we didn't do horsemen's laws was because we felt like they weren't actionable,

although we should probably just do a set and release them and not make them weaklies or something.

I was hoping, of course, yet yet again that you could read my mind and

I wouldn't have to write it all down because there's a lot of it. But but hopefully

you're glad we're doing it because of all your project

management experience I mean I I think about the PMO that you ran.

It's a horseman's laws of product management is kind of interesting to me and you and I have talked about this a lot right and

...