Sunday, January 15, 2017

Common Project Mistakes

Common Project Management Mistakes

Project Management Mistake No. 1: Not Getting Executive Buy-in.
Solution: "Somebody at the higher levels of the organization needs to own the project from start to finish and be personally vested in its success, When [a project] has no clear head, things tend to fall apart."

Project Management Mistake No. 2: Putting Too Many Projects Into Production at Once.
Most managers think that they can get more done by starting all projects at once, but in reality, it's counterproductive. "Multitasking slows people down, hurts quality and, worst of all, the delays caused by multitasking cascade and multiply through the organization as people further down the line wait for others to finish prerequisite tasks."

Solution: "To stop these productivity losses, a good first step is to reduce work in progress (WIP) by 25-50 percent," he says. "This reduces the back and forth and makes managers and experts more responsive in dealing with issues and questions. Though counter-intuitive, reducing the number of open projects by 25-50 percent can double task completion rates."

Project Management Mistake No. 3: Too Many changes to Project Scope. 
Most managers think that in today's time and space the projects should be agile and adaptable. Yes, if the objectives are to be progressively met and stakeholders have agreed to it. Else even with proper change management we see lot of time, cost and scope getting messed up. The overall satisfaction, moral and intensity of team as well as users is challenged.

Project Management Mistake No. 4: Bottle necks due to resource constraints. 
Companies rarely have sufficient resources to staff all projects concurrently. As such, projects compete against each other for resources, and people are often assigned to several projects at the same time. Those with special expertise of scarce skills may be in high demand, causing bottlenecks.
Project Management Mistake No. 5: Inability to Maintain Focus
Too many of us allow day-to-day demands to overshadow our truly important objectives. Instead, we allow ourselves to be distracted by urgent, although less important matters. Bogged down with emails and derailed by meetings, we are unable to concentrate on strategy. 

This problem can be overcome by breaking down larger strategic goals into more manageable parts. These smaller components will be easier to integrate into your daily routine. It is also helpful to keep your product vision front-of-mind by keeping it visually prominent through printouts posted around the office. It is also helpful to weigh the cost versus benefit for each decision before committing to a product change. This analysis can spare you from paying twice for the same real estate.

Project Management Mistake No. 6: Inability of managing key Stakeholders Support
Levels of supportiveness can range from active opposition to active support. For each of the important stakeholders, the project team needs to understand the stakeholder’s current level of support and then determine a realistic optimum level to facilitate the project’s success.

What is a realistic optimum varies, for example, environmental activists can never be realistically expected to support a new road through a wilderness area; in this circumstance the realistic optimum may be passive opposition (as opposed to active opposition) and a communications plan developed to negotiate an outcome that the environmentalists can live with.

On the other hand, your project sponsor should be an active supporter; if the person is merely a passive supporter communication needs to be planned to engage the stakeholder in actively supporting the success of her project.

Achieving either of these objectives needs open communication. If the stakeholder is unwilling to communicate—either because they really don’t like you or they are just too busy—you need to devise ways to open channels. This may involve using other stakeholders in the network around the project to open the communication, using someone else on your team as the messenger, changing the way you communicate or just plain persistence.










Saturday, September 24, 2016

Why Projects Fail?

Classic Mistakes

Analysis of the examples in the “Catalogue of catastrophe” reveals the most common mistakes.  Given the frequency of occurrence, these mistakes can be considered the “classic mistakes”.  The following list outlines the most common themes and provides links to examples;
  1. The underestimation of complexity, cost and/or schedule
  2. Failure to establish appropriate control over requirements and/or scope
  3. Lack of communications
  4. Failure to engage stakeholders
  5. Failure to address culture change issues
  6. Lack of oversight / poor project management
  7. Poor quality workmanship
  8. Lack of risk management
  9. Failure to understand or address system performance requirements
  10. Poorly planned / managed transitions

  1. The underestimation of complexity
    In Powerpoint all projects can be made to look simple, in reality the situation is much more complex.  Failure to see those complexities leads to the underestimation of schedule and budget, plus a host of other ailments. Examples
  2. Failure to establish appropriate control over requirements and/or scopeSince mankind first started looking into the failure of technology projects, changing requirements have been a reoccurring theme.  The following examples illustrate the point.Examples
  3. Lack of communicationsCommunications are the oil that allows effective decisions to be made across the team.  Where communications breakdown, the effective of the decisions being made can rapidly turn bad.  Examples
  4. Failure to engage stakeholdersStakeholders are the people who need to provide key input to the critical decisions made in the project. Failure to engage stakeholders effectively is the fast-path to disaster.  Examples
  5. Failure to address culture change issues
    Although technology is the focus of many projects, failure to recognize and address culture change can derail the deployment of a new system.  Examples
  6. Lack of oversight or poor project management
    Delegating is easy, but unless there is an appropriate level of oversight projects can quickly go off the rails. The following examples illustrate what can happen when management’s asleep at the wheel.  Examples
  7. Poor quality implementationsIndividual bugs may be fixable, but when the number of bugs is allowed to run rampant the entire project can be put in jeopardy.  Examples
  8. Lack of risk managementProjects are full of uncertainties and failure to identify or manage those uncertainties appropriately can rapidly see them turn into serious problems and issues.  Examples
  9. Failure to address performance requirements
    Performance requirements are one of the non-functional requirements a system needs to satisfy.  Many projects fail to define their non-functional requirements (especially performance) and that failure leads to systems that are operationally unusable.  Examples
  10. Poorly planned / managed transitions
    The work needed to successfully transition a project from the project team to the operational environment or market place once the project is complete is an area that often gets overlooked. Failure to properly think through that transition can quickly turn what might have been a project success into chaos.  Examples
Note that although the mistakes outlined above represent the common problems that occur in projects, the problems can be triggered by many different processes.  For more information on the triggers of project failure and the behavioural patterns behind failure try the following pages.
  1. Trigger events
  2. Behavioural patterns

Sunday, December 13, 2015

2 Steps to Greater career satisfaction

2 Steps to Greater career satisfaction requires some major accountability, so you must:

1. Get clear on your strengths and specialties. Want to be paid your worth? Then stop claiming you’re a jack-of-all-trades. Employers pay top dollar for specialists who can prove they will save or make them enough money to justify their expense.

2. Identify a problem (bigger than you!) that you wish to solve. Passion for work is the intersection of a problem you wish to solve AND where you get to use your strengths and specialties to solve it. Find the thing you wish to fix--and then seek the employers in the business of fixing it.

My Personality traits & strenghts

My personality trait and strenghts:

Visionary 20 %
Educator 15 %
Researcher 15 %
Mentor 15 %
Super-connector 10 %
Builder 10 %
Warrior 10 %
Optimizer 5 %

Visionary
Thinks big-picture and conceptualizes ideas to motivate others to action.
Are you: Capable of shaping a vision for those that can’t see the possibilities.
Can you: See the end before the beginning. Able to assess from a bird’s eye view.
Do you: Have a long-term mindset and plot your course accordingly.

Educator 
 Closes gaps in knowledge and to ensure staff is clear in their roles and goals.
Are you: Good at organizing thoughts into oral and written communications to motivate and train others.
Can you: Take control of an idea and choose the right method for communicating it.
Do you: Excel at wordplay and use communications skills to guide conversations.

Researcher
Gathers data and information to assist in better designs and decisions.
Are you: Detail-oriented and structured in all your work efforts.
Can you: Assess and locate the right information and resources needed to complete a project.
Do you: Enjoy getting things organized and building routines for consistency.

Mentor
Coaches performance and helping others develop their own skills.
Are you: Seen as a thought-leader and highly successful in your industry.
Can you: Coach others to new levels of awareness and performance.
Do you: Enjoy helping people develop their skills and increase their confidence.

Optimizer (I am NOT)
Assesses, analyzes, and maps out improvements that directly save or make money. Are you: Someone people rely on to make sound financial decisions.
Can you: Assess a business or project and immediately see ways to save or make money.
Do you: Gain satisfaction from knowing your work makes the business more profitable.

Friday, December 11, 2015

Good stuff for PM Resume

Good stuff for PM CV
RESPONSIBILITIES:
  • Manage large and complex IT projects throughout the entire lifecycle, coordinating the efforts of vendors, internal team members, and other business units
  • Perform business analysis activities at the strategic, operational, and organizational level; working with key users in the continual improvement of business processes
  • Represent the IT program team internally through
    • stakeholder interviews
    • participation in cross-functional meetings
    • content development for executive presentations
  • Perform ongoing review and analysis of program strategy and methodology
  • Evaluate and manage vendor partnerships
  • Identify, escalate, and resolve issues critical to program success
  • Contribute to strategic planning, monthly status reporting, budgeting and other assigned special projects as required by position
  • Manage the recruitment, retention, and career development of internal staff
  • Manage, mentor, and lead internal and external staff as defined in project structures


QUALIFICATIONS AND SPECIAL SKILLS REQUIRED:
  • Seven to ten years of related business experience; Consulting preferred
  • College degree; MBA or equivalent work experience preferred
  • Eagerness to contribute in a team-oriented environment
  • Ability to work creatively and analytically in a problem-solving environment
  • Demonstrated leadership experience, ability to set direction and vision, build consensus around recommendations, work with a team to meet objectives
  • Demonstrated ability to manage staff remotely, across multiple time zones
  • Excellent communication (written and oral) and interpersonal skills; ability to interface and influence all levels within the organization, including facilitation, consulting, negotiation, presentation, nd coaching.
  • Excellent project management and coordination skills working with multiple stakeholders across several technology platforms and business areas
  • Strong technical skills and experience working end-to-end through all phases of the SDLC process in medium to large scale IT Projects
  • Demonstrated ability to execute basic financial analysis, such as ROI
  • Expertise in MS Office - Excel, PowerPoint, Word
  • Professional Characteristics/Motivators:
    • Motivated by the desire to make a difference in the business, to work with a highly talented set of peers, and to work on interesting projects
    • Outstanding work ethic; displays a high sense of urgency to resolve issues quickly and efficiently
    • A high sense of responsibility to our customers, our users, our colleagues, and to the quality and timeliness of one's own work
    • Willingness and flexibility to jump into the details to get the job done
    • Ability to work in an unstructured environment and the confidence to set a direction with limited direction (comfort with ambiguity)
    • A continual desire and capability to learn
    • Highly organized and detail oriented
    • Personal philosophy to lead by example
    • Customer Focused
    • Very professional presence
    • Ability to articulate issues, build consensus around recommendations, and define next steps

Sunday, May 12, 2013

Project Management Interview Questions

“TELL ME ABOUT YOURSELF...” (Have something short and sweet here. There is a large group of interviewers that like to challenge (ahem, torture) you by starting with this open-ended question.)

“WHAT HAVE YOU BEEN DOING since your last job?” (If you’ve been out of work more than a month, be ready for this question. Hint: “Watching the History Channel” is a bad answer.)

"WHAT ARE YOU LOOKING FOR in a new job?” (This should work with your answer to the similar question, "What interests you about this company?” Both answers can be used to express your goals and show the homework you’ve done on the job.)

“I see you worked at Acme, Inc. for 5 years. WHAT TYPES OF PROJECTS did you manage?” (Prepare example projects from your past that you can speak to in moderate detail for this question. Your projects are your portfolio.)

“WHY DID YOU LEAVE Acme, Inc.?” (Just the facts and move on. Shoot no arrows, raise no eyebrows. They are figuring out if they want to work with you and/or if you are a criminal.)

“WHAT WAS YOUR GREATEST PROJECT ACHIEVEMENT?” (This would be a good place to focus on something that helped the company bottom line. Leave off your cool “Glee Club” accomplishments.)

“Tell me about a PROJECT THAT FAILED.” (If they asked the “achievement” question above, you can be sure that this one is coming next.)

“WHAT WAS THE TYPICAL SIZE AND BUDGET of your projects? How did you manage budgets?” (Make sure you have high, low and average examples. Estimate based on resource and other costs if you don’t have exact numbers.)

“WHAT IS THE FIRST THING YOU WOULD DO when assigned a new project?” (I’ve gotten this question, to my surprise, many times. While it may depend on the project, it’s best to cite something specific from your methodology of choice.)

“What SPECIFIC STEPS AND TECHNOLOGIES did you use on a typical project?” (This is a drill-down question customized to the job requirement details. If ITIL was mentioned in the reqs, for example, be ready to speak some ITIL detail here!)

“TELL ME WHY YOU'D BE A GREAT FIT for this position.” (This can be asked a number of ways, but the gist of it is this... why are you a match for not only the job, but with the company and clients with whom you'll be working.)

“WHAT QUESTIONS DO YOU HAVE for us?” (I usually have a LOT of questions. However, I’m learning to trim what I ask to the time left and how glassed-over interviewer’s eyes may be. If you earn a second interview, you can ask questions later.)

Surprisingly, some common questions I expected like “What is your greatest weakness?” have not been asked. Also, I have rarely been asked about any jobs prior my last two. I may be yearning to talk about my Peace Corps experience... but they don’t have time, or don’t care!

How would you manage conflict or a tough sponsor is a common one I have been asked.

Often conflict on a project is posed as an example... either a "tough sponsor" as you noted, or a problematic team member or project that is behind schedule and/or over budget. An applicant should definitely be prepared to answer how he/she would deal with any of these issues.
• Tell me about the main milestones of a project you have done.
what are the most important things you have to take care about in a project and why
Tell me about a lesson learned from a failed project

Describe to me ,in depth, a Project that failed and how so?

If you were given the project of building a house from scratch, what would be your thought process and how you would define its life-cycle?
yes, the "failed project" one has come up, and it can be tough. Best to have at least 2 examples (one big, one small) ready to go for that one. Seems to often be followed by, "What did you learn from that experience?" or "What would you have changed to save the project?"

I haven't been given the "build a house" or "build a car" analogy type question, yet. I did once work with a developer who complained about people wanting to buy shiny wheels for the car before building the frame, though. Usually, with some colorful expletives thrown in!
what were the challenges (failures, bad team member or delivery slippages ) during the project pahse and what did you do to mitigate them? also, sometimes I am asked - what you could have done differently ? --- both of these hint towards some talking about Risk and Stakeholder management.
• Personally I find using "case interviews" as a very effective tool for evaluating project managers. I usually use a specific problem for specific business with specific objective. Then I ask the candidates to try to structure the solution / make a plan and describe what resources/expertese they need to get the project done -- It allows me to judge how they think about a problem, how would they structure a solution, do they know when they have to rely on someone elses help - kind of simulates the real world that they will be thrown in... (Hint: to use Chris's example buying the shiny wheels before you build the frame is what ocassionally happens in a case... ) You can also see what priorities people have in their mind (e.g. Had someone building a airport in New York whose primary concern was land regulation.. before need, before cost, before possibility to do it from an engineering perspective, before location availability.. guess what? He was working for the government! I did not even need to look at his resume... ) I also ask very specific question such as "How would you go about X... e.g. picking the location for that airport...?" It allows me to judge whether the person can switch between big picture and the details.. which is important for a project manager who deals with all levels of stakeholders.

• Personally, I like your way of giving an case example to solve, as opposed to asking the candidate to cite one from their past. A couple weeks ago I was asked to "provide an example of specific information I had on a project, that I chose to hold back from the team or management, and how that affected the project outcome." Now, I'm prepared with many examples and projects, but in a multi-person interview, to try and come up with an actual real example for something as specific as that stumped me for (more than) a few seconds, and my answer was less than exceptional.

I think that same question could have been presented as an example like, "Imagine your QA lead just told you about her concern regarding one of the developers... what would you do with this information?" Asked that way, which is the way you present it as a "case interview" I believe would have been just as effective as requesting a specific example from my past.

a. Do you have any experience of recovering a troubled project. What did you do, why that particular approach, etc.
b. As a people manager, which one you think is challenging and why - managing a top performer or poor performer.
c. Do you have experience in managing reward and penalty, tough SLA based project. How did you ensure SLA adherence and sustenance.
d. How do you manage attrition and knowledge retention.
e. How do you expedite delivery date and what are pitfalls in ensuring the success.
f. Your experience in managing multi-cultural team environment.
g. Your experience in adopting latest project management methodology like Lean, Agile and how does it relate to conventional project management methodologies.
h. Your experience in quality management, quality audits, metrics collection and analysis.

• I'm new to to the PM field and I am excited to say I have a phone interview coming up for a project coordinator position. Because this is a new career path I am choosing, can anyone offer any advice or suggestions for my upcoming phone interview as well as any questions employers have asked in the past when you were entering as an entry level...
- How would you establish relationship/trust and manage the resources that are based in multiple offshore locations.
- Describe examples of significant scope change / cost overrun / vendor slippage. What actions did you take? What would you have done differently?
• Tell me/us about a time that you have had to manage situation with a difficult/non-preforming resource/person and what did you do to resolve the issue.

What do yo do when faced with unreasonable requests from senior management.

How do you manage/negotiate with stakeholders who want to introduce a change but will not listen to an increase to time/budget.

- Do you have any experience of RECOVERING A TROUBLED PROJECT? What did you do, why that particular approach, etc. (I've had some version of the "troubled" project question, usually given in the form of an example, in every interview.)

- As a people manager, which one you think is challenging and why - MANAGING A POOR PERFORMER or a top performer. (I've not had this question, but I have been often asked about a "problem" team member situation. How to deal with a "top performer" is actually an interesting question!)

- Your experience in managing (and establishing relationships) in MULTI-CULTURAL TEAM ENVIRONMENT. (I've only been asked this, obviously, on those projects with offshore or remote teams for which I've applied. If there are people on the team in other places, speaking various languages, you can be sure to get this one. I hope to be able to work with multi-cultural teams, actually. Ciao!)

- Your experience in ADOPTING LATEST PM METHODOLOGY like Lean, Agile and how does it relate to conventional project management methodologies. (If this is listed in the job description, it will be asked. If you see "CSM", "Agile", or "Scrum" in the description, there is likely to be a very specific question that will test your knowledge of those methods. Same goes for Lean, Six Sigma, etc.)

- Your experience in QUALITY MANAGEMENT, QUALITY AUDITS, METRICS collection and analysis (If you are applying for a job that manages SDLC and interacts with developers and QA teams, this can be expected. I do not know if it is asked often in other industries like construction, defense, or pharma. Perhaps someone else can comment on other industries.)

- I have been asked about the "SCOPE CHANGE" and "UNREASONABLE REQUESTS from management" situations mentioned by @Tu-Ly and @Ruth but they've been posed in the form of a specific example like, "Tell us about a time when a stakeholder asked for additional functionality on a project (software) that was not part of the original scope. How did you handle that?" (Definitely prepare, as I mentioned in the initial post, a few project examples that you can cite for this type of question.)

I've not been asked the questions about SLA's, managing attrition, expediting delivery (amazingly) very often. My most recent interview included SLA discussion and metrics, but in this string I'm trying to apply 80/20 and concentrate on the questions most often asked (in my own experience.)

While I think making up a scenario a good idea, it's probably not as good (IMO) as citing an actual experience you have. Perhaps you can think of an experience from your past (from school or previous non-PM position) that contains some of the same structural elements of the question being asked of you. You don't have to be a PM to have dealt with a troublesome team member or unrealistic stakeholder requests (like when the customer asks you to make the latte non-fat, but with whole-fat cream... what is wrong with those people?) If you can think of something (anything) from your past that relates, your answer will be more authentic.

In any case, if the interviewer is asking you a "have you ever dealt with..." case example kind of question, they are not only to see if you have that specific experience in your past, but also how you would deal with it in the future. If you don't have a specific PM example and you can't come up with a analogous example as above, your last resort would be just to say, "I have not had exactly that type of situation, but if presented with that situation I would do (INSERT what you would do here!)"

In this final scenario, where you don't have any story to tell, if the job requires PMP certification I'd suggest your response follows PMBOK guidelines, same for Lean, Agile, etc... how you respond to issues goes a long way towards telling the hiring manager what kind of PM you are, and what methods you follow. If it's an Agile job and you say, "I'd pause development and have the product manager fill out a new requirements document" then you just struck out. :-)