Mayte - Great post! This Thread is getting more and more interesting...
George, I'm thinking about writing a book about how to keep your ethicals while looking for a job. ;)
...
1 reply by George Lewis
Mar 22, 2017 11:24 PM
George Lewis
...
Mayte - that's really interesting...
(1) I have been tempted to add only the portion of knowledge the recruiter is looking for, is that ethical? or should I add all my information even if the Job does not requires it. For example, If someone is looking for a PMP, but I also have an PHD (hypotetical), I really want the Job but do not want the manager recruiting to feel I will be a challenge to him. What do you do?
(2) Some others have certificates and swear in their resumes that they have certifications.
(3) Some others add languagues and tools they've barely heard about.
(4) Some others skip works in their
Saving Changes...
George LewisProgram/Project Manager| DXC Technology CompanyHeredia, Costa Rica
Mar 22, 2017 6:14 AM
Replying to Drew Craig
...
George, I started to write that, then realized the question was what not to include. : )
Maybe another thread?
Andrew - as suggested I created another thread on the other side of the question.
George LewisProgram/Project Manager| DXC Technology CompanyHeredia, Costa Rica
Mar 22, 2017 3:14 PM
Replying to Mayte Mata Sivera
...
George, I'm thinking about writing a book about how to keep your ethicals while looking for a job. ;)
Mayte - that's really interesting...
(1) I have been tempted to add only the portion of knowledge the recruiter is looking for, is that ethical? or should I add all my information even if the Job does not requires it. For example, If someone is looking for a PMP, but I also have an PHD (hypotetical), I really want the Job but do not want the manager recruiting to feel I will be a challenge to him. What do you do?
(2) Some others have certificates and swear in their resumes that they have certifications.
(3) Some others add languagues and tools they've barely heard about.
(4) Some others skip works in their Saving Changes...
Edward DanielsProject Manager| IndependentGlen Burnie, Md, United States
In my humble opinion, most PMs work in the organizations that have an established PMO that manages multiple projects under a portfolio. I haven't seen it happen where a project fails at the last minute, there are indicators from the beginning and as PM, our primary responsibility is to inform, consult and advise all stakeholders of all going-ons. A project failure is not a bad thing, we learn from them and they are called "Lessons Learned". I wouldn't report a project failure on my resume. A project can fail for any number of reasons, as long as a project doesn't fail because the PM fell asleep on the job, i think it is a waste of everyone's time to list that on a resume. As a mid-level PM, organizations i have worked with have organization cultures that take away some of my personal call on ongoing projects. When looking to hire a PM, i personally look at what they have achieved, not just a list of tasks they have performed. Write a narrative that helps your interview know what you have done and willing to do moving forward. For example, I would like to read, how a PM led a team of 5 analysts in deploying 500 workstations over say a 3 or 4 week period than "i supervised 5 analysts on a workstation deployment project".
This gives me an opportunity to ask leading questions about -
1. Why it took 3 or 4 weeks to get 500 workstation deployed.
2. Any particular challenges or opportunites that the PM learnt from this deployment.
3. Is there anything they would want change in their current or previous PMO way of doing things.
4. How do they deal non-flexibility when it comes to organizations with baked-in cultures.
This is how a potential PM can truly know what they are walking into. It is not always about what not to include, a 2-page resume is very difficult but not impossible. Depending on how long you have been working, my advise is have a 2-page resume that is straight to the point and a more detailed 3-5 page resume that details more. When asked, present both and let them know one is a 2-page while the other 3-5 page details more about you. FYI - it has helped me tremendously in trying to get my point across to potential employers. Saving Changes...
Edward DanielsProject Manager| IndependentGlen Burnie, Md, United States
Mar 21, 2017 10:09 AM
Replying to George Lewis
...
Would anyone include a project failure in your resume? this is a tricky one...
Hi George,
It is not tricky at all. Let's employ statistics here, except your project failures are statiscally significant, why bother? I mean if you have been involved in say 10 projects and 1 of them failed, i would say 90% success rate is an A and you should bring up what you learned from the failed project. Now if you have a 60% failure rate, that is statistically very significant and we as PMs are supposed to be ethical and truthful in all our dealings. While you are not encouraged to list them on your resume, when interviewing you are supposed to bring it up and i would respect someone who presents it in a way that they have learnt something. For example, you can explain how the organization responded to the 60% failure rate. Many organizations have measurement standards that are just a little askwed, so a 60% failure rate may be a tad higher than the actual. So to everyone, you are not doing anyone favors when you list project failures. You are supposed to have learnt something useful from them to bring to future projects or employers. Saving Changes...
Edward DanielsProject Manager| IndependentGlen Burnie, Md, United States
Mar 21, 2017 9:09 AM
Replying to Wade Harshman
...
What not to include in a project manager resume?
"I screwed up an important project that cost my organization millions of dollars, and now I need a job."
Hi Wade,
You said "I screwed up an important project that cost my organization millions of dollars, and now I need a job." I don't have much to go on but have you looked at being a consultant? I don't know what happened or why you think you screwed up an important project. There should be checks and balances, along with reporting that should have indicated the project is not going as planned. If you can answer the questions below (5Ws and H) -
What happened?
Who is involved?
Where did it take place?
When did it take place?
Why did that happen?
How did you screw up?
This is not about shifting blame, but you may just realize that you didn't screw up at all. As PM, we should be aware that we have stakeholders to help us wade through the shallow and deep waters of every project, it isn't about just directing the teams. It is about engaging everyone, if there is any risk, no matter how low the probability is, we should add it to the risk register and communicate it. The plug may be pulled on a project if the business case no longer supports it, that is not project failure. It is actually smart, we all know and remember the saying "Penny-wise, Pound-foolish". How many times do we really figure that into our projects?
Product Operations Program ManagerBarcelona, Cataluña, Spain
In addition to all insightful comments, and going back to the original question - what to not include - I'd recommend not to include too much detail which may overwhelm the reader - provide high level information and back it up with figures.
Headhunter will then most likely ask for a separate document that dives further into a specific or set of experiences that closely relate to the opportunity. Saving Changes...
Florent BIGUEURCompliance Officer, VP| Credit Agricole CIBParis, France
Mar 21, 2017 10:09 AM
Replying to George Lewis
...
Wade - you're correct!
Which makes me ask, would you include a project failure in your resume?
Most of the recruiters check the timeline in your resume. How do you justify the time if you spent 3 years on project that do not appear in your resume ?
As my point of view, if it is a recent experience, it is better to put it in the resume, explain the failure and what you have learned from this (do not put responsability on others).
However, I agree with view on too old or not relevant experiences for the job targeted. Saving Changes...
LORI WILSONRETIRED - Technical Project Manager| RETIRED - LifePoint HealthClarkston, Wa, United States
Mar 21, 2017 10:16 AM
Replying to Aaron Porter
...
I wouldn't include a failure in my resume, but I would be prepared to talk about it during the interview; the question will most likely come up.
I agree with Aaron's recommendation not to include a failure in your resume, but be prepared to talk about it. You can definitely refer to what you learned from a failed project experience and how you are more prepared and knowledgeable to help companies avoid future project failures.
...
1 reply by George Lewis
Mar 25, 2017 12:53 AM
George Lewis
...
Lori - that's makes me ask again, what is really a project failure?
Community Champion
