Project Management

Voices on Project Management

by , , , , , , , , , , , , , , , , , ,
Voices on Project Management offers insights, tips, advice and personal stories from project managers in different regions and industries. The goal is to get you thinking, and spark a discussion. So, if you read something that you agree with--or even disagree with--leave a comment.

About this Blog

RSS

View Posts By:

Cameron McGaughy
Lynda Bourne
Kevin Korterud
Peter Tarhanidis
Conrado Morlan
Jen Skrabak
Mario Trentim
Christian Bisson
Yasmina Khelifi
Sree Rao
Soma Bhattacharya
Emily Luijbregts
David Wakeman
Ramiro Rodrigues
Wanda Curlee
Lenka Pincot
cyndee miller
Jorge Martin Valdes Garciatorres
Marat Oyvetsky

Past Contributors:

Rex Holmlin
Vivek Prakash
Dan Goldfischer
Linda Agyapong
Jim De Piante
Siti Hajar Abdul Hamid
Bernadine Douglas
Michael Hatfield
Deanna Landers
Kelley Hunsberger
Taralyn Frasqueri-Molina
Alfonso Bucero Torres
Marian Haus
Shobhna Raghupathy
Peter Taylor
Joanna Newman
Saira Karim
Jess Tayel
Lung-Hung Chou
Rebecca Braglio
Roberto Toledo
Geoff Mattie

Recent Posts

Project 2030: Skills We Need to Cultivate Now

The Technical Program Manager: How to Stay Relevant in 2025

5 Things Your Operational Plan Should Do

5 New Project Guardrails for Adaptive Leaders

The Leader's Voice: Respect It, Protect It, and Use It Properly!

Categories

2020, Adult Development, Agile, Agile, Agile, agile, Agile management, Agile management, Agile;Community;Talent management, Artificial Intelligence, Backlog, Basics, Benefits Realization, Best Practices, BIM, business acumen, Business Analysis, Business Analysis, Business Case, Business Intelligence, Business Transformation, Calculating Project Value, Canvas, Career Development, Career Development, Career Help, Career Help, Career Help, Career Help, Careers, Careers, Careers, Careers, Categories: Career Help, Change Management, Cloud Computing, Collaboration, Collaboration, Collaboration, Collaboration, Collaboration, Communication, Communication, Communication, Communication, Communications Management, Complexity, Conflict, Conflict Management, Consulting, Continuous Learning, Continuous Learning, Continuous Learning, Continuous Learning, Continuous Learning, Cost Management, COVID-19, Crises, Crisis Management, critical success factors, Cultural Awareness, Culture, Decision Making, Design Thinking, Digital Project Management, Digital Transformation, digital transformation, Digitalisation, Disruption, Diversity, Diversity, Documentation, Earned Value Management, Education, EEWH, Enterprise Risk Management, Escalation management, Estimating, Ethics, execution, Expectations Management, Facilitation, feasibility studies, Future, Future of Project Management, Generational PM, Governance, Government, green building, Growth, Horizontal Development, Human Aspects of PM, Human Aspects of PM, Human Aspects of PM, Human Aspects of PM, Human Aspects of PM, Human Resources, Inclusion, Information Technology, Innovation, Intelligent Building, International, International Development, Internet of Things (IOT), Internet of Things (IoT), IOT, Knowledge, Leadership, Leadership, Leadership, Leadership, Leadership, lean construction, LEED, Lessons Learned, Lessons learned;Retrospective, Managing for Stakeholders, managing stakeholders as clients, Mentoring, Mentoring, Mentoring, Mentoring, Mentoring, Methodology, Metrics, Micromanagement, Microsoft Project PPM, Motivation, Negotiation, Neuroscience, neuroscience, New Practitioners, Nontraditional Project Management, OKR, Online Learning, opportunity, Organizational Culture, Organizational Project Management, Pandemic, People management, Planing, planning, PM & the Economy, PM History, PM Think About It, PMBOK Guide, PMI, PMI EMEA 2018, PMI EMEA Congress 2017, PMI EMEA Congress 2019, PMI Global Conference 2017, PMI Global Conference 2018, PMI Global Conference 2019, PMI Global Congress 2010 - North America, PMI Global Congress 2011 - EMEA, PMI Global Congress 2011 - North America, PMI Global Congress 2012 - EMEA, PMI Global Congress 2012 - North America, PMI Global Congress 2013 - EMEA, PMI Global Congress 2013 - North America, PMI Global Congress 2014 - EMEA, PMI Global Congress 2014 - North America, PMI GLobal Congress EMEA 2018, PMI PMO Symposium 2012, PMI PMO Symposium 2013, PMI PMO Symposium 2015, PMI PMO Symposium 2016, PMI PMO Symposium 2017, PMI PMO Symposium 2018, PMI Pulse of the Profession, PMO, PMO, pmo, PMO Project Management Office, portfolio, Portfolio Management, Portfolio Management, portfolio management, presentations, Priorities, Probability, Problem Structuring Methods, Process, Procurement Management, profess, Program Management, project, Project Delivery, Project Dependencies, Project Failure, project failure, Project Leadership, Project Management, project management, project management office, Project Planning, project planning, Project Requirements, Project Success, Ransomware, Reflections on the PM Life, Remote, Remote Work, Requirements Management, Research Conference 2010, Researching the Value of Project Management, Resiliency, Risk Management, Risk Management, Risk management, risk management, ROI, Roundtable, Salary Survey, Schedule Management, Scheduling, Scope Management, Scrum, search, SelfLeadership, SelfLeadership, SelfLeadership, SelfLeadership, SelfLeadership, Servant Leadership, Sharing Knowledge, Sharing Knowledge, Sharing Knowledge, Sharing Knowledge, Sharing Knowledge, Social Responsibility, Sponsorship, Stakeholder Management, Stakeholder Management, stakeholder management, Strategy, Strategy, swot, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management Leadership SelfLeadership Collaboration Communication, Taskforce, Teams, Teams in Agile, Teams in Agile, teamwork, Tech, Technical Debt, Technology, TED Talks, The Project Economy, Timeline, Tools, tools, Transformation, transformation, Transition, Trust, Value, Vertical Development, Volunteering, Volunteering #Leadership #SelfLeadership, Volunteering Sharing Knowledge Leadership SelfLeadership Collaboration Trust, VUCA, Women in PM, Women in Project Management

Date

Dubai's Megasuccessful Megaprojects Set the Standard

linkedin twitter facebook Request to reuse this  
PMI® Global Congress 2014 -- EMEA kicked off in Dubai, where nearly 1,000 attendees got an insider's look at how project management helped turn a pearl-diving village into a world-class city.

"Dubai has a reputation for megaprojects, not only large, but iconic -- incredible feats of engineering," said Mark A. Langley, president and CEO of PMI, at the opening session of congress. "Not only the best and biggest projects, but the best project and program management to ensure success."

When it comes to project performance, he said, PMI Pulse of the Profession® data reveals the Middle East does much better than the rest of the world.

And Dubai stands front and center. The transformation of what was once a vast desert into a world-class city has been "staggering," said His Excellency Mattar Al Tayer from Dubai's Roads and Transport Authority. 

He outlined five economic building blocks:

  • High stability and security
  • An open and diverse economy
  • A central geographic location with a multicultural population of more than 200 nationalities
  • Environmental sustainability
  • High-quality infrastructure

While oil fueled early growth, Dubai has a grand vision -- and from grand visions come grand projects.

Take Dubai World Central, a next-generation aerotropolis ultimately capable of handling 200 million passengers by 2016, said His Excellency Khalifa Al Zaffin of Dubai Aviation City Corp. 

And while the project is designed primarily to house commercial and residential districts, its competitive advantage lies in Dubai's strategic location. "One-third of the world's population is within a four-hour flight -- mainly from the Middle East, North Africa and Southeast Asia regions that together have US$3.6 trillion GDP," Mr. Al Zaffin said.

Dubai is leveraging that strategic location to carve out its place as a major global player. A new Silk Road is emerging, with 55 percent of the Middle East trade now with India and China, said Dr. Nasser Saidi of Nasser Saidi & Associates and former chief economist at the Dubai International Financial Centre.

Part of the Dubai's success lies squarely with securing project and program buy-in at the highest levels. In the case of snaring hosting duties for World Expo 2020, local, municipal and federal government were all involved. 

"In other expos, it was always the mayor of the city particularly who was responsible," Dr. Saidi said. "Here, responsibility is right at the top, which leads to better coordination, strategic planning and getting things done."

Along with World Expo 2020, two other platforms are driving Dubai's future growth, said keynote speaker Mr. Hassan Al Hashemi of the Dubai Chamber of Commerce and Industry:

  • A booming Islamic economy with opportunities in everything from halal fashion to tourism to support the 2.2 billion Muslim consumers expected by 2030

  • Emerging markets, especially Africa, with Dubai serving as a vital gateway to the burgeoning market

Dubai's evolution is nothing short of amazing. And it will only continue with World Expo 2020, an engine for change powered by innovation and supported by expertise in project and program management. 

Where do you look for inspiration? 
Posted by cyndee miller on: May 06, 2014 05:44 AM | Permalink | Comments (1)

Getting Documentation Right

Categories: Project Planning

linkedin twitter facebook Request to reuse this  
Documentation is an important aspect of a project manager's job. We document to keep us aware of status on projects. We use it to stabilize spending and keep a paper trail of events and circumstances. So, what should you capture and how should it be maintained? Here are a few tips to make sure you're capturing usable documentation.

  • Know your source. Having the information helps, but being able to backtrack to determine who provided it -- and thus its worthiness and validity -- is even better. This is important in the case that information comes into question later. For instance, if you receive a pre-defined budget for your project but then are given another amount, a senior source with oversight over your project can help validate the original amount. Be sure to have that contact's information and even a backup source in case that source moved on.

  • Have clear, concise information. Lessons learned will tell you that communication is key to getting information correct. As much as possible, try to make documentation clear, so the knowledge transfer process goes smoothly and you, team members and stakeholders are able to follow it. Include wording that easily links to follow-up information or shows there is a continuation to a document.  

  • Use a repository. Make sure to keep documents in a secure location to be able to recall them when needed. Whether you file documents by projects, size or funding amount, at the very least have a system for filing. Have some type of dated system for knowing what is the most current file or selected information. This will help to determine if the information is no longer useful.

Now that you know how to maintain documentation, we'll review which documents should be retained in my next post.

 What are your must-have tips for documentation on projects?
Posted by Bernadine Douglas on: May 04, 2014 01:29 PM | Permalink | Comments (4)

Why Realistic Goals Matter — and How to Set Them

Categories: Project Planning

linkedin twitter facebook Request to reuse this  
One of the regular challenges I hear coming from the project management community is the idea that our organizations are setting unrealistic goals. This is a tremendous challenge because setting unobtainable goals can lead to project failure, low morale and a culture of insecurity. 

It's vitally important to spend time working with our project management offices (PMOs) and sponsors to develop realistic timelines and goals that are achievable in the short- and long-term. Why? Because this is going to help maintain motivation throughout the project as each milestone is obtained. Additionally, it will help you communicate progress more effectively to your sponsors and gives you the capability to set clear, reasonable expectations at the start of the project. Here are three ways you can set better goals that motivate your teams, sponsors and stakeholders:

  1. Ensure clarity of project goal. To effectively set proper goals for your team, you need to make sure that your goals are in line with the project's objectives. Too often projects go astray because the project's goals aren't clear or don't align with the business objectives of the parent organization. This can be managed by making sure that you clarify the project's goals at the very start. For example, set up a meeting with your sponsor or executives to talk about project objectives, how they will be measured, and the sponsor's role and responsibilities. This simple step ensures that you have clarification and can work with your team to set goals that are in line with sponsor expectations. 
  2. Take a short and long view of the project. It's often too easy to look at the end result of a project and say that is the only goal that matters. This can throw off your team and demoralize everyone involved, because if you are dealing with a project that can take years to complete, there is no sense of accomplishment, even when you have completed a major milestone in the project's life cycle. That's why you need to set short- and long-term goals. The short-term goals will do two things: First, they help your team members stay motivated and drive progress by giving them an occasional sense of accomplishment. Second, they give good insights on whether the project is on- or off-course, making it much easier to adjust the schedule and plan accordingly. 
  3. Communicate. Everything in project management comes down to communication. In setting goals for your team, you need to communicate consistently. A successful communication strategy focuses on clearly relaying the project's objectives and goals and how those support the organization's mission; explains how the short- and long-term goals relate to each other; and allows you to maintain control over expectations. 
While it isn't possible to control every variable on every project, a project manager can make great strides in team performance by using goals to set proper expectations. 

What helped you set proper goals in a recent project?

Read more about PMOs and their impact on strategy implementation in PMI's Strategic Initiative Management: The PMO Imperative.

Posted by David Wakeman on: April 28, 2014 10:04 AM | Permalink | Comments (1)

Turn Chaos Into Success

Categories: Complexity

linkedin twitter facebook Request to reuse this  
Project managers usually advance in their careers by managing small, then medium and ultimately large projects. What project managers may not be prepared for is the complexity that comes with taking on bigger projects. Left unmanaged, this complexity leads to chaos and ultimately project failure. 

Why does this happen? 

A business system is characterized by processes and activities that work in tandem to deliver a specific result that benefits customers. Throughout a project's life cycle, it can encounter a number of business systems -- such as leadership systems (how leaders set values and organizational performance and governance) and customer systems (engagement strategy to meet customer needs and support that relationship) -- that independently and jointly put pressure on the project. 

As you segment the business systems further, you will find underlying, interrelated business processes and activities that create even more complexity. And as the project traverses along the value chain, more strategic tensions apply, such as competing research and development priorities or sales quotas.

Projects that disrupt these systems and value chains promise new and improved approaches. But project managers must mediate the chaos this disruption generates to achieve project success. 

Organizations with less mature processes and fewer performance measures tend to put more pressure on project teams. In these organizations, the project team is responsible for navigating the chaos caused by increased complexity. Projects often devolve into uphill battles and ultimately fail. This demonstrates an inherent "inverse tension" between process maturity and project complexity. 

Reduce complexity by relaxing tensions.

By understanding tensions, project managers can develop a management discipline that shapes the project plan and enables success. To create that discipline, follow these foundational steps:

  1. Identify the business systems that impact the project, as well as their implications.
  2. Classify the current maturity of the business systems and value chain, and plan any needed workarounds. 
  3. Categorize project complexity by assessing the project plan, methods and team.
I use APQC's Process Framework as one source to identify common organization business systems and processes, and their potential pitfalls.

Voices_Peter_Complexity_pic1.png
 
A team should identify the system's performance gaps to manage mediations and avoid negative impacts proactively.  

To assess the performance of business systems, I generally rely on the CMMI model (Capability Maturity Model Integration). I define the performance criteria according to the following maturity levels: 

  1. Initial: The starting point for use of a new or undocumented repeat process
  2. Repeatable: The process is documented sufficiently to enable the team to follow the same steps again
  3. Defined: The process is confirmed as a standard business process
  4. Managed: The process is quantitatively managed in accordance with agreed-upon metrics
  5. Optimized: The process includes deliberate process optimization and improvement
Voices_Peter_Complexity_pic2.png

I also use simple checklists to assess the project capability of an organization and team to determine any preventative actions I can take in the planning phase. For example, asking a series of assessment questions that identify process maturity levels allows me to consider any gaps I need to mitigate to improve project performance. 

Voices_Peter_Complexity_pic3.png

To analyze team-related project complexity, I leverage the characteristics outlined by U.S. authors Kathleen B. Hass and Amit Kumar:

  • Details: The number of variables and interfaces 
  • Ambiguity: Lack of awareness of events and causality 
  • Uncertainty: Inability to pre-evaluate actions 
  • Unpredictability: Inability to know what will happen 
  • Dynamics: Rapid rate of change 
  • Social structure: Numbers and types of interactions 
  • Interrelationships: Many existing interdependencies and interconnections  

Voices_Peter_Complexity_pic4.png

I used these frameworks to reduce complexity and increase predictability when I managed a big project team that was working with a large number of suppliers. The project was highly complex, behind schedule and expected to go over budget. 

The team managed supplier payments by sending invoices to accounts payable once the related work was complete. Using assessment questions, I discovered the main problem was related to a large global transformation initiative, in which the purchasing team worked within limited regional relationships. I classified this as a high complex engagement because the team:

  1. Was ambiguous about the role it needed to play 
  2. Was uncertain when work would be accomplished and order fulfillment would occur
  3. Had changed its social structure from regional to global and required more time to align strategically
  4. Had a high dynamic rate of change that created performance issues
In my management improvement plan, I was able to clearly demonstrate what business system was failing, where in the system it was located and why it was underperforming. I created a clear path forward to restore performance, which resulted in reduced complexity, better alignment and lower costs.

How do you create a framework to get a handle on complexity?

Learn more about complexity on PMI.org.
Posted by Peter Tarhanidis on: April 24, 2014 01:28 PM | Permalink | Comments (2)

7 Steps to Project Planning Acceleration

Categories: Project Planning

linkedin twitter facebook Request to reuse this  
What's a reasonable amount of time to devote to planning a project? I use this rule of thumb: If it is a low-uncertainty project (i.e., we've completed another with similar conditions in the past, with known technology and firm assumptions), devote at least 10 percent of the expected duration of the project to planning it. If it's perceived as a high-uncertainty project (i.e., one with new technology, new approach, uncertain conditions), devote at least 20 percent.

But let's face it. Often, organizational pressure will not allow us to devote that much time to planning. So is there an approach that lets us reduce planning time but still do good work and come up with a complete, useful plan? 

Many organizations I've worked with use a project planning acceleration workshop (PPAW). This is an organized, closed-door, multiday session with the whole project team to focus exclusively on producing the project plan -- something that usually takes several weeks, completed in a few days' time. There are different ways of organizing such an event, but I usually follow these seven steps:

1. Plan the plan. Share with team members all of the project's background information. Send invitations with enough lead time and clearly state the session's sole objective, which is to produce a solid project plan. I often kick off the session stating that once we are finished, we will have a project plan that is roughly 75 to 85 percent complete -- and that we are going to accomplish this in a very short period of time. Therefore, total commitment is required from all participants.

2. Set the stage. What you want is an environment conducive to teamwork without distractions. Secure a room to host the workshop, preferably outside of the office. And don't forget to include a lot of food and beverages for the duration of the workshop. When people are tired, food helps!

3. Define the agenda. Depending on the complexity of the project, different workshop durations will be required, but three days is adequate for most projects. I often use an agenda that looks like this:

  • First day: Devote the morning only to the human elements of the project -- for example, for introductions and team integration activities. It'll set the stage for the rest of the workshop. In the afternoon, analyze the project background and produce a thorough project charter that includes scope statement, time and cost constraints, major deliverables, key stakeholders, expected benefits, restrictions and assumptions.
  • Second day: In the morning, develop the work breakdown structure (WBS). Make the whole team work on defining the major deliverables and then break into smaller groups to further decompose these major deliverables. Produce the project's schedule in the afternoon.
  • Third day: The planning elements needed for your project might vary, but I usually devote this day to producing the budget, a roles and responsibilities matrix (mapping the team members to work packages on the WBS), a key resources plan and a risk management plan. 
4. Use collaborative working techniques. Don't just project steps on a screen; make team members work together. When producing the WBS or the project schedule, use the participatory cards on the wall (COW) technique. For the risk management plan, brainstorm together to identify risks and ask participants to pin different risks on color-coded charts according to their assessment of probability and impact. 

5. Document everything. Assign someone in the team to document everything produced. You may use Post-its to draft the WBS or the schedule, but these elements need to be recorded formally for when the project starts. 

6. Assign tasks for completion. After the workshop is finished, the project plan won't be completely finalized. Usually certain parts need more research or analysis. Assign specific team members to complete outstanding pieces and establish a deadline for completing these elements that were initiated at the PPAW.

7. Kick off the project. Once the project plan is deemed completed, host one more session to make a final review of all the elements, especially those that needed further research. Combine this activity with a formal project kick-off meeting -- the end of PPAW and the beginning of your project.

In my experience, when a team is co-located and completely focused for a specific period of time to create a plan, it yields better results.

Have you ever run a PPAW? How has it improved your project?
Posted by Roberto Toledo on: April 10, 2014 05:31 PM | Permalink | Comments (7)
ADVERTISEMENTS

"Bad artists copy. Good artists steal."

- Pablo Picasso

ADVERTISEMENT

Sponsors