Is It Clear?

Last week my daughter Shannon and I went for a walk around the local pond. As we came around the corner, the garbage can caught us by surprise. It said:

“What?!” we said to each other.

We decided to take a closer look. The can actually said:

A little misplacement of the sign, whether on purpose or not, gave a totally different message.

I guess we can forgive a garbage can for its miscommunications. In the garbage goes...

Who Needs to Know?

Have you ever had someone say, "You don’t need to know that; leave that part to me," when working on a project?

After your first reaction ("Huh?"), if you are like me, you would be thinking, "Hmm, I asked because I needed to know."

What happened here? It seems as though clear roles and responsibilities have not been defined. One person thought it was their responsibility to do that part of the work and didn’t realize another person also needed to know.

What could have helped? A RACI chart would have been useful. RACI stands for responsible, accountable, consulted and informed. It would show who is:

• (R)esponsible for the work (to get the job done)
• (A)ccountable for the work (to report on it)
• Needs to be (C)onsulted on the work (their input gotten)
• Needs to be (I)nformed about the work (perhaps their part of the project depends on it)

Typically, a RACI chart is drawn with activities down the left-hand column, and roles or people’s names along the top row.

Here is an example of a RACI chart from raci.org:

It's a very handy tool indeed to prevent some conflicts from occurring.

Deficiencies: The Achilles’ Heel of Construction Projects

This week, please welcome Paul Behner, an accomplished project manager in the construction industry, as my guest writer.

Deficiencies are a standard line item on most, if not all, construction projects.

Construction project deficiency is defined as a characteristic or condition that fails to meet a standard, or is not in compliance with a requirement or specification, and is sometimes referred to as defective work.

Frequently, the term deficiency is confused or misinterpreted as incomplete work and, more times than not, it's used under lien act legislation to delay substantial completion milestones which trigger holdback releases. In reality, a deficiency is not the same as incomplete work. From a legal perspective, only incomplete work affecting the beneficial use of the facility or asset intended from the project performance determines substantial completion.

Without evaluating the global issues surrounding the interpretation of substantial completion, it is fair to say that both deficiencies and incomplete work are routinely misunderstood.

There is inherent ongoing risk to the general contractor who is responsible for contract performance of all trade subcontractors and suppliers. This includes all work until project close-out, with the exception of warranty work. The ongoing issue of ineffective deficiency management cannot be improved without first breaking down the problem. Until then never-ending deficiencies will inevitably remain the Achilles' heel of successful project delivery and, in turn, erode profitability and customer satisfaction.

Deficiencies are commonly cited as the barrier to successful project completion. To get to the core issue, it is more effective to consider a deeper understanding of project management which goes beyond the deficiency issue. The General Contracting business is as much about time sensitive delivery of a specified product or facility, as it is about operating a business. The business strategy ought to be focused on exceptional project delivery, therefore requiring exceptional project management proficiency.

Without question, deficiencies are an anticipated task and risk of every project and should be managed holistically within the project management plan. Whether deficiencies are the catch-all reference for incomplete or defective work being a chronic issue plaguing success, a project management plan that includes the five phases will greatly improve project close-out and overall performance. There is only one solution to effectively manage construction deficiencies and that is by way of a project management plan with improved guidelines on project close-out.

Paul Behner has spent 30 years in the construction sector. He provides strategic consulting on the full-cycle management of a project from planning to execution to close out. Visit his website at greentreepm.ca.

Stakeholder Engagement

Recently I went to a luncheon hosted by the Halifax Chamber of Commerce, which my company was proud to sponsor. (See our logo on the banner to right of stage above.)

The topic of the luncheon was “What’s Up, Halifax?” and four panelists represented major projects in beautiful Halifax.

The panelists, Alex Halef, President of BANC Group of Companies, Dov Bercovici, President & CEO, Discovery Centre, Bob Bjerke, Chief Planner and Director, Planning and Development, Halifax Regional Municipality, Steve Snider, CEO & General Manager, Halifax Harbour Bridges, were asked questions which had been pre-submitted to the moderator. Several questions were about improving our city for businesses and residents.

What struck me with the questions and answers was the emphasis on stakeholder engagement, not only from resident and business to the government and developers, but also among the city and developers.

From the answers, you could see that communication was obviously good between the city and development representatives. They communicated in front of over 100 people and were willing to answer the audience’s questions and discuss topics among themselves in the open.

It was also heartening to see that both parties were open to further increasing their communication and stakeholder engagement.

According to PMI, a stakeholder is "an individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project."

Knowing who the perceived stakeholders are can be the most difficult part of identifying stakeholders.

For the cities and towns we live in, we are all stakeholders, and I know the government is conscientious in my area to seek input from residents and businesses. But there can always be more input and improvement on engagement.

Is that a bad thing? No. Projects are continuously improving all the time, and we should expect that to be so.

I have observed over the years that, as project managers, we often don’t realize how much project stakeholders want to be involved in a project. Sometimes we might think we are bothering a client or user, other times we think they don’t really want to be engaged at a certain level of depth. Should we assume how much stakeholders want to be involved? Well, no. We should ask them. The answer might be surprising.

Involving stakeholders is a key, and valuable, tenet of project management.

That's When We All Win

I have been reading about the upcoming American election with some interest. So much so that I only recently realized we were having a local (Halifax, Canada) municipal election and voting at the polling station is on Saturday.

One of the things that elections usually centre on is change for the better. Citizens take responsibility by electing officials who will represent them to take action.

I believe in the power of the democratic process. But related to that is our own power to change our own world. Two songs that I enjoyed about taking self-responsibility are Michael Jackson’s Man in the Mirror and Nickelback’s When We Stand Together.

Who is a Successful Project Manager?

My manager at Motorola, Jim, was one of the most successful project managers I have known. His projects completed as planned, but he was successful because his team got the work done happily. He hired people to do a job and he let them do it. Now that I am teaching about project management, I take some of the knowledge that PMI (Project Management Institute) gives on project management and apply it to Jim’s approach.

As a successful project manager, Jim was:

1. Inclusive: He made everyone on the team feel like they were the project manager. Once responsibilities were accepted, Jim let you do your job. But he didn’t ignore you – we knew any time we needed to communicate with him the door was open.
This is related to the PMBOK (the Guide to the Project Management Body of Knowledge) in that roles and responsibilities were assigned, and everyone knew who was doing what on a task. We knew our RACI (chart for who is Responsible, Accountable, Consulted and Informed.)

2. A delegator: Jim told us to figure things out ourselves. He didn’t take on our jobs, and he had faith that we could do what we were lined up to do. When I asked Jim a question about a software model, he said, “Read the book, that’s what I did.” It might have sounded gruff, but I got the point. And I was also encouraged that he thought I could do what he did.
The PMBOK says, “Successful project managers have strong leadership skills.” Jim was a good leader and set an example.

3. A communicator: He provided structure to the team. Everyone knew what they were supposed to do. We met weekly. We were never “lost” about what to do or what was expected of us.
We had: the RACI, mentioned above; a schedule with milestones; a communications plan; and project ground rules – these weren’t necessarily named using PMI terminology, but followed the standard.

4. A leader: He gave direction in a clear manner.
We always knew where we were in the project schedule and what we had to do. The team was led by Jim and the work was managed, monitored and controlled to stay on track.

Jim died a number of years ago from ALS (Lou Gehrig’s disease). Right up to the end he maintained his attitude and approach, and continued to lead and be insightful.

If you are interested in learning more about project management, our needs assessment at PMneeds.com will help you determine which type of development would benefit you most. There are opportunities for learning about the fundamentals of project management, advanced project management applications, and PMP certification preparation.

Projects, Not Complaining

I was driving to Truro the other day and thought I would listen to a CD on the way. So I listened to Jack Canfield's Success Principles.

Jack's first rules had to do with taking responsibility for yourself and not complaining. This got me to thinking about project management (of course...) and how those who initiate projects do so with an "opposite of complaining" mindset. That is, instead of going on complaining about something, they take a "let's get it solved" attitude and turn it into a project.

If you are a project initiator, congratulations on your proactivity.