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

A Hollywood-Style Move From PM to Scrum Master

Categories: Agile

linkedin twitter facebook Request to reuse this  
"As your mother tells you, and my mother certainly told me, it is important, she always used to say, always to try new things." 
-- Sir Philip Anthony Hopkins as Hannibal Lecter (The Silence of the Lambs, 1991)

Cinephiles and regular movie-goers know who Sir Philip Anthony Hopkins is. Sir Anthony is a Welsh actor of film, stage and television, considered to be one of the greatest living actors.

Your journey as a project management practitioner may be similar to Sir Anthony's journey as an actor. You may have to play different roles in projects and might gained recognition for your work. As your journey continues, you may be looking for the next stop that may lead you to explore other project management disciplines, like agile -- and, in particular, the role of an agile scrum master.

From Stage to Movie Set

Versatility is a virtue of all great actors. Though Sir Anthony has experience as a stage actor, acting for a film is quite different. As a stage actor, Sir Anthony had to undergo many rehearsal hours, and experienced a specific, tight-knit team of actors and staff. Lighting and environment are essential for the performance and there is no room for error in every live show. A theatrical play delivers a well-defined "product" that may resemble what agilists call a "traditional project" under waterfall methodology. As a project manager, you "manage the stage" of the project, meeting the stakeholders' pre-defined requirements and applying your skills supported by the project team. Your project will deliver the product or service it was intended for.

But on the film set, Sir Anthony likely needed to be more flexible, since a scene may require several takes until the director is pleased. The film set is more dynamic: different locations; a different type of crew; the addition or removal of stunts, etc. The phases of a motion picture-making -- pre-production, principal cinematography and post-production -- are similar to sprints in an agile environment.

Sir Anthony makes transferring acting skills from stage to the film set seem easy. But like him, you also have transferrable skills: you can communicate, influence, orchestrate and remove roadblocks. You can use these talents to help you adjust to the new project environment.

From Hannibal to Odin

While Sir Anthony has occupied diverse roles -- from Richard Nixon (Nixon, 1995) to Odin (Thor, 2011) -- he's been successful because he's always prepared properly, trained to correctly represent the character and depended on his foundation as an actor (whatever the media).

As a project practitioner, you are likely familiar with PMI's A Guide to the Project Management Body of Knowledge (PMBOK® Guide)--Fifth Edition, tools and techniques; best practices; and project methodology of the company or customer you work for. Those elements complement your preparation and training as a project manager -- and lay the foundation to explore and learn new methodologies like agile.

What is your experience as a project management practitioner transitioning to scrum master?
Posted by Conrado Morlan on: September 03, 2014 10:25 PM | Permalink | Comments (2)

To Have and To Hold

linkedin twitter facebook Request to reuse this  
In one of my previous posts, I suggested ways to maintain documentation. And as you know, documentation is very important -- it's the essence of knowledge transfer. The beauty of documentation is that it allows us to avoid the pains of reinventing a series of events that may only reside in a person's mind as a singular experience. It can also lead us to extract some aspect that may move our project from uncertainty and unknowns to more useful information. 
So, once we have taken the precautions I mentioned in my previous post for generating clear and valid documentation, the question becomes: What project documentation should we always have and hold on to? I would suggest, at a minimum, the following:

The charter. It is the closest disclosure to everything the project should touch on. It includes a high-level look at the project: resource list, budget, timeline, assumptions, constraints, risks, other areas of impact and dependencies, a brief description and an immediate focus.

Budget background and expenditures. This information typically details the budget spending and directs you to possible future support, if any can be used again.

Sources. These include contacts and stakeholders; where information is stored; direct lines of contact; contacts who would be next in the succession; who and where to reach out to in case of additional needs; and where information stemmed from, and how it should be categorized and even prioritized.

A status report of risks and issues in their most recent form. These items show the progress that has or has not been made and is especially helpful in communicating to a new project manager (or yourself, if returning to a project) where to pick up. This status report can even help determine the project's resource needs.

Scope. This tells you what should have been the focus of the project. It also helps determine whether there needed to be an extension to this scope or if something different should be embarked upon, such as a total new project or maybe a revamping of the current scope.

Are there any types of documentation you find significant to have during a project and to hold on to after a project closes?
Posted by Bernadine Douglas on: August 28, 2014 12:35 PM | Permalink | Comments (5)

Leading With Integrity

Categories: Leadership

linkedin twitter facebook Request to reuse this  
A few months ago, I wrote about the essential principles of leadership, and one seemed to have really struck a chord with readers. That principle is integrity. And, as I prepared to write some thoughts on the role of integrity in leadership, several examples of why integrity is so important jumped to mind. 

Take the case of the United States senator accused of plagiarizing his college thesis paper, or the seemingly lenient penalty that the National Football League commissioner laid down on one of the league's stars over a domestic violence incident, when other comparable infractions have drawn much stronger responses. 

What these two situations have in common is a lack of integrity that, on the surface, seems to be driven by taking the easy way out. Integrity is often defined as "doing the right thing when no one is watching." I don't think that is an appropriate enough definition, though. Integrity is the act of doing the right thing, even if it is extremely difficult. 

That being said, here are a few tips on how you can lead your project teams with integrity:

1. Lead honestly. The foundation of leadership and integrity is leading with honesty. You can't tell everyone everything they want to hear all the time and still get things done. Business doesn't work like that and life doesn't work like that. So to be a high-integrity leader, you need to be honest in all cases. As Erika Flora, PMP, PgMP, told me recently, being a leader requires you to "be brutally honest and provide feedback that sometimes people just don't want to hear." You can put this to work by setting clear and realistic expectations of your team, sponsors and stakeholders at the beginning, and not allowing yourself to be tied down to unrealistic expectations just to make everyone happy.

2. Take ownership. I've been in a number of organizations that faced a challenge of ownership in their projects. What that means is people are running around with big titles and the expectation is that those who report to them will jump at their slightest utterance. And as long as everything is moving along according to plan, everything is great. But as soon as the project goes off track, the "leader" is looking to point fingers and place blame to help relieve his or her responsibility. Don't do that. Being a leader and having integrity means you have to take responsibility for your performance and your team's, good or bad. As a leader, you should always start the project by telling your team something along the lines of, "Ultimately, I am responsible for the success or failure of this project, but I can't do it without you."

3. Share the spotlight. To be a strong leader of high integrity, you need to allow your team members to receive some of the glow and adulation that comes with goals achieved, projects delivered that exceed expectations and overall high performance. Allowing your team members to receive this share of the attention will make it much easier for you to get buy-in on tough issues or tricky situations in the future because they'll see you as the kind of manager who allows them to receive recognition. By the same token, when it comes to delivering bad news and accepting criticism, allowing yourself to receive the blame and not looking to share that blame with your team will engender a great deal of goodwill. And never, ever look to use one of your team members as a scapegoat for something that is ultimately your responsibility.

How do you see integrity playing out in your current team?
Posted by David Wakeman on: August 26, 2014 11:07 AM | Permalink | Comments (2)

Finding Innovation Through Design Thinking

Categories: Innovation

linkedin twitter facebook Request to reuse this  
Recently, I came across a concept presented by U.S. businessman and author Tim Ogilvie centered on "design thinking" -- how to turn abstract ideas into practical applications to maximize business growth. Since the core of portfolio management centers on identifying the right opportunities through strategic alignment, innovation and transformation, this concept seems to apply to our job as portfolio managers.

Of course, this is easier said than done, and although innovation is typically defined as a "breakthrough," it is actually accomplished through trial-and-error experimentation and old-fashioned hard work and perseverance. I think of innovation as "fail fast, fail often," but more accurately as "recover even quicker." 

Mr. Ogilvie asks some key questions, to which I've added my own thoughts on how they apply to portfolio management in identifying the right innovative projects or programs in a systematic way:

  • What IS? This covers more than the current state -- it assesses what's happening with competitors, the industry, adjacent industries and opportunities. What ideas exist? What new products or markets can be created?  
  • What IF? What are key possibilities? If something could change, what would that be? Through deep consumer insight, voice of the customer and a systematic process, options can be identified, assessed and prioritized. Careful oversight is needed at this stage, since viable options don't happen by accident.
  • What WOWS? What is fundamentally different than what's been done before? How is it better? Sometimes, an innovation is not necessarily something new, but something that brings an idea together perfectly. For example, the iPhone was not the first smartphone, but many have adopted it as the best. Innovation can be combining or recombining capabilities at a different level than before, not necessarily introducing new capabilities.  
  • What WORKS? Ideas may look good on paper or in a presentation but may work differently when translated into a market test or actual use. Through small experiments and investments, the "fail fast, fail often" mantra should prove what's viable. Failing doesn't mean the end. Experiments that fail are sometimes the precursors to a breakthrough, if learnings are applied.

Innovation Model Canvas

The Innovation Canvas and its eight key components is another way to find and sell innovation. You can easily put this on a one-page document or even the back of the napkin to concisely describe to executive sponsors why a project or program changes the way the organization does business. If you can only partially fill out the grid, then the project may require more development. You may even want to do two versions -- one for the current state and another for the future state:

Voices_Jen_framework1.png
Voices_Jen_framework2.png

What methods do you use to spot innovation in your projects and programs? 

Posted by Jen Skrabak on: August 21, 2014 10:29 AM | Permalink | Comments (1)

Project Management: The Vessel for Innovation

Categories: Innovation

linkedin twitter facebook Request to reuse this  
Innovation seems to be the new mantra for companies -- even though it has affected and shaped all aspects of our lives. And innovation covers not only the creation of a product, but also includes the process to produce it, how it's delivered to customers and even how value is generated, both for the company and the customer.

Some argue that processes and policies are barriers to innovation. These people confuse innovation with creativity and believe that trying to implement a well-thought-out, standardized process to manage innovation will constrain the results. But the opposite is true: A method for innovation sets the ground for achieving success in an efficient way. After all, creativity is only a part of a more complex innovation process, driven by project management -- and as such, you could say that project management is the vessel for innovation. That's because the best way to guarantee your organization's innovation efforts are well-managed, successful and deriving true value is through the use of program and project management tools. In addition, portfolio management can help define where to invest innovation dollars.

The problem is that those in the innovation field do not necessarily see project management as a useful tool, and those in project management do not feel that what they do is so beneficial to the innovation process. But let me give you seven processes to break down those perceptions for the sake of fostering innovation:

  1. Innovation happens in a company or a project team when leadership sets up a culture and environment for it. Senior management should first define why innovation is important, how success is going to be measured and how it will be rewarded.
  2. Define a standardized innovation project life cycle. This definition should include a description of the interim products that are expected at the end of each of the major phases.
  3. Innovation is a social process: It's about the people in the process. Creativity and new ideas always come from different sources. Therefore, flexibility, constant team interactions and empowerment of team members should be embedded in the process. 
  4. Innovation is all about failure. Enough room to fail fosters creativity and eliminates barriers that could seriously limit our ability to change. But knowing when to stop a failed project is also important. Leave bad ideas quickly.
  5. Always pilot-test what you are proposing before taking it to a full scale. Gain enough data to either modify what was defined initially or to definitely cancel it, if the product or service developed is not successful.
  6. Innovation doesn't have to mean new product development. Manufacturing processes, delivery, distribution, customer experience and financing are all fertile grounds for innovation. 
  7. Project management itself needs to be innovative. Adapt the tools and techniques to the type of projects that you have. If you think, for example, that agile or lean tools can be beneficial, test them and use them.

For organizations that compete on a global scale -- that is, most companies -- innovation can be their most important competitive advantage and the factor that guarantees long-term success. Innovation might sound like the flavor of the month, but in the future, success will be on the side of organizations that know how to do it and excel at it.

How does project management foster innovation at your organization?
Posted by Roberto Toledo on: August 14, 2014 09:30 AM | Permalink | Comments (3)
ADVERTISEMENTS

I have made good judgements in the past. I have made good judgements in the future.

- Dan

ADVERTISEMENT

Sponsors