Guessing is not a strategy: How to build decision velocity with AI and real-time data
June 10, 2026 | Live Webinar
Multi-Project Schedule Planning, Part I
Categories:
Project Planning
Categories: Project Planning
| Projects are rarely planned and executed in isolation. In general, they have external dependencies on activities, tasks or deliverables outside the project's reach. Managing tasks and dependencies that spread across several projects, which are not necessarily part of a program, creates a multi-project management context. For instance, say you are managing an IT project, delivering a software application. Many of your project tasks will be conducted within the project's boundaries and with the full control and ownership of your project team. Nevertheless, your project has dependencies on a software component, developed in parallel by another team within the same enterprise, yet as part of an entirely different project. Your project will have to wait for the other team to finish and deliver its component to deploy and test your software application. Since the two projects have phases and deliverables dependent on each other, their project schedules will have to be correlated. Managing correlated schedules requires a different approach. In a single-project context, a project manager plans the schedule, giving consideration to the project context, the work to be carried out by the project team, assumptions, risks, and the tasks' internal and external dependencies. This is more or less a silo approach, where the external dependencies rely on deliverables and not on the project phases or cycles in which they are produced. In a multi-project management context, the project managers involved, or an overseeing multi-project manager, will have to reach alignment across the projects in several aspects, including:
Let's go back to our previous IT project example, and how alignment could happen. The two projects start off independent of each other. Then they can have touch points during the requirements analysis and scoping phase, when your project team will analyze and hand over requirements and product specifications to the other team. Then the two projects will meet again during a joint testing phase, when both project teams will deploy and test their application components integrated together. Finally, the two projects will meet again during the go-live deployment, when the rollout of one project will not be complete without the rollout of the other. The more touch points the projects have, the more complex their schedule planning will be. The stronger their dependencies, the less flexibility you will have when planning your project schedule. And the more relevant the other project is for your organization, the less planning flexibility and schedule control you will have on yours. The situation gets even more complicated when your project depends on three or more other projects, which have different schedule plans, business criticalities and even project management approaches. For instance, your project is conducted in a waterfall methodology, and it's dependent on another project following an agile approach. It can become quite challenging aligning your waterfall schedule to the iterative and dynamic schedule of the other project. What is your project scheduling experience with dealing with multiple projects that depend on each other? |
Do's and Don'ts for Portfolio Managers
Categories:
Portfolio Management
Categories: Portfolio Management
| Jen L. Skrabak, PMP, is a senior-level project executive, leading high-profile business transformation projects, programs and portfolios. She has more than 18 years of professional experience across industries such as healthcare, biotechnology, entertainment and financial services. She recently established a PMO Center of Excellence that includes both project managers and business analysts, implemented a global US$50 million program across multiple sites and managed a $500 million portfolio. Ms. Skrabak served as the committee chair for The Standard for Portfolio Management - Third Edition. Read her thoughts on portfolio management below: Although PMI's The Standard for Portfolio Management was updated for its Third Edition earlier this year, I still find that there is much confusion over what portfolio managers do and how they differ from program and project managers. Having been a portfolio manager for over 10 years, I'm offering a few key differences that may help you. What portfolio managers focus on:
Now that we've level set the strategic responsibilities of portfolio managers, there are some key responsibilities that don't fall under portfolio managers. What portfolio managers do not focus on:
PMI Announces PfMP certification Recently, PMI announced its new Portfolio Management Professional (PfMP)SM credential, which will be available in Q4 2013. Having served on the Steering Committee for the PfMP credential, and providing strategic direction and guidance to the team that was chartered to make the final recommendation, it is very exciting to see this launch. I know that many in the PMI community have been asking about this certification. Having also served as chair for the development of the portfolio management standard, I believe that it's an important credential that meets a key need (remember the "P" in PMI encompasses portfolio). It drives advancement of portfolio management as a profession by formally recognizing the importance of a standard set of skills, knowledge and abilities. Key requirements include eight years of business experience and at least four years of portfolio management experience. It's expected that The Standard for Portfolio Management - Third Edition will be used as a key reference for the exam. The PfMP exam outline will be made available in September, with the first opportunity to take the exam in late Q4 2013. If you want to be one of the first to be certified for the PfMP, email [email protected]. |
Get With the Program
Categories:
Program Management
Categories: Program Management
| For the past two decades, television dramas in Taiwan have faced fierce competition from Korea, mainland China and Japan. But in 2011, a modern Taiwanese drama -- "In Time With You" -- managed to challenge these markets, with ratings that rocketed to 2.7 million viewers. The production team responsible for this success warrants a closer look. In television, there is a type of producer known as a "show runner." This person is responsible for both the execution and creative aspects of the show for each individual episode and throughout the series. The role is similar to a project sponsor who not only needs to raise funds, but also has to clarify project scope, acquire the team and determine an acceptable risk tolerance. For "In Time With You," Jason Hsueh is such a show runner. In 2011, Mr. Hsueh started to adapt a Korean TV drama, "The 1st Shop of Coffee Prince," for Taiwan. But he found the terms of the adaptation agreement too restrictive. Eventually, when pre-production costs reached $50,000, he decided to stop -- it would be pointless if he couldn't make creative changes so the drama would be relatable to Chinese-speaking target audiences. This timely decision also stopped further financial hemorrhage of a high-risk project. But more importantly, it forced Mr. Hsueh to reconsider previous drama ideas, including "In Time With You." "In Time with You," a love story written by scriptwriter Hsu Yu Ting, had been considered for years but had not been brought to the screen. The story didn't follow the established formula for romance. However, Mr. Hsueh felt that this light love story, based on the lives of ordinary people, had potential. He boldly adopted a script many others wouldn't have attempted. The foundation of a successful drama is first a good script, and then a good director. Consider the drama to be the project, with the director comparable to a project manager, the person responsible for the production of the show. He or she is the one who puts all the artistic elements together, who brings the story to life by interacting with actors and interpreting the script. Mr. Hsueh knew that if he wanted to decrease risk on "In Time With You," he needed to find the right director. That's why he handed the reins to Arthur Chu, a director famous for a subtle, refreshing touch. Mr. Chu shot every take beautifully, and was very loyal to the original script. He directed the drama with good quality control, and the production team never inflated the script. Plenty of product placement opportunities knocked, but Mr. Hsueh only considered products that were in tune with the original story. This steadfast commitment to the original story -- along with a sophisticated, approachable marketing effort -- resulted in soaring ratings. Through careful execution, a previously neglected idea for a TV drama series became a blockbuster success in Chinese-speaking countries in 2012. It started with a good script (program management plan), a project sponsor and program manager (show runner), project managers (producers and director) and project team (technicians, actors and marketing staff). Even if the success of "In Time with You" was a surprise, it was not an accident. Have you seen program management adapted to other creative industries? |
Join the Evolution
Categories:
Leadership
Categories: Leadership
| Thousands of books, quotes, advice and research have covered the topic of leadership. In contrast, there is far less dedicated knowledge on project leadership. And yet, as mentioned in the opening remarks at PMI® Global Congress 2013 -- EMEA and in a recent Voices roundtable on talent management, project leadership is fast emerging as a critical skill for project practitioners. The Gulf Cooperation Council (GCC), the region where I live and work, is booming with projects, particularly in construction, oil and gas. In the region, project managers have been recruited traditionally for their technical and engineering expertise. However, due to regional growth, the dynamics of the project work force are changing, and so are expectations of project managers. It is now common for a typical core project team to be made up of members aged 30 to 60, with a mix of locals and expatriates from at least five different nationalities, all working together in one location. This environment of change and uncertainty requires project professionals to become more responsive, adaptive, people-centric and emotionally intelligent. For these reasons, I presented a lecture on this subject at a recent PMI Arabian Gulf Chapter meeting. From the discussion that evening, there seemed to be concerns about the role of a project leader versus the one for a traditional project manager. The main points of concern that I clarified that night were:
Getting into specifics, I proposed these ways in which a project manager differs from a project leader:
Although not everyone agreed with me, I insisted that project leaders are made from experience, so building leadership skills is something every project professional can do to work through the changing business environment. To that end, leadership skills and experience can be gained by:
Finally, to help you establish a project leadership mindset, regularly ask yourself:
How can a project manager evolve to encompass a project leadership role? |
Tips for First-Time Global Project Managers
|
A project manager's first global project marks a pivotal time in professional development. A project with global scope offers an exciting opportunity to work with people from many different cultures and skill sets. However, global projects also come with unique challenges. These can include large physical distances between implementation teams, language barriers, country-specific regulations and other considerations that can negatively affect your project. To get off to a good start, project managers need to manage the differences between global and co-located projects within these essential elements: 1. Requirements: On a co-located project, there is a single set of project requirements. On global projects, it is common to encounter both global (such as quarterly financial reporting) and country (such as provincial tax) requirements. Failure to consider them can cause painful functional gaps upon implementation. Work with your project leadership team to define a prioritization scheme for both types of requirements. For example, prioritize the country requirements by regulatory mandate, business value and desired need. A prioritization scheme helps you achieve overall balance in meeting the project success criteria. 2. Estimation: A global project typically features added complexity and costs not found with a co-located project. This calls for estimation to include additional effort to manage the previously mentioned requirements, as well as cross-geography coordination. The latter can include things such as team member travel time and global communications. In addition, there can be additional costs, such as import duties on equipment, that can add to the overall estimate. To ensure good estimation, identify global and local estimation components to more accurately account for the additional complexity. 3. Scheduling: Scheduling milestones, effort and resources on global projects is one of the greatest challenges for a project manager. The first thing to remember is to include country-specific scheduling considerations, such as regional holidays and vacations. In addition, always leave room in the schedule for project risks that can arise from unstable governments, new regulations and labor disputes. Finally, be prepared for unexpected surprises from nature, such as snowstorms, floods, volcanic eruptions and other disruptions. If such an event happens, meet with your leadership team to discuss whether to reset the project schedule around the unexpected surprise. While global projects can present some unique problems, they also can be very rewarding when managed properly -- even if a volcano erupts! What tips do you have for first-time global project managers? |