Posts Tagged ‘tips’

Prioritization and emergencies

Sunday, September 5th, 2010

So, what happens to a schedule when emergencies happen?
At one time or another the team will have emergencies that take them away from the critical work. In most projects, there will be changes to the market that cause emergency changes to scope, timelines or budget. And, often the PM is the one to direct and support the team through the emergencies.
What happens when the PM is the one who has the emergencies?
Have you set up the project to run without you – even for a short time? Do you have contingencies for your absence?
What are the tips you would give to less experienced PMs?
Happy PMing

Perry

Keeping balance in your life

Sunday, August 15th, 2010

I think the topic is applicable to everyone who works. Whether you work for someone or for yourself. You do your best work when you are energized and excited. You can only be energized and excited if you have balance in your life – as a colleague of mine says, you need to fill your buckets before you can do a great job.

When you work for someone else, that can be as simple as not taking work home on the weekend, or taking a two week vacation. When you work for yourself, it gets a bit more complicated. You need to find the opportunities between client needs to refresh yourself.

I’ve found myself thinking lately about all the things I have to do. The problem is  I work better at things I get to do. My blinking alarm was telling me that it was time to take a break. But I still had all these things I had to do.

When I get in this cycle I find it works to look at when I think I can take a break – next week, after a milestone/deadline has passed, whatever works.

Then I plan what I’ll do with my time off and as the day approaches I let people know I am taking a day off.

I find the planning helps me feel like I’m taking a bit of time off because I’m thinking of what I want to do. Not only what I have to do.

I planned my day off for last Thursday and protected the day by letting clients and my business partner know I would not be available. And, it worked.

I not only got Thursday off, but I have been doing more reading and relaxing since Thursday than I’ve done for a couple of months. The added bonus is when I think about the work on my plate, and getting more work, it feels like something I get to do again.

What do you do to fill your buckets?

Happy PMing

Perry

Using your lessons learned. How to make the next project easier

Sunday, August 8th, 2010

We all know the value of using lessons learned from other projects,but how often do we get to use them?

What gets in the way?

I know it’s often difficult to find the lessons learned on any project, let alone a project that is comparable to the one you are about to start.Time,or lack of it, often gets in the way of thinking about any lessons you might want to implement in your new projects. And, organizational assumptions can seem like a barrier to making changes: “we’ve always done it this way and there’s really no way to make it better in this company”.

What I suggest is to take a small step. If you don’t have time to read up on previous projects before you start, build it into the kick off meeting. Ask the team what they think is the one consistent challenge on projects. Use that to try some new tools, tactics, or techniques.

If the team decides that requirement gathering is a consistent challenge, why not try a new approach – maybe moving from one on one meetings, to a series of large group sessions that get refined in one on one sessions. Or, maybe checking where you start requirements, if you attempt to get requirements all at one time, try iteration techniques.

If the team decides it’s communication with stakeholders, how about looking at how the communication normally flows, and bringing something new to the process.

You’ll have different issues depending on your organization. By trying one new thing, and including the team in developing the new method you can take small steps that improve the project performance in your organization.

Any other ideas on common lessons and new approaches?

Happy PMing

Perry

Status reports – useful or not?

Sunday, August 1st, 2010

I’ve been reading a number of posts on LinkedIn and other blogs about status reports and why they don’t work. Most of theses are promoting a different model for status reporting. The problem is not with a format of reporting, but with the process of reporting.

The reason we status report seems to have gotten lost in the search for a new format of status reports. We report to keep people apprised of the status of the project. We use whatever tool fits best within the organization, or methodology.

The key elements of status reporting are,

  1. where we thought we would be based on the last approved baseline and where we really are
  2. what we see as issues that the sponsor needs to help resolve, and how they need to help
  3. what we see coming up that is just a heads up – and what we’re doing about it

If you are reporting clearly and honestly on these three points, the status report has value. If not, here’s the problem,

  1. Where we are v where we thought we would be. If you are trying to provide a more optimistic picture, you’ll mislead the sponsor, and lose your credibility
  2. If you are trying to show you can solve the issues when it’s really in the hands of your sponsor, you are going to have to come to the table for help when you are at the end of your resources. The sponsor wants to help, let them get in there and do their job.
  3. If you don’t tell your sponsor what’s coming up – and say whether you need help or not – you’ll look like you are blindsiding them when they hear it from someone else.

So, the point is, status reporting is communication and if you communicate the right things clearly and objectively, the format is just a tool.

What do you think about status reporting? Do you have a story to share?

Happy PMing

Perry

Making decisions, the project manager’s challenge

Sunday, July 25th, 2010

Often the project manager is in the middle of a push and pull about decisions. Everyone wants to get started, but key decisions aren’t made. How do you keep everyone engaged when this is happening?

I find this one to be the most interesting challenge, and the one linked tightly to corporate culture.

Sometimes it’s a good idea to go ahead with some of the project while you wait, and other times, delay in decision making is a sign of trouble brewing.

Sometimes the corporate culture is ‘just do it’ and sometimes it’s about careful analysis before acting – and usually somewhere in between the two extremes. If your organization leans towards the ‘just do it’, you need to get an idea of the direction and then go forward. If your organization leans towards the analysis scenario, you need to get documented agreement to go forward before the decision is complete.

How does the PM know which scenario is true for their project?

History will help, what has happened in previous projects when decisions are delayed? Your sponsor will give direction to help determine what to do. And the way the team reacts is also a good indicator.

If you determine you can go ahead while waiting for the final decision, there are some ways to ensure you are doing the right thing. First, your sponsor needs to be on board with what you are doing. And second, develop a way to document both the reasons for going ahead and the implications.

How do you determine what to do? That’s probably the easiest part. Look at activities that need to be done regardless of the decision. Can you start drafting risk plans, communication plans, or resource plans.

Can you develop marketing plans? Will the decision have an impact on the way you’ll market the product?

Can you analyze some potential solutions?

The overall question in this circumstance is depended on the decision you are waiting for. If the decision could determine whether the project goes forward or not, or is a fundamental decision about the product features, you probably don’t want to use resources of any kind because the risk of wasting resources is high.

If the decision is a refinement of the features, or a buy/lease decision, there are a lot of activities that can be done to move the project forward while you wait.

Happy PMing

Perry

Project management blog recommendation

Monday, June 14th, 2010

If you don’t follow the Papercut Edge, I highly recommend you give it a try.  The current series of posts are all about the 9 types of PM behaviour that you don’t want to see.

Check it out.

Happy PMing

Perry

Project Management Questions

Sunday, June 6th, 2010

A short post today – I’m all done in from tramping around 17 heritage sites today. That’s 10 locations, one had 5 units to show, 2 had 2 units and  a bonus, there was an open house in one of the units. So, it was great but tiring.

This post is about places to ask and  find answers to your PM questions. Places on line, other than Google searches.

LinkedIn has a list of PM related groups. Join one and start a discussion – or create your own group.

Ask About Projects, is also a great resource. It’s more casual than LinkedIn and allows you to vote on good answers as well as to provide your own answers.

Those are two of my favorites, what would you contribute to a list of great sites for PMs?

Perry

The Art of Project Management

Sunday, May 30th, 2010

Have you ever watched a PM be successful without  an apparent methodology? Is this an example of good project management or lucky project management?

I would say, it can be both. An inexperienced PM can get lucky, and experience PM can be using their knowledge and wisdom to work the methodology without having to openly use all the tools. The challenge is, it’s not always about experience.

How do you know which one you are dealing with?

A lucky PM will eventually run out of luck. At best, when things go off track after the luck runs out, the lucky PM will be scrambling to figure out how to show what happened and figure out what the team will do. At worst, the lucky PM will struggle to figure out who to blame.

For sponsors and clients, you can ask a few questions along the way. A lucky PM will not be able to easily answer specific questions that start with what, when, and how. “How is it going?” is too easy to answer with “great!”, but “What are the current issues (there are always some issues)” is harder to answer if you don’t have a handle on the project.

A ‘good’ PM will have their finger on the project, they will produce the documentation you need but they will be able to answer the hard questions. Or, will be comfortable with saying they will need to check.

The challenges is it’s not about experience all the time. You can find highly experienced PMs who work by the methodology, they run successful projects, they can tell you exactly where in the Project Management Life Cycle the project is. You can also find inexperienced PMs who will successfully manage teams through challenging projects without referencing any methodology.

Why does this matter? PMs will bring to the project what they have: experience, people skills, communication skills, any combination of these. By understanding where your PM fits on the scale of lucky to good, you can understand how work with them.

For an internal PM, you know how to develop their skills. For a contractor or consulting PM, you can work with these concepts to hire the right type of PM for your project.

Have a great project week.

Perry

Asking the right questions

Sunday, May 23rd, 2010

I have been looking on LinkedIn a lot lately and trying to answer some of the questions raised in discussions. I found it hard to give a useful suggestion most of the time because the question was not asked with enough context.

Asking questions is a skill. For a consultant, PM or a business analyst, it’s a critical skill. It’s about asking the right questions in the right way.

What are the right questions? That depends on your objective. Who, what, when, why, how are a good place to start. Thinking about your end goal will help determine what information you need.

  • What are we trying to do?
  • When do you need to have it done?
  • Who will be doing the work, who will be affected by the outcomes?
  • Why are you trying to achieve this?
  • How have you done this in the past, how can we get started…?

These are all excellent questions. When the questions are framed this way the gap is context. When you start to form your questions, think about the people you will be asking, is there ambiguity in the context? Will you need to explain the background? Can your answer come in a yes/no format – this is not what you are aiming for most of the time.

Let’s look at an example.

Question:

Do you have a PMO?

Answer:

Yes or no.

This can be misleading when you go to implement a solution.

If you realize there’s more information, you might ask what does the PMO do? If you go down this route, you’ll get the information you need, eventually, but you are setting up more of an interrogation than an interview.

A new approach:

Question:

Often an organization has formal or informal project support, methodology, training and prioritization. How is this handled in your company?

Answer:

Depending on your client, you’ll get a different answer – what you will get, though is a conversation rather than an answer. The conversation will lead to a richer understanding of what, why, how, who, when.

If you think about the bigger picture of the information you need, you’ll start to form more open and encompassing questions and the result will be a better understanding of your client.

Do you have any success stories, or horror stories?

Mergers, successful transition

Sunday, May 9th, 2010

This blog was inspired by a LinkenIn posting.

I’ve worked on four successive credit union mergers and each time we developed looser success criteria. The reason we did this is integration and success on mergers is complicated and we found the tighter we tried to control it, the less successful we became.

At the beginning of the project, you may not know enough about the technical integration details to develop success criteria. I’ve found it much more useful to start with guiding principles and develop success criteria as knowledge grows.

The integration of the people is somewhat easier to plan – harder to achieve success. The key parts are communication, training, communication, training and transparency – oh, and communication.

Trying to achieve smooth people transition is a false goal. If you acknowledge that there will be challenges and hard times, it builds perspective. The difficult times will be difficult, but no one is measuring them against false promises of easy transition.

Guiding principles can be as simple as – minimize customer disruption, maximize employee involvement, transparent communication.

What this means is that you begin to set success criteria when you know enough to set realistic ones.

As and example, our transition date for the banking platform data was a key criteria.

By setting the date based on executive wishes,

  • we had to make changes to the date,
  • we had to reschedule training,
  • we had to re-communicate information to staff and members and
  • we had to work the team long hard hours.

By setting the date based on analysis of the banking platform, we were able to

  • pick a date we could stick to
  • initiate structured training and change management
  • clearly communicate the progress, and upcoming milestones
  • clearly communicate to the membership what was happening
  • identify innovative approaches to meet the guiding principles
  • let the people who were leaving know the date they could go on to their new journeys

Does anyone else have tips for project managers on mergers and acquisitions?