I just had a fun, spirited debate on Twitter about the definition of a project. It started when a friend of mine tweeted this:
#ProjectManagement for Beginners (re: #1, remember that project has a fixed duration) 5 min video @projecttipshttp://t.co/jVKHP8UXdH
— Norman Reiss (@nonprofitbridge) April 24, 2014
Now, my team at Legal Services Corporation recently finished a project (at least, that’s what I call it) to redesign the Find Legal Aid lookup on our website. I blogged about that effort, which was kickstarted by the DC Legal Hackers, on LSC’s tech blog. A few things about this:
- There was no deadline.
- It was something that we could have outsourced completely, but we wanted to learn the underlying technologies.
- It was low priority, and my lead developer had a lot of more critical, time-sensitive projects on his plate.
So we didn’t set a deadline. We pitched the project to management with clear goals (a charter). After the initial development was done at the DC Legal Hacker’s first hackathon, we identified the four person team that would work on it internally. We reported on it weekly, during our project review. And we rolled it out when it was finished.
On seeing Norman’s tweet, I challenged the notion that a deadline is a required element of a project. Mind you, many agile programmers work with the bias that iterating until it’s done correctly is more important than meeting a deadline. I doubt that they can actually sell that to their internal or paying clients often, of course.
So I threw my two cents in:
@nonprofitbridge What if your project doesn’t (and shouldn’t) have a fixed duration? That’s a valid scenario. @projecttips
— Peter Campbell (@peterscampbell) April 24, 2014
— Peter Campbell (@peterscampbell) April 24, 2014
which brought this reply from someone that I assume is, unlike me, a certified Project Manager, and therefore better versed and disciplined in the best practices:
@peterscampbell @ProjectTips not really a valid scenario. Create a new project and scope for that project that build from the last. — Rebel Saffold (@rebelsaffold) April 25, 2014
So, here I am, coming off of a highly successful development and rollout of our little webapp, being told that it wasn’t a valid project. The entire tweetstream is copied below, but here are the points that I want to make that go a bit beyond Twitter’s 140 requirement.
- The Project Management Institute (PMI) awards Project Management Professional (PMP) certification to those who complete the requisite hours managing projects and pass the test. I’ve completed their requisite hours, and I’ve taken most of the test prep classes, but I’ve never gotten around to taking the test. So I agree with Rebel that their definition of a project requires a deadline. But I don’t agree with their definition.
- As with many certifications, what you have to say to pass the test is not always what is going to work in the real world. My first career was working as a cook/sous chef, which I did through most of my very late teens and twenties. As with technology, I was mostly self-taught. I’ll never forget one day, when working in a French restaurant in Cambridge, Mass., a fresh graduate of the Culinary Institute of America came on board. He didn’t last his first night on the job. This guy could make some wonderful, complex recipes, but he was overwhelmed when he hit 15 to 20 orders on the wheel. I get the PMI reasoning, but I’ve adapted it over the years in my nonprofit environments where we don’t have the staff or budget to do things to the letter.
- I absolutely value the governance of a project management discipline. I firmly believe that you need to recognize targets and milestones if you want to push forward. My tolerance for “no deadline” is in rare cases like the one above. In particular, I need to have work schedules so that large projects don’t end up piling on top of each other.
- But the trick to successfully getting a lot of things done well in what we call “a constrained resource environment” (e.g. any nonprofit and most of everything else) is to not let the governance get in the way of getting things done. So I take or leave parts of it, being more formal when there’s more at stake and absolutely informal when it doesn’t threaten our outcomes.
I might get that PMP certification someday, although, at this point, it might be when I retire. But, with a few exceptions, I have a good track record of overseeing some great accomplishments in my career, and I expect that to continue until the day that I can retire. And I’ll do it by applying appropriate standards and bucking them when they get in the way of the end goal.
Here’s the tweetstream:
@rebelsaffold What’s invalid if it has scope, outcomes, but no timeline? Still needs resources + planning. @ProjectTips
— Peter Campbell (@peterscampbell) April 25, 2014
@peterscampbell requirements of a project include a project kick off and a closure. http://t.co/8JIccWOd35
— Rebel Saffold (@rebelsaffold) April 25, 2014
@rebelsaffold Waterfall PM requires deadlines. Agile spurns them. The real world requires flexibility and multiple models.
— Peter Campbell (@peterscampbell) April 25, 2014
@peterscampbell that philosophy is why so many projects fail. Deadlines. and milestones, requirements for success and measurement’s.
— Rebel Saffold (@rebelsaffold) April 25, 2014
@rebelsaffold Are you familiar with Agile PM? Lots of successful software you use is developed using it; deadlines are not the priority.
— Peter Campbell (@peterscampbell) April 25, 2014
@peterscampbell tell a client that a deadline is not a priority.
— Rebel Saffold (@rebelsaffold) April 25, 2014
@rebelsaffold Agile PMs do that often. I’m internal IT. I can better manage heavy workloads by not stressing deadlines on less critical work
— Peter Campbell (@peterscampbell) April 25, 2014
@rebelsaffold Waterfall + agile are valid approaches for different types of projects. http://t.co/xMYkW4oGBD
— Peter Campbell (@peterscampbell) April 25, 2014
@peterscampbell again, why 60% of projects fail. 30% of those are by internal PM shops. Numbers don’t lie…
— Rebel Saffold (@rebelsaffold) April 25, 2014
@rebelsaffold I thought we were debating the need for deadlines in some plans. Yes, many projects fail for many reasons.
— Peter Campbell (@peterscampbell) April 26, 2014
@peterscampbell deadlines are a primary reason for failure. No deadlines can lead to stalls and accountability issues with project members
— Rebel Saffold (@rebelsaffold) April 26, 2014
@rebelsaffold Yes, but there are some projects where the deadline isn’t a critical factor. They are exceptions, not rule.
— Peter Campbell (@peterscampbell) April 26, 2014
@peterscampbell Then you should not label it a project. Its an evolving initiative. Those with no PMI background could be confused.
— Rebel Saffold (@rebelsaffold) April 26, 2014
@rebelsaffold We report progress w/project review, have charter, allocate resources (more dynamically). If it walks like a duck…
— Peter Campbell (@peterscampbell) April 26, 2014
@peterscampbell I hope when your “dynamically” allocating resources your using a change request process to warrant additional resources.
— Rebel Saffold (@rebelsaffold) April 26, 2014
@rebelsaffold Do you believe that Project Management is a “one size fits all” proposition? We apply appropriate rigor.
— Peter Campbell (@peterscampbell) April 26, 2014
@peterscampbell not at all, I actually prefer agile myself. However there are some set in stone requirements of a project. Deadlines is 1.
— Rebel Saffold (@rebelsaffold) April 26, 2014
@rebelsaffold From where I sit, PM is a flexible framework for accomplishing things w/proper oversight, not a set of laws.
— Peter Campbell (@peterscampbell) April 26, 2014
@peterscampbell PMI would not agree in my humble opinion. If were ala cart, why is there a certificarion to make sure there are standards?
— Rebel Saffold (@rebelsaffold) April 26, 2014