Skip to main content
Subscribe
Never miss an interview. Click to subscribe with your preferred app:
60 Free PDUs
Earn all the PDUs you need. It's free:

Episode 003: Project Failure

Play Now:

In today's show we are talking about project failure. We'll look at the numbers of failing projects quoted in various statistics and the critical success factors identified in order to have a successful project. But most importantly, we want to know how project managers who are faced with a failure manage and cope with this failure.

Episode Transcript

Below are the first few pages of a computer-generated transcript with all its computer-generated quirks.

Cornelius Fichtner (00:11):

You are listening to the project management podcast. We bring project management topics to beginners and experts. Find us on the web at PM. podcast.blogspot.com or send your emails to PM This email address is being protected from spambots. You need JavaScript enabled to view it.. Hello, and welcome to the third show. This show was recorded on the 17th of September, 2005 in it. We'll talk about project failure, and I know I have to go and get some Kleenex because I'm sure I'll start crying. And just a minute, in my last show, I said that this show was going to be the second part of my review of the 2005 PMI leadership meeting in Toronto, Canada. But due to current events, I have changed the topic for today and we will talk about project failure in my resume. I sometimes mentioned that I have successfully implemented all assigned projects over the past five years. Of course I was lying when I said that, because in truth, I had successfully completed all projects over the complete 15 year project management career.

Cornelius Fichtner (01:26):

But since nobody would believe that I cut it down to five years, I don't really know why I have been this successful. My best guess is that it's probably a combination of just plain good luck, a certain talent for project management and simply being assigned the right projects, those projects that weren't meant to fail, but now it looks like I'll have to delete that sentence from my resume because one of my projects is failing and probably has failed. Let me give you the background of this. I work in the it department of a bank. Well financial institution, really. We are roughly 130 people of which half are software developers. We support about 120 applications. We have a very quick turnaround for a financial institution. We have a software release every month, and of course there's a hell of a lot of risk involved with this quick turnaround.

Cornelius Fichtner (02:28):

When you just push out software, every 30 days testing on the other hand to mitigate this risk is quite minimal people test the new features. People make sure that well it's now no longer green. We've changed it to blue. They make a quick test. Is it blue? Yes, it's blue. Perfect. Let's move on. I got real work to do here. I don't need to test this software. There are really no regression tests in all of this. I doing the project that has now failed. We were hoping to establish some sort of a suite of system tests that we could run during the release weekend. Until today, we've been able to set up to create a basic environment test. Uh, we were able to create a suite of smoke tests and we have about 75 manual user acceptance test scripts that really tests just the availability of the most critical functions in the applications.

Cornelius Fichtner (03:33):

So these 75 tests, we went to the users and said, Hey, if you show up on Monday morning and you needed to work with the system, what's the most critical stuff that you need functioning. So we have that that's available, that's here and ready. And it took about a year to create all this my original plan. However said that at this point in the project, we should have a finished and automated suite of all of the tests that I mentioned and much more as of yesterday, I have decided that this project has failed and it stuck with absolutely nowhere to go. Trust me, I was absolutely pissed about the fact that I had failed. I was grouchy. I was bad tempered. And just generally in a sour mood about this, I needed a shrink to get me through this, some sort of a psychologist. So I went to doctor Google and I searched around.

Cornelius Fichtner (04:36):

And in the end of all, places, I ended up on the pages of alcoholics anonymous, where I found their original 12 step program. And then, you know, the 12 step program, it's nothing more than a methodology, right? So what does a good project manager do? He reads the methodology and then he decides which parts he wants to take and which parts he wants to leave. And frankly, for me, only the first two step, really, they, they helped, ah, here they are. First step. We admitted that we were powerless over alcohol, that our lives had become unmanageable. Second step, we came to believe that a power greater than ourselves could restore us to sanity. Okay. Yeah. The first one, absolutely. I admitted that I was powerless over the failure of this project and I admitted that the project had just become unmanageable, that it was going nowhere.

Cornelius Fichtner (05:37):

And I also came to believe, step number two, that a power greater than myself. Um, let's see executives, the sponsor or business users that only they could restore this project back to its sanity. Hmm. So that helped me get over mine, just complete frustration of having to face my first failed project, my failure. However, it got me thinking and I wanted to know, is it really true that 70% of all it projects fail because with my track record, it's statistically wrong. So back to Google start surfing around. One of the things that I found is probably the most widely quoted statistic on project failure. It is the Standish group's chaos report. They've been doing that since 1994 and they have analyzed thousands of projects and they have come up with three categories on how projects succeed or fail. First category is of course, a successful project, meaning that the project is completed on time and on budget with all features and functions as originally specified.

Cornelius Fichtner (07:05):

Then there are the challenged projects, the project is completed and operational, but over budget late and with fewer features and functions than initially specified at third. Yep. That's the failed project. The project is canceled before completion or never even implemented so much for these three categories. And when you look through the Standish reports over the years, the chaos reports, what you'll see is good news folks. What Standish saw was a massive increase in projects that were executed. And at the same time, the percentage of successful projects has increased a lot more than the percentage of those projects that have failed based on these three categories that they've had. And a lot of thank you goes of course, to project management and the according processes behind it. So project management really, really helps to make a project successful. Yeah, we all knew that, right. But what are the critical success factors for these projects? Well, the chaos report, the original Carol's report talked about the chaos 10, the 10 critical success factors to make a project succeed. And when I looked at those, I had my big

Cornelius Fichtner (08:41): Oh

Cornelius Fichtner (08:42): Experience, which really, really explained why my project is failing, what's failing. And all I had to do was look at the first four of these 10, what they did is they also graded them and they gave them a number. And the first four, they add up to 60% of why projects fail or succeed. And here are the first four executive support, 18% user involvement, 16% experienced project manager, 14% and clear business objectives. 12%, no wonder my project is failing. I have no real executive support, 18% right. Gone. The user involvement is absolutely minimal. They don't give at dingoes kidneys about testing. They have real work to do and clear business objectives. Yeah, not really. Okay. So 46% of my critical success factors right there gone experienced project manager. Yeah. Okay. I'd say I'm experienced, so we're good there, but the other 46 being goal, that's why my project is failing.

Cornelius Fichtner (10:11):

Could I have done more to get executive support? Could I have done more to get the users involved and to get clearer business objectives? Sure. I could, but I really tried my absolute best to make this project work. Oh. And by the way, this is not the first time that my company has tried this. I'm actually the third person who's failing with this particular project. So overall I now understand much, much better why this project is failing. Let's take a few looks at examples of percentages. You know, I started out this search trying to figure out, is it really 70% of projects that file fail of IT projects? Well, I found on gantthead.com. I found an ad that said more than 60% of software projects in the United States fail and poor requirements management is one of the top five reasons. Okay. I found a paper on project success and failure.

Cornelius Fichtner (11:14):

What is success? What is failure? And how can you improve your odds for success in that particular paper? And I'll put a link onto my blog. They talk about 30% of it projects that fail. And I went back to the Standish report to the chaos report and I found the 2004 third quarter chaos spotlight. It's just a one page PDF giving you the basics of it. All they say 18% failed, 29% were successful. And 53%, which challenged. So according to the longest standing report that we out there still over half of 80 projects that we perform are challenged. Hmm. Interesting. Well, and just about as many different percentage numbers that you'll get, you'll get the same number of reasons why the chaos 10, like I said, starts out by saying the executive support. 18% of that is, is very, is, is the reason why projects fail.

Cornelius Fichtner (12:21):

So very big number on executive support there in Lorin J. May wrote an article called major causes of software project failures. And he starts out there by saying that poor user input is the first one that's going wrong. And then we have an article by James Jang, Gary Klein, and Joseph Balloon called ranking of system implementation success factors. Uh, that one appeared in the project management journal in 1996. Okay. Okay. That's a little while ago, but generally speaking, it's probably still standing what they say and they say, number one reason, clearly defined goals. So take your own pick. I mean, anywhere from what was it, 18% to 60% and any real reason that you can find, you can put it right there at the top of your list. Another thing that I realized as I was doing this little research here is, you know, project failure is a taboo.

Cornelius Fichtner (13:31):

I have yet to find a project manager who walks up to me and openly admits, you know, my project has failed. I have done my part in this and I have openly admitted my failure in a project. So I belong to these 18 or however many percent of it projects that fail. Now I want to hear from you, my dear listener, drop me a line, send me an email to PM This email address is being protected from spambots. You need JavaScript enabled to view it.. And tell me about your failed projects. Tell me why you think they failed. Tell me with which of the studies that I have mentioned here. Do you agree or disagree? Well, is executed support more critical than user requirements? What have you found on your projects? Why did they fail and what could you have done differently in order to not have them fail to be successful? But here is what I want you to do.

Cornelius Fichtner (14:32):

Most importantly, whenever I manage a project, my focus is first and foremost on people because it's people management really not project management. So tell me, how do you keep your sanity after a failed project? How do you motivate yourself to continue? Do you just shrug your shoulders and say, Oh, well you win a few. You lose the flu and you move on. Do you go out and get drunk with your project team? Or do you soak for weeks at end? Let me know how you deal with failure. What works for you? Because nowhere in all these studies do they look at the people behind the failed projects? I couldn't find anything on that. Nobody talks about the fact, well, this is stressful. This is annoying. This is aggravating. If you have a failed project, you have to admit yourself, you failed, you weren't as good as you thought you were.

Cornelius Fichtner (15:37):

How do people cope? How do we project managers cope? Because after all, if the statistics are true and depending on which one you believe three out of 10 project managers will face a failed project. And somehow they get over it. They continue, they move on to the next project. But what is the process? How do they get over it? What do project managers do in order to move on and go to the next project? And also what does this mean to their career? I mean, how do people look at them in the future, in the same company? Well, he's not a failed project. Can't be much good County. Drop me a line, a PM This email address is being protected from spambots. You need JavaScript enabled to view it.. And tell me what you think even better. If you have the opportunity to make an MP three recording, make about a one to two minute recording of your thoughts, send it to me. And I'll be more than happy to put you here on the project management podcast for that.

Cornelius Fichtner (16:40):

Yeah, that's about it for today. Thank you very much for listening in my next show, I will go back to the promised review of my third day after 2005 PMI leadership seminar in Toronto, as always, you can find us on the This email address is being protected from spambots. You need JavaScript enabled to view it., or you can send your emails to PM This email address is being protected from spambots. You need JavaScript enabled to view it.. And finally, we have this today. It's a quote from Jones and capers book patterns of software systems, failure and success. There are myriad ways to fail on a project, but there are only a few ways to succeed with that. Let's all stay on the path to success and sanity until next time.

Above are the first few pages of a computer-generated transcript with all its computer-generated quirks. A human-generated transcript is available to Premium subscribers starting with episode 136.

Episode 002: PMI® 2005 Leadership Meeting Part 1

Play Now:

Several times a year, the Project Management Institute (PMI) holds Leadership Meetings all around the globe. These meetings are for component leaders (chapter board members, SIG chairs etc.) to attend and grow as leaders. This is my review of the first two days of the 2005 PMI® Leadership Meeting in Toronto, Canada.

Episode Transcript

Below are the first few pages of a computer-generated transcript with all its computer-generated quirks.

Episode 002: PMI® 2005 Leadership Meeting Part 1

Cornelius Fichtner (00:11):

You are listening to the project management podcast. We bring project management topics to beginners and experts. Find us on the web at PM. podcast.blogspot.com or send your emails to PM This email address is being protected from spambots. You need JavaScript enabled to view it..

Cornelius Fichtner (00:27):

Hello, and welcome to the second show. It wasn't recorded between the seventh and 11th of September, 2005. And this show will definitely interest you if you're a member of the PMI, or if you're thinking about joining it this week, I spent four days at the 2005 PMI leadership meeting in Toronto, Canada. PMI holds these leadership meetings regularly all over the world, some locations where, for instance, in October, 2004, they were right here in Anaheim, California in the United States in February of 2005, it was in Singapore and may. It was in Edinburgh, England, September. That was last week. It was in Toronto, Canada, and that's the upcoming shows that you'll hear. And at the end of October, it'll be in Panama city Panama. This was my first meeting and I have decided to divide my reviews for you into two shows. The reason for this is because the focus was quite different on day one, we focused on issues and trends within the PMI, and that's also going to be the first show to show that you're hearing today. And on day two and three, we were attending several seminars on leadership and that's going to be in one of the upcoming shows. Well, then let's jump right in and listen to what I had to say as I was traveling to the seminar.

Cornelius Fichtner (01:55):

All right, I'm sitting here at Chicago, O'Hare international airport. I'm on my way to Toronto, to the 2005 PMI leadership meeting. I'm arriving a day early because I'm a first timer and I want to attend tomorrow's first time of session, which of course means I have to spend a whole day in beautiful Toronto tomorrow, walking around, looking at all the sites. And hopefully also connecting again with my friends, all of whom I haven't seen in 15 years. Oh, well, all things I do for my profession as always, I prepared very little. Whenever I go to a seminar, I select the seminar. I generally know what it's all about. And I do very little before I actually do. So then I print out in this case, 50 pages from the website, and I read through these pages as I journey to wherever I need to go.

Cornelius Fichtner (02:51):

I looked at the schedule. I looked at everything that I want to do. And frankly, I'm quite impressed by the number of which the PMI office here. I counted 24 separate seminars. And that was just at a glance. Let me give you a quick overview here of what it is that they're doing. First of all, there is the association governance track. The association governance track has seminars in it like the building of a knowledge center, getting industry leaders on board and the theme that goes throughout all of the tracks volunteers, our most valuable resource. The next track is the PMI institutional knowledge track, where you can learn about generational differences and professional society participation research program, past, present, and future. And then there's also obtaining and sustaining volunteers. So once again, we talk about volunteers here and finally the individual leadership development. Again, they have one of the seminars in that track is leadership fundamentals for volunteer leaders, overview of the seven habits of highly effective people. It's an interesting topic. And then there is perfecting public speaking skills, which I doubt they can do on Friday morning from eight 30 to nine 30, but at least it's the stone. So I'm looking forward to three days, filled learning three days, which I'm sure the PMI can pull off with their years of experience in organizing such seminars.

Cornelius Fichtner (04:28):

I used my iPod to make this recording. And as you can probably tell the sound quality of an iPod is not all too great. I hope however that you could at least tell how excited and how motivated I was to attend this meeting at the end of day, one night, set up my recording studio, a laptop and a microphone in my hotel room. And here is what I had to say followed by a voice of someone else.

Cornelius Fichtner (04:56):

It is the end of day zero at the PPI leadership seminar, 2005 here in Toronto, and not much happened really today in terms of project management. So let me start with last night, I went out to dinner with Glen Fujimoto, who is the chair elect of the chapter project management Institute of orange County, where I am the programs director. We sat in a seafood restaurant and we talked and talked for two and a half, maybe three hours. And among other things we spoke about the implementation of the agile software development methodology at his company. If you don't know agile, let me tell you from what I learned yesterday, it is quite different from anything that I have ever done in terms of software development. I have asked Glen if he would be open to having an interview here on the project management podcast, he said, sure, so you can look forward to that today.

Cornelius Fichtner (05:59):

I enjoy Toronto. I went up to the CN tower. I stood on their gloss floor, which is 342 meters in the air. And there was nothing below me, but a piece of glass, which was quite interesting. I hooked up with my friend, Rob Brown, whom I hadn't seen in 18 years. And I'm happy to report that he is an actor, quite a successful actor here in Toronto. After that I walked over to the conference center, get my registration stuff, you know, the usual pact and name tag, the schedule, everything you really need for this concert conference. The day then continued with the first timer orientation Lynn Wheeling from the PMI welcomed us. And let me paper here, Lynn wheeling. She is the manager component and community relations were about 80 of us in that meeting room, maybe about a hundred out of 200 new time.

Cornelius Fichtner (07:04):

First time as this year. And she was very friendly and very cheerful. She first introduced all the PMI volunteers that were onsite. And then they did a little icebreaker. They had a bingo where you, as a first time, I got a bingo card with various questions on it. And you had to find somebody for instance, who drives the motorcycle. So you had to run around, get to talk to the others. And I had to find the person who drives a motorcycle and who first got his bingo card filled up, you know, five across five diagonal or five top-down one. And they actually won two free entrances to the next leadership seminar, wherever that is. I don't even know where the 2006 one is she mentioned about, I forgot. Then they looked at the schedule of the upcoming three days and they also looked at the locations of where the rooms are and all that showed us an app of that.

Cornelius Fichtner (08:04):

It was a regular, hello, first timer session. I mean, nothing extraordinary. What I missed, however, was, you know, some guidance. They didn't really tell us what you can expect. Granted Lynn talked about, you will be able to make friends for life here in the next few days. I believe that because in the project management area where we try to stick together, we know each other. So yes, I believe that we will be making friends for life here. I agree with that, but what, what are the takeaways? You know, the short term things, what am I going to learn? What's the attitude that I should have going into this. So I was missing that a little bit. And also the, the other portion of the guidance that I was missing. Like I told you, there are a very large number of the seminars that they're having roughly 24, right?

Cornelius Fichtner (08:59):

If I remember the number, correct. Well, which ones should I go and look at? I'm the programs director. Is there anything that you PMI suggests that I should focus on? What about the chair elect? What about a president who happens to be your first time, but what should they focus on? So that kind of guidance we're, what's kind of missing. Well, they're your habit? Day zero. From my point of view, my feet hurt from walking through Toronto. And even though the hotel gave me a really nice map of the town of Toronto, I feel that the PMI didn't really give me a really nice roadmap of the conference that is coming up.

Rosemary Tyler (09:45):

[inaudible] my name is Rosemary Tyler. Um, I live in the U S I've been a certified project manager since the year 2000. I've been in the business for over 20 years. And my personal model is I can, I will. I must, I shall not. How can people contact the women in project management suit? I'm very active in women, project management, SIG, and they can contact us at our website, www dot [inaudible] dot org.

Cornelius Fichtner (10:17):

The next day I got up at six, o'clock headed up to the conference center where I had a full day of seminars ahead of me. What I didn't know or didn't realize at that time. However, is it wasn't really seminars. Instead. It was discussions about issues and trends in PMI. Here's what I have to say at the end of the day.

Cornelius Fichtner (10:41):

At the end of day one here at the PMI leadership meeting in Toronto, I feel pretty exhausted. It was a full day of lots of discussions and listening and learning. And I would like to give you a brief overview of what happened today. Of course, it all started with the usual opening ceremonies and Lynn Wheeling, whom I've met yesterday at the first time as orientation started the day off. And she's absolutely excellent at working a crown. She really, really did a fine job. And she spoke again that during this meeting, your focus should be on networking and on meaningful dialogue. So that was a nice opening. And she then handed it over to, shall we call him the keynote speaker? His name was Mark Adams. He is a former NBA basketball coach. And I have to admit Mark did his homework as an NBA basketball coach, former.

Cornelius Fichtner (11:46):

He knew what project management was all about, or at least he winged it very nicely. He had also in the private industry, so he knew about project management and he was able to relate to it. He talked a lot about coaching off course, and he said that biggest role of a coach is the one on one coaching. And he made it quite clear to us folks. A team meeting is not coaching. It does not count as coaching. If you're coaching somebody. That's a one on one thing you don't just do that. During a team meeting, he talked about his friend, his friend, Josie Miller, his friend, Josie Miller is Amish. For those of you who don't know, Amish is a religious group here in the United States. And they live very simply. And when an Amish needs a new barn, well, everybody in the area comes together, chips in and they put up that barn in nine hours.

Cornelius Fichtner (12:50):

And Josie Miller is the well project manager among the Amish who put up that barn. It takes him three weeks to prepare. And he talked about what Josie does. And Josie focuses on the team. He focuses on the talents that he has available. Not everybody is a carpenter. So where do I put real carpenters? Where do I put the grunts? And he makes sure that he puts the right people into the right place. Oh yes. And even though bear Amish, they think about profit. They think, is this a profitable undertaking? Do we really want to do this? Mark also talked about the fact that what is the most important thing that you need in project management? And of course, as a coach, he said talent. When he was coaching the worst team in the United States versus one of the top 25 teams in the United States, the only difference was talent, man.

Cornelius Fichtner (13:50):

He was so much smarter and better when he had talented people on his team. Well, so that means to all of us out there as project managers find the right talent for the team. So that's my takeaway there for the opening ceremonies that we have this morning, we then moved on and we split up into the various regions. PMI splits the world into, I believe 14 regions. And my chapter is in region seven and we got together and we had the meeting was facilitated by Maria Mack Holland. PMI asked us today to look at three topics. And by the way, that's why the day was dubbed the issues day because they were really wanting us to dig deep and talk about the issues and identify issues both in the morning and the afternoon. So they wanted us to number one, identify and discuss trends. Number two, find out what opportunities and challenges these trends represent.

Cornelius Fichtner (14:56):

And number three, then identify gaps where we as components need help. The whole thing started out with quite a bit of backslapping there. Maria was talking about all the great things that each chapter did, and we gave ourselves a nice big round of applause. The various trends that we in our region came up with more or less boiled down to two words, value proposition. That was the number one thing that I kept hearing again and again today, what is the value of being a PMI member? What is the value of participating as a volunteer in PMI? So that came back again and again, we also talked about the delusion of the title, project manager, look around you in your companies. If they stick somebody in a position and they don't really know what to call him, what will they call him or her? Exactly. They will call him a project manager.

Cornelius Fichtner (16:02):

So it seems almost like the title project manager is being watered down somehow. And we felt that there needs to be some possibly standardization, some better definition as to what project manager is and what a product manager does. And we have to get it out there to people. The question of the PMP being watered down and diluted also came up. Is that the case? Because we now have so many more PMPs than we had years ago. Well, maybe, but I would like to call quote, Corina Martinez, who was also there today. And she said, when you have the PMP, that only means very few things. That means that you have some education in project management. It means that you've been able to prove that you have some experience in project management. And it means that you were able to pass the PMP test. It doesn't mean anything more.

Cornelius Fichtner (16:58):

It does not mean that you are a great project manager and think about it. If you are a CPA certified public accountant, or if you have an MBA degree or a doctorate degree, even if 200 million other people have the same degree, it's not going to water the degree down. It is a basic stepping stone for your profession. And so is the PMP. So we don't think that there is a dilution or watering down of the PMP actually happening. We also discussed other trends that we see in our region. There is the need for additional infrastructure. Some of our region components actually look at outsourcing, outsourcing bookkeeping, outsourcing the website, just to have better, more solid infrastructure right there. And we discussed the need for community outreach to talk more to vendors, to talk more to local governments, to companies in our area, go out there, bring them in, bring project management to them, get them out as your sponsors, you have to be involved in your community in order to make project management more understood better on the story.

Cornelius Fichtner (18:16):

After three breakout sessions in the 14 regions, we got back together and here are a few other trends that the other regions came up with. One was very good because I enjoyed that. It proved that we were doing the wrong, the wrong, the right thing in our chapter. And that was the need for advanced training opportunities. As you know, once you become a PMP, you need to keep it going because every three years you have to have 60 professional development units, PDs. And how do you get that? Well, you want to get trained, but you don't want to take yet another project management beginner's seminar, just so that you get one or two of those PDFs. You want to have advanced training. And this is what people are looking for. And I will be talking about how to deliver advanced training in an upcoming podcast anyway, because our chapter did it and I have done it for a whole year.

Cornelius Fichtner (19:18):

So I have some back best practices there to share with you demographics. It was good to note that our chapter is not the only one. There are many, many more it professionals now in the chapters. And we are very much looking for ways not to lose the other industries. I mean, there is construction out there. There isn't any factoring out there. We have to keep these people interested in project management in helping us in our local chapters to keep project management going the growth. If you've looked at the numbers of the PMI lately, it's skyrocketing membership is soaring, and that is an enormous strain on all the chapters. And then of course there is the PMP that has grown enormously. So the acceptance has grown of the certification and the requirement to actually, you have to have a PMP to even apply for this position has grown.

Cornelius Fichtner (20:17):

So that's a, that's a trend that everybody sees Asia and Europe. They reported that the trend that they need is to have more integration of cultural differences and local flavors into project management. And me coming from Switzerland, I can understand what they are talking about because project management here in the United States is definitely different from what I was used to back in Switzerland, branding consistency or something else that was talked about, think about it. People move around the globe these days. And when you move from a chapter in Switzerland to a chapter in orange County, California, well, you won't recognize it anymore. Everything is different, everything is done differently. So there should be some kind of a branding consistency, not just for folks like me. Also for global companies, you have international companies that are supporting the PMI. And if there is not a global brand logo recognition, somehow that everybody, every chapter kind of adheres to, and it's difficult for these companies to realize, Hey, we're supporting the same group here.

Cornelius Fichtner (21:27):

We're still on track with what we're doing. The agent region also spoken by the way the agent region comprises one third of the world's population. And the interesting thing that she mentioned was that the PMI in the agent region grew with it. And now they're actually embracing the other industry. So they are now bringing in construction and bringing in manufacturing quite different than what the PMI actually started out on. It started out in construction, manufacturing it now it looks like it is taking over the PMI world. And the final one I would like to tell you about here is from the Caribbean and South America. They talked about the fact that they are in places where sometimes natural catastrophes hit. So what do you do as a chapter? What do you do as a business continuity plan? What if your town is struck? How do you bring the chapter back up?

Cornelius Fichtner (22:29):

So they are looking for some help in that region. And also they need some more help with bringing job opportunities to their members there. So that was the morning session from nine 30 to 1130, about the component leader, learning and sharing by region. We then moved on and in the afternoon, once again, we talked about issues and this time we broke up into the component, learning and sharing by size. So we broke up into barriers, size groups. My chapter at this point has roughly 1500 members, but I joined a 2000 member group because we expect to, to be there quite quickly. And what happened? The two gentlemen, unfortunately at the, I didn't make a note of their names. The two gentlemen who led this group, the session, they first showed us the results of the component maturity assessment. This was a survey which was presented to all the components worldwide by the CS mag, the components services member advisory group.

Cornelius Fichtner (23:40):

That's a mindful CS mag. And they showed us the results of this. This was quite a different and interesting session because everything that they showed was challenged. The validity of the questions that were asked were challenged. The results were challenged. The interpretations were challenged. It was quite astounding for me as a newcomer to see that and tip of the hat to the two gentlemen who facilitated this meeting, they kept their cool, they gave very good calm responses. They consider that they suddenly found themselves in the defensive and they handled the situation very, very well. I learned later on that the other meetings were quite similar that even the same kind of responses came that even the statistical validity was questions of everything. It seems to point all into the same, same direction here. I'm not going to go into the details of this meeting as much as I did before.

Cornelius Fichtner (24:46):

Instead I have the following two comments. Some people take this fall too seriously. You might believe off this session here with the 2000 and more member chapters, that this is some people's real job. And for me as a first timer, it was quite off putting. And I believe that it was the same for others too, because after we had a breakout session and came back, the room was half empty and people left because they probably didn't want to be in this Slayer fast as it was. So folks learn to relax a little. This is not your whole life. Second, the intensity of these reactions and the discussions, however, showed that there is quite clearly a dissatisfaction with PMI out in the components. And there is definite need of a way, a structured, a clear way in which this dissatisfaction from the components is gathered aggregated and then presented to the PMI.

Cornelius Fichtner (25:58):

And then the PMI has to listen at need, has to take action. This is what I have taken from this, this particular session. Next the day ended with the graduation of this year's class of the leadership Institute. The leadership Institute is now in its fourth year. It's a four year old training initiative by the PMI and each year 25 volunteers from the PMI volunteers have chosen to attend this PMI leadership Institute. We had a couple of opening speeches by Louis Merican, the PMI, uh, chair, and by the PMI CEO, Gregory [inaudible] of course, both of them focused on the benefits of the leadership Institute. And then Gregory [inaudible] continued to introduce the next level of a PMI leadership Institute. It is now going to become PMI learn from what I was able to gather from the very short presentation that he made. I will may have to revise the statement.

Cornelius Fichtner (27:07):

I lay to point when it's really out there and we can all read up on it. It is now a online e-learning tool where every PMI volunteer and PMI leader can assess their own capability and their own needs, and thereby define where they need additional training. My hope really is that the PMI was able to capture the best top of what these four years of the leadership Institute has given them, and that they were able to translate this into this new PMI learn. I'm happy of course, to report that Christine Monson, my boss has graduated today from this leadership Institute. And I'm also happy to report that Cornelius Von inc. Yes, a gentlemen who shares my first name from Holland. He is, I believe that he has also graduated from the leadership Institute today and he had the guts to wear a red jacket. Exactly the same thing that I would have done, I would have graduated with a red jacket. So that was, that was good to see. I would like to end this first day with a quote from Peter Monkhouse and he said, I try to add value every day in everything I do. I believe if we can all do this as PMI leaders and PMI volunteers, then we can take the PMI to the next level.

Speaker 6 (28:49): [inaudible]

Brent Felsted (28:53):

Hi, it's Brent Felsted from orange County, California. I'm second time as the leadership meeting before it was the college presidents, and I've enjoyed this trip to Canada, a great deal. Some of the things that I've gotten is just interacting with the other chapters, talking to other people, finding out how they do things. That's what I found most valuable. Thanks. I hope you have a great, a great conference

Cornelius Fichtner (29:24):

In the two days following the recording of the review, you just heard, I spoke to many people at the meeting about their opinion of day one. Most of them rolled their eyes about it and said that in particular, the afternoon was just a waste of their time. The should never

Cornelius Fichtner (29:42):

Have presented the results of the survey at this early stage and that the PMI shouldn't instead have, let us discuss that quote real unquote issues that components face today that would have been much more valuable for everybody. That's about it for today. Thanks for listening in my next show, I will, of course, feature day two and three of the PMI, 2005 leadership meeting. I will give my review of the presentations I attended. I will share the gold nuggets I found in the seminars we'll do with you. You will hear more voices from other people, and I will give my overall verdict as always. You can find us on the This email address is being protected from spambots. You need JavaScript enabled to view it.. And finally, we have this good project. Management is not so much knowing what to do and when to do it as knowing what excuses to give and when to give them with that. Think about volunteering for your local chapter until next time.

Above are the first few pages of a computer-generated transcript with all its computer-generated quirks. A human-generated transcript is available to Premium subscribers starting with episode 136.

Episode 001: Introduction

Play Now:

Allright! After three weeks of planning, learning and fighting with inadequate technology I have finally finished the first show. This is the introductory show of The Project Management Podcast in which I tell you, why you should care, subscribe and listen to the future shows. I am introducing myself, my background in project management, how I got the idea of creating The Project Management Podcast and what kind of shows you can expect in the future.

In the show, I mention that I found some freely available audio content discussing project management. You can find the links to these in my post from August 18, 2005. The music used on the show is by Rimela https://go.to/rimela (This legacy link is no longer active).

The next show(s) will be recorded at the 2005 PMI® Leadership Meeting in Toronto, which lasts from September 8.-10. 2005. I will not be able to record anything during the actual presentations. Instead, I will make this a good and educational review for those PMI chapter boardmembers out there who are unable to attend.

Episode Transcript

Below are the first few pages of a computer-generated transcript with all its computer-generated quirks.

Cornelius Fichtner (00:11):

You are listening to the project management podcast. We bring project management topics to beginners and experts. Find us on the web at PM. podcast.blogspot.com or send your emails to This email address is being protected from spambots. You need JavaScript enabled to view it..

Cornelius Fichtner (00:29):

Hello, and welcome to the first show. This show was recorded on Saturday, the 3rd of September, 2005. And today I'm going to tell you why you should care. It's the introductory show of the project management podcast. And I want to tell you about what's coming. I have recently learned from a journalist that when in journalism, one of the questions you have to ask yourself is who cares, who cares, what you write about, or in my case, who cares? What you talk about. That's why I want to take a few minutes today and explain to you why you should care. And listen to the show. I will talk about the who, the why, the what the, why not. And also the win let's start with the hoop. My name is Cornelius Fichtner, as you can probably tell by my accent, I am not a native English speaker. I'm originally from Switzerland and I learned my English in Oxford England.

Cornelius Fichtner (01:24):

And when I returned home, I had an impeccable British English accent. I married an American citizen, and now I live in Southern California. And you might say that my accent at this point is a bit confused. I've been working in project management for the last 15 years. I started out as a software developer in COBOL, and then I moved over into organizational planning as it was called. It's just project management by another name. I've worked for a consulting firm. I've worked in a supermarket and then I moved over into an internet startup software company, building websites. Now I'm in the financial industry. My projects were in Switzerland, Germany and the United States. And they have all been small to medium sized projects, roughly three to 15 members. And they were anywhere from three months to one and a half years in time. I'm a member of the PMI, the project management Institute.

Cornelius Fichtner (02:18):

And I'm also a board member of the local chapter that PMI IOC project management Institute of orange County. Why am I doing this? Well, I got an iPod for my birthday and I discovered audio books and realized, Hey, I'm a lot better at listening than I am at reading. It's so much more entertaining. You can do it while driving to work. You can do it while folding your laundry. So I began looking around for audio content on project management. I found some with rather good quality, but nothing in the sense of a podcast that is regular and always updated. And by the way, you can find links for these files at pmpodcastdotblogspot.com. So the idea of creating the project management podcast popped up into my head and I discarded it. It came back two weeks later and I discarded it again. And when it showed up for the third time, I finally said, okay, I have something here.

Cornelius Fichtner (03:17):

I've got to do this. And here I am recording the first show of the project management podcast. Next on the list. What, what are you going to hear? Let me start out by saying what you will not hear. This is not a PMP preparation podcast. So if you are planning to take the PMP exam soon, don't listen to this podcast. I will be going out into the field. I'll be bringing interviews with people with practitioners, and that's not what the BMP test is about. The PMP test is going to test you on the theory, the methodology of project management and not how people are doing it in the field. You may also have noticed that this sound quality is not radio sound quality. At this point, I'm using the equipment that I have and the quality that I have is what you get. It will improve over time.

Cornelius Fichtner (04:13):

I'm sure when I buy new equipment and I'm also at this point, not able to do any phone interviews. Here's what you will hear. My goal is to bring project management topics to beginners and experts alike. So we'll hear a mix of quite a few things. I have a colleague who does a lot of work with project managers in Russia. And I have a colleague who does a lot of training in China. So it's going to be interesting to hear what those two will have to say about the differences of project management in these places. I'll also be talking to the president of the PMI, IOC, the project management Institute of orange County chapter. And we will hear from her what challenges she has in leading a chapter with roughly 1400 members. Two days ago, I had lunch with a gentleman who recently became certified in Sarbanes Oxley, and he's also a PMP and he will be talking to us about what the socks, the Sarbanes Oxley law in his view is going to do to project management and how it will change it.

Cornelius Fichtner (05:15):

And as you know, the pin box has recently been updated. So I'm going to talk to a colleague of mine who does a PMP preparation workshop, and we'll be hearing from him how he is going to change the PMP prep workshop because of the many changes that have gone into the pin book. Some other shows that are on my list are risk in winemaking. That's going to be an interesting one. I'll be talking to you about volunteering in the PMI. What can you do? And what will it do for you? I have organized a local seminar for about a year, which we call the advanced topics seminar, which helps many PMPs in the region here to get their PDs. And I'll be talking to you about best practices that I learned in organizing such a monthly recurring seminar. I'm hoping to take quite a few speeches because around this area here, we have quite a few speeches from project managers on a regular basis.

Cornelius Fichtner (06:17):

And I'm hoping to get their release that I can record it and bring it to you here on the project management podcast. My number one love in project management, however, has always been methodologies. So I'm going to probably look at a, quite a few methodologies compared them, bring them to you, give you the ins and outs. I'll also be bringing you the ins and outs on various project management websites, which ones are good, which ones are bad, and which ones are just plain ugly regarding the, when at this point, I don't really have a set schedule, expect irregularly scheduled shows at first. And once the ball gets rolling, I hope to produce shows on a much firmer schedule. Now that was the who, why, what, what not? And the, when of the project management podcast, I hope I have whetted your appetite and that you will come back. Thanks for listening. The next show. It will be coming from the 2005 PMI leadership meeting in Toronto. I'm going there next week. I'll be staying up there for about five days and the seminar is three days long. I hope to produce several shows from up there telling you my experience as a first timer at a leadership seminar. Again, you can find this on the web at pmpodcast.blogspot.com or send your emails to This email address is being protected from spambots. You need JavaScript enabled to view it.. Finally, we have this. Remember that there are no good project managers, only lucky ones with that. Enjoy your projects and until next time. Bye bye.

Above are the first few pages of a computer-generated transcript with all its computer-generated quirks. A human-generated transcript is available to Premium subscribers starting with episode 136.

Cornelius Fichtner
Cornelius Fichtner
Cornelius Fichtner, PMP, CSM, is the host and the author at The Project Management Podcast. He has welcomed hundreds of guests and project management experts to the podcast and has helped over 60,0000 students prepare for their PMP® Exam. He has authored dozens of articles on projectmanagement.com and PM World 360. He speaks at conferences around the world about project management, agile methodology, PMOs, and Project Business. Follow him on Twitter and connect with him on LinkedIn.

Project Management for Beginners and Experts

Going beyond Project Management Professional (PMP)®, PMI Agile Certified Practitioner (PMI-ACP)®, and Certified Associate in Project Management (CAPM)®

PM PrepCast, Agile PrepCast, PM Exam Simulator, PDU Podcast, PM Podcast are marks of OSP International LLC. PMI, PMBOK, PMP, PgMP, PfMP, CAPM, PMI-SP, PMI-RMP, PMI-ACP, and PMI-PBA are registered marks of the Project Management Institute, Inc.

Copyright © 2008-2025 OSP International LLC. All Rights Reserved. Our Privacy Notice: http://www.osp-international.com/privacynotice

Advertisement