What Can We Learn From the Movies?
By Ramiro Rodrigues
I'm 50 years old, which means I was born the same year PMI was founded. The last half century has seen a lot of interesting projects across industries, but today I’m going to focus on one area in particular: cinema. I’ll start with a question: What swept the Oscars in 1969? You may know it was Oliver!—a British musical based on the work of Charles Dickens. In addition to best picture, the movie also won the awards for best director, musical score, art direction and sound. The magic of cinema progressed in parallel to the 20th century at large, and I’ve long admired its ability to create fantasies and magnetize audiences. These same capacities evolved as technology and investments provided more technical resources for the enchantment of the audience. The delivery of a movie has always impressed me, as it has all the ingredients of a project. There is conception, planning, execution, control and conclusion—all with the added complexity of dealing with human emotions even more so than in other business segments. Today's major productions involve hundreds of professionals, suppliers and deliveries, so they require a well-structured project management model. And if the delivery of a movie provides all these difficulties, imagine what it takes to deliver a saga of 23 films? Well, this was the case for the so-called Marvel Cinematic Universe. Why should we consider this a grand project? Starting with the first movie, Iron Man, in 2008, you can find several “Easter eggs” referencing the other Avengers. And in the post-credits scene (a practice that started there), Nick Fury appears to talk about the Avengers initiative. Thus begins an intricate sequence of characters and films over 12 years, which translated into the largest franchise and box office phenomena of all time. If it was not enough complexity to produce a single film of this nature, imagine the magnitude of a long-term project that would involve scores of producers, suppliers and actors. And this was accomplished while delivering a structured and coherent plot that lived up to the expectations of a global audience. This gives us clues into why more and more cultural producers are looking to specialize in the best practices of project management. These principles have much to contribute to ensure organization and control, without interfering with the magic and emotions that art provides. After all, the show must go on! I’d love to hear from you. Do you see movies as projects? Share why or why not below. |
3 Project Management Lessons From a 70.3 Ironman
By Conrado Morlan I’ve been running for eight-plus years—ever since my son suggested I do a half marathon in San Antonio, Texas, USA. So when a friend suggested I try a triathlon, I was ready for it. At that point, three years ago, I had 10 full marathons and 15 half marathons under my belt. The triathlon includes three disciplines in a single event: swimming, cycling and running. It was the athletic challenge I needed, similar to the professional challenge I encountered when I moved across industries to keep leading and managing projects. To get ready for the triathlon, I had to go back to the pool and start swimming after a long time away. I borrowed a road bike from a friend to start the formal training. We worked out on our own on weekdays and as a team on weekends. That first experience transformed me into a triathlete enthusiast, which led me eventually to the Ironman 70.3. The "70.3" refers to the total distance in miles covered in the race, consisting of a 1.2-mile swim, a 56-mile bike ride, and a 13.1-mile run. The short distance triathlons helped prepare me for the Ironman 70.3. And as I’ve come to realize, learnings I’ve made along the way also apply to project management. These are my three main findings: 1. Expertise and Experimentation Mastering all three disciplines in a triathlon can be difficult. My background is in running, but I was new to swimming and cycling. My coach gave good tips and workouts that helped me manage my bicycle on hills, navigate sharp turns and use all of my leg muscles to have a better stroke. For swimming, I followed my instinct and experimented with the breaststroke. I soon felt confident in the pool and gradually in open waters. My experiment worked out, as I finished my swim in the Ironman 70.3 about 20 minutes ahead of the cut-off time. As a project management practitioner, you may have mastered an industry-standard methodology and need to catch up with the new trends. In the triathlon, you may not transfer skills from swimming to cycling or running, but in project management, you can. Communication, time management, and people management are required regardless of the methodology or best practice that will be used in the project. This gives you room to experiment. At project checkpoints, you can inspect, adapt and make the required changes to improve your project and be successful. 2. Transition Is Key The transition is where the triathlete moves from one discipline to another, changing equipment. The area should be prepared in advance, with the gear set up in a way that helps the athlete have a smooth and fast transition. The time spent there may define the winner of the competition. I would compare the transition area with the risk registry. The more prepared the project manager is, the less impact there will be to the project. The “gear” in your risk register will include the most impacting risk(s), the risk owner and the actions required to mitigate the risk if it arises. It’s a working registry, so the project manager should keep adding risks during the project as required. 3. Anybody Can Help You A triathlon is not a team event, but that does not restrict the triathlete from getting support from others. Before the competition, the athlete may have followed a training plan supported by a coach, they might have been mentored by fellow triathletes and, last but not least, they likely benefited from family support. It’s common for some triathletes to have a race sherpa on the competition day. The athlete and sherpa will discuss beforehand what tasks each will take on during the race. In short, a race sherpa will lend a hand whenever necessary and cheer for the athlete during the competition.
As a project manager, you have your project team, stakeholders and sponsor(s), but that does not restrict you from getting help from people outside the project. You may have an internal or external mentor, somebody in your organization who can be influential and help you address issues. I used to have a list of people in the organization I contacted in advance. I let them know about the project and asked them if I could ask for support if needed. That simple action helped me on several occasions when I faced a challenge. If you are an athlete and a project manager, what lessons have you learned from practicing your favorite sport? Please share your thoughts below. |
Follow These 3 Steps to Validate a Variance
By Lynda Bourne As you may know, any monitoring and control process has three components. The first is establishing a baseline that you plan to achieve, the second is comparing actual progress to the plan to see if there are any differences, and the third is taking corrective or preventative action. Corrective actions fix existing problems, while preventative actions stop problems from occurring in the future. This post looks at the middle phase. Before taking action to bring performance into alignment with the plan, make sure the variance you are seeing in the control systems is real. Corrective and preventative actions take time and usually involve costs, and there is no point in expending effort where it is not needed. The variance is the difference between two imprecise elements: the planned state and the actual situation. The plan is based on estimates and assumptions made some time ago about what may occur in the future. All plans and estimates have a degree of error built in; it is impossible to precisely predict the future of a complex system such as a project. Similarly, the measurement of the actual situation is prone to observational errors; key data may be missing or the situation misinterpreted. So how do you decide if the measured variance is real and significant enough to warrant corrective action? I suggest considering the following: 1. Does the reported variance line up with your expectations? 2. Is the variance significant? 3. Is a solution viable? Let’s explore these in depth.
Does the reported variance line up with your expectations? Try looking at a couple of different monitoring systems, such as cost and time. Do the two systems correlate, or are they giving you very different information on the same group of activities? If they correlate, perhaps your expectations are misplaced. If they are giving you different information, there may be data errors. Is the variance significant? If the predicted slippage on the completion date for a key milestone over a series of reports is bouncing around, any single measurement within the noise factor is likely to be insignificant. Trends, on the other hand, highlight issues. Sensible control systems have range statements that indicate the variance is too small to worry about if it is inside the allowed range. This general rule is modified to take trends seriously and to require action to correct negative variances close to a milestone or completion. Is a solution viable? Other situations are simply not worth the cost. There is no point in spending US$10,000 to correct a -US$5,000 variance. However, this decision has to take into account any effect on the client and your organization’s reputation. Cost overruns are generally internal, whereas late delivery and quality issues may have a significant reputational cost, affecting stakeholder perceptions. Where a viable option exists to correct negative variances, corrective and preventative actions need to be planned, prioritized and implemented. There is no point wasting time on a controls system that does not generate effective controlling actions. Closing Thoughts Second, implementing corrective and preventative actions requires the resources working on the project to do something different. Variances don’t correct themselves, and simply telling someone to catch up is unlikely to have any effect. Sensible management action, decisions and leadership are needed to physically change the situation so there is a correction in the way work is performed. This is a core skill of every effective manager. I’d love to know: How do you deal with variances in your projects? Please share below. |
Unlock the Value of Artificial Intelligence
Categories:
Agile,
Benefits Realization,
Best Practices,
Calculating Project Value,
Change Management,
Complexity,
Innovation,
Leadership,
Leadership,
Nontraditional Project Management,
Portfolio Management,
Program Management,
Project Delivery,
Project Planning,
Project Requirements,
Roundtable,
Strategy
Categories: Agile, Benefits Realization, Best Practices, Calculating Project Value, Change Management, Complexity, Innovation, Leadership, Leadership, Nontraditional Project Management, Portfolio Management, Program Management, Project Delivery, Project Planning, Project Requirements, Roundtable, Strategy
Artificial intelligence is no longer a tool we’ll use on projects in the future. Right now, many organizations are formalizing the use of advanced data analytics from innovative technologies, algorithms and AI visualization techniques into strategic projects. The maturity of advanced data analytics is creating an opportunity for organizations to unlock value. The McKinsey Global Institute estimates AI’s global economic impact could climb to US$13 trillion by 2030. As an example, in the healthcare industry, Allied Market Research reports rising demand for data analytics solutions due to the growth in data from electronic health records, among other factors. The global healthcare analytics market was valued at US$16.9 billion in 2017, and the report forecasts it to reach US$67.8 billion by 2025. The Evolution of AI Maturity Everyday examples of these solutions range from simple automated dashboards, remote check deposit, Siri-like assistants, ride-sharing apps, Facebook, Instagram, autopilot and autonomous cars. Tips on Successful Transformation As a project leader, take these steps to avoid key pitfalls:
Please comment below on what approaches you have taken to enable advanced data analytics in your role or in your organization. |
Tips for Project Success in a Functional Organization
There are fundamentally two types of organizations: functional and projectized. Of course, between those there are various combinations of functional and projectized in the form of matrix and hybrid. Every organization type has its own advantages and disadvantages, but from the project point of view, functional organizations are most challenging, due to their focus on individual functional work. A typical functional organization has departments like R&D, operations, procurement, human resources, quality assurance and—on occasion—project management. Each department focuses on its own area. The challenge is, projects are often multifunctional, crossing various functions and requiring contributions from all departments. In a typical functional organization, there is no one who looks after projects end to end and connects all the dots. A project manager has little authority over the resources of other departments. All told, this results in several challenges:
Despite all these challenges, a project manager still has the responsibility to make the project successful. How can they do this? Let’s discuss some tools and techniques that a project manager can use:
Until you get to know the stakeholders and analyze their engagement, a project cannot be successful. The communication strategy is key to bind stakeholders, and any communication strategy without proper stakeholder analysis will be ineffective. Moreover, it will lead to chaos.
A project launch, the kickoff meeting is an important event and may decide its fate. It helps in onboarding functional managers, securing their buy-in and building trust. Take time to ask each functional manager what they want from the project in order to support it.
The project will become a struggle if trust is not built among stakeholders, especially in a functional organization. The kickoff is the starting point. Project managers need to build transparency and create opportunities for networking and exchanging ideas. Keep functional managers informed about project progress and seek their help when required. In turn, offer help when they need it. A helping mind set could be key to build trust.
In a functional organization there is a fair possibility that people on the project work in silos. Therefore it is important for the project manager to create networking opportunities for greater interaction among contributors and supporters. Informal networking events could be more effective.
Due to the different goals of independent functions, varied personalities and the loosely coupled structure of functional organizations, different functional managers may have opinions that differ from the project manager’s. To get a functional manager’s buy-in, conflict management skills are essential. Please refer my post The Techniques That Don't Resolve Conflict. A project manager has to find a solution where both the functional manager and project manager feel they’re winning and achieving their goals.
Communication is an underlying skill required to apply all the tools we’ve discussed so far. A project manager has to focus on two aspects: establishing an information system and ensuring effective interaction with team members and stakeholders. A project management information system keeps stakeholders informed and fosters collaboration. Effective interaction requires active listening skills. Here, refer to my posts Listen Up and 8 Steps for Better Listening. Listening skills help you understand others better, do stakeholder analysis, make up your mind and thereby communicate effectively. I’d love to hear from you: How do you drive your projects to success in a functional organization? I look forward to reading your thoughts. |