By Ramiro Rodrigues
A good definition of the word “maturity” is the state of people or things that have reached full development.
For entities such as business organizations, maturity needs to be associated with a specific expertise. This can apply to operational, technical and also project management maturity.
Project management maturity means that an organization is conditioned to evolve qualitatively in order to increase the chances for project success.
To this end, there are both paid and free maturity evaluation models on the market. The application of one of these models allows you to achieve the first important objective: identifying what stage your organization is at.
This step is difficult, given the complexity in trying to compare whether an organization is doing its projects well in relation to others, without being contaminated by individual and subjective perceptions. Often, most models will question various aspects of how projects are executed and produce a score for ranking. With this result, the models will classify the organization's current maturity level.
Once this level has been identified, the next step is to try to plot an action plan to move to the next level. Here is another benefit of a good maturity model: Many offer references to the most common characteristics expected in each level. With this, it is easier to draw up a plan of action focused on the characteristics expected at the next level. This progress should be incremental—one level at a time.
The action plan should be thought of and executed as if it were a project, following the good practices and methodology of the organization itself. It should be scaled to be completed in time to allow its gains to be observable and perceived by the organization. This will then cause the expected positive impacts in the next cycle of a new maturity survey.
In summary, the steps to be followed are:
1. Apply a maturity search.
2. Evaluate and disseminate the results of the first survey.
3. Develop an action plan.
4. Rotate the project to the evolution of the level.
5. Go back to step one and continuously improve.
By following this sequence, you can foster a constructive cycle in your organization as you continue to evolve your ability to execute projects.
I’d love to hear from you: Have you used maturity models in your organization?
By Peter Tarhanidis, PhD
I’ve been fortunate to have a career that constantly challenges me and my team to apply new approaches to achieve an organization’s mission. I believe that adapting these contemporary management practices and innovative operating models has helped me become the project leader I am today.
Below are select project initiatives that have helped me develop my skills:
What themes have you identified in your career? How have you broadened your range?
By Kevin Korterud
It’s quite possible that, if asked to remember every project I led over the years, I would be hard-pressed to do so. Our typical project management journey takes us down a new road when we complete a project, so we’re never really stopping to take a retrospective on how each one shaped who we are today.
A much easier exercise for me is to recollect which projects played a significant part in shaping my journey as a project manager. These projects, not unlike silver polish, brighten our skills and capabilities to a shine that allows us to undertake even larger and more complex projects.
Here are three projects that had a profound impact on my capabilities, and what I learned from each:
Up till a certain time in my project management career, I felt that my work included some rather large projects in terms of team members and scope. However, nothing prepared me for the massive construct that is a transformation program involving almost 2,000 people.
Transformation programs extend well beyond the realm of what project managers normally lead. They involve significant changes to business processes and technology, as well as altering what people do on a day-to-day basis. In addition, there are many project and team members involved with multiple, parallel tracks of work. All of this makes a project manager feel as small as the tiny people in Gulliver’s Travels.
Transformation programs pushed me to think and engage externally beyond my assigned project, especially when it came to dependencies between projects. I also realized it was essential that project managers collaborate and cooperate in order to maintain progress for the overall transformation program.
2. Technology Is in Everything
Over the years, I have followed with great interest the increase in the proportion of a project that involves technology. On my first projects many years ago, the level of technology was quite modest, relying mostly on data inputs, online screens and reports that augmented existing business processes. Today, technology permeates nearly all facets of a project.
When asked to assist with the estimation and implementation of a new type of airliner, my initial assumption was that there would be some form of enabling technology and the airliner would still operate as before. For example, there would be some technology support required, but the fundamental functions would not really change.
After reviews and discussions, I was astounded at the depth of technology that was found in this new model. The flight deck had provisions for laptops to be used by pilots to both prepare and operate the airliner. Flight operations and integration tasks that were once managed manually were now conducted automatically and at high speed, all of which reduced pilot and ground crew workloads. The technology found in this new airliner caused me to dramatically re-think the level of rigor required to estimate and plan its implementation. In addition, it raised my expectations of the effort required to estimate and plan today’s projects in order to ensure quality delivery.
As we consistently execute project delivery over and over across a number of projects, our growing confidence can sometimes cause us to view project delivery as commonplace. We can begin to lose our sensitivity towards project outcomes as we proceed through a seemingly endless stream of phases, sprints, tasks, activities and artifacts of project management.
A big wake-up call for me occurred when I led a project to process calls from customers of infant nutritional products. Customers would call in on a variety of topics ranging from inquiries about the right product to use as well as potential infant health issues. Before I formally began the project, the sponsor reviewed with me existing customer cases showing both simple inquiries as well as potential emergency health issues. I realized then that my efforts on this project could potentially save the life of an infant.
It’s easy to think about projects as two-dimensional entities that refine business processes and technical capability. From the dialogue with the project sponsor, I came to appreciate how this project could improve both the time and quality of response on an inquiry related to the health of an infant. This motivated me and the team to always be thinking about how this project would interact with the customers in the most effective and efficient manner, especially when the life of an infant could be at stake.
As we all proceed through our project management careers, we tend to remember the distinct impact these projects had on us. Some of the projects affect how we plan projects, others influence project execution and still others will be remembered for how they served as key waypoints in our project management journey. In addition, these “waypoint” projects are well-suited as experiences to share with the next generation of project managers following in our footsteps.
What projects on your project management journey have shaped who you are today?
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.
By Wanda Curlee
PMI is celebrating its 50th anniversary this year, an occasion that has led me to reflect on projects from my past. While I don’t have 50 years of experience, I do have 30.
Over those years, I have been a project manager or project team member across many industries. But by far, I’ve learned the most on Department of Defense (DoD) projects. In fact, my very first project was a DoD project. I’ve found that in this industry, the project manager is responsible for all aspects of a project. And when I say all, I mean all.
The project manager needs to understand the contract from beginning to end. From my first federal project to the most recent one, the contract was well worn, as I would look at it many times a day.
On a federal project, there are various sections of the contract. For example, Section B describes how the supplies or products are to be formatted and supplied. Section C is always the statement of work (SOW). Other sections provide the names of administrative and technical contacts, how invoices should be formatted, when the invoices need to be submitted and what supporting information is needed.
There is a section that lists all the rules, regulations and laws that the contractor must follow and obey. This list usually runs more than five pages, printed on both sides and single-spaced.
The statement of work is also always very detailed. Think about a contract for a nuclear submarine, an aircraft or some other vessel—the SOW would be tens of thousands of pages. While I never managed those types of contracts, I did oversee some pretty intense technology programs, where the SOWs were thousands of pages.
I learned that having a team I could trust was instrumental in delivering a complex project. Trust meant that the team understood the needs of the project. They knew when deliverables were due and what the client expected, and they kept everyone informed if there were issues or delays. The team also kept detailed records and updates. This meant the project manager should never be blindsided, and with that, neither should the client.
Of course, I did not learn all this on my own. I had a wonderful boss/coach who saw my potential. He took the time to explain why things were happening the way they were. I was allowed to work in different departments to learn how each area affected the project. To this day, I am very thankful, and I pay it forward. I have always taken the time to mentor and coach those on my project teams or in organizations I ran. The greatest reward was to see those I mentored surpass me in rank within the organization.
When I think back to the moment where I earned my chops, it was a U.S. Air Force project to design a paperless office and non-hackable email system. Don’t laugh! As you may have guessed, the initiative was not successful. Within two years, the government canceled the project. But one thing I’ve learned over the years is this: Unsuccessful projects provide a wealth of learning, maybe even more than successful projects.
What have been the most influential projects you’ve worked on throughout your career?