This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
I earned a master’s degree in economics and worked in the field for a few years before shifting to project management. Despite the shift, I continue to use economics as my primary lens for analyzing the world around me. Recent project management industry changes prompted me to consider its economics. This article aims to provide data-supported context and analysis.
Sometimes, great leadership appears effortless. The leader’s actions seem intuitive and simple, yet the impact is powerful. I was inspired by US Navy Captain Chris “Chowdah” Hill, who earned the nickname for his thick Boston accent. I stumbled upon him while listening to a podcast on conflicts in the Middle East. Captain Hill commands the US Navy’s nuclear aircraft carrier, Dwight D.
Meteorologists are better at predicting the weather than project managers are at delivering projects. About a third of projects are delivered on time, on budget, and with the desired scope. By contrast, a seven-day forecast is accurate about 80% of the time. So why is project success so elusive? Intentionality is lacking.
Stakeholder alignment—or lack thereof—can be the difference between project success and failure. In today’s dynamic business environment, projects face multiple stakeholders and constituencies. Often, these groups have competing or divergent interests. Project managers often focus on the “hard skills” to ensure adherence to the triple constraints of scope, schedule, and cost.
Hybrid projects are not constrained by a single methodology or well-defined framework. By definition, they are a melding melding of practices. A huge responsibility accompanies this unbounded freedom of choice. Project managers must clearly describe how the project will be executed to be successful. Shirking this responsibility is detrimental.
I authored my first project management article 10 years ago. A mentor recommended I start writing to launch my transition from managing project organizations to teaching. Writing those early articles was challenging. Reducing complex ideas into writing is a skill requiring practice and discipline. I did not anticipate having so much to say.
We should view project management approaches as a palette of options. Predictive, Agile, and Lean/Kanban form the boundaries. Hybrid is the vast interior space. The first article in this series described the boundaries and color-mix of approaches: This article discusses how these approaches may be reflected in central project management domains.
Hybrid project management just had its breakout moment! The Project Management Institute’s Pulse of the Profession® 2024 reported that hybrid (32%) is now the second most commonly used approach. Predictive (44%) still holds a commanding lead. And, agile (26%) use fell by 2 percentage points. Before we get too excited, the State of Agile Report shows different trends.
Thank you Mr. Zucker the great class, I truly have a better understanding of Agile and the approaches used. I appreciate your enthusiasm and extensive knowledge on the subject – awesome job teaching us and encouraging participation. Look forward to seeing you in another class.
A picture is worth a thousand words. Projects can generate a lot of data. Large, mature organizations generally have the tools to capture, store, and analyze this information effectively. However, small and less mature organizations and those leading non-traditional efforts often lack the tools, practices, and experience.
Making good decisions is a critical project management skill. The challenge is to create a fair, efficient, effective, and transparent process for our teams and stakeholders. In a McKinsey survey, only 20% of respondents stated their companies excelled in decision-making. The path to the answer is often as important as the solution.
Shift-left is an Agile/DevOps call to action. It signaled the need to address quality sooner. As we adapt to the current dynamics, we should challenge standard paradigms and reevaluate when to execute project processes. Timing is crucial for successful project outcomes.
Time is our only finite resource. We cannot buy it or create it. Therefore, we must spend it wisely. Effective time management is a critical project management competency. Regrettably, many teams lack these skills or discipline and consequently fritter away their time. There is not a silver bullet to managing time more effectively.
Words matter. Even in project management. Words can carry meaning far beyond their formal definitions. Connotation and perception can have unintended consequences. Even basic project management terms can create misunderstandings that can disrupt or derail a project. In this article, I expose some linguistic pitfalls impacting the profession.
An agile backlash is underway. Some organizations have declared victory, fired their agile staff, and moved on. Others are agile in name only or are “doing” agile but have not fundamentally changed the way they work. We should not blame Agile for bad Agile. The problem is not with the values, principles, and practices. Instead, it is with organizations and their approach to agility.
Artificial Intelligence (AI) will transform project management. Gartner estimated that AI may replace 80% of project management activities by 2030. A recent article in the Harvard Business Review described “How AI Will Transform Project Management.” I say, “Bring it on!” I look forward to the opportunity. AI is powerful, potentially disruptive, and will change what project managers do and how they.
ChatGPT generated this article to demonstrate the difference between human and AI-generated content. The prompt was: “As a project manager, I want a 500-word description of how AI and machine learning will impact project management.” Artificial Intelligence (AI) and Machine Learning (ML) are revolutionizing industries across the board, and project management is no exception.
We make hundreds of assumptions and take small risks daily. Without them, we would spend innumerable hours worrying about everything. We assume our car will start. Our air conditioner will work. The weather forecast is accurate. These daily assumptions are banal. Recovering from these risks may be inconvenient but not horribly impactful. Project assumptions and risks are not as casual.
Software projects have two measures of success. First, building and implementing working software. Second, having people use and adopt it. Project managers tend to focus their attention on delivering the application. But the project’s real success rests on user adoption. Once, I led a large project. The application was delivered on-time, on-budget, and with the documented scope.
Large enterprises and government agencies increasingly turn to Agile for their software projects. This is a difficult shift, with many struggling to fit their new round agile pegs into their existing square waterfall holes. Cultural, structural, and procedural impediments make “being agile” a challenge. Agilists may be critical and call this “fragile-agile” or “agile-fall.” We should commend these.
Agile seems like a mystery to many. It has an unfamiliar vocabulary and practices. To outsiders, it feels like an exclusive club. However, when we step back and inspect agile, we see that it follows common, recognizable patterns from our daily lives. Imagine it is Thursday evening. Your family is planning the upcoming weekend. There is a fixed amount of time and many things to do.
Einstein spent the last 30 years of his life searching in vain for a unifying theory of physics. The project management profession has had a similar quest—defining a methodology, set of practices, or principles that could successfully guide any project. Like physics and nature, project management is ubiquitous. Projects address simple, complicated, and complex problems.
An Agile workflow is a timeline of steps you need to start, work, and finish an Agile project. Agile workflows break projects into short, repeated phases. Teams use these cycles to seek customer feedback and add updates to the deliverable. Workflow phases or sprints last from one week to three months, during which time teams commit to finishing a limited set of tasks.
The project charter is a foundational deliverable created during the project’s initiation phase. The charter documents the project’s purpose, planned direction, and what is initially known. It may be called a charter, proposal, grant, or request. It may be a formal contract or a less formal document. Regardless of the format, articulating the project’s intent is invaluable and harder than expected.
The Milestone-Kanban Schedule (MKS) is a hybrid project scheduling and management technique that combines traditional and agile best practices. The technique is well-suited for simple and complicated projects where the required deliverables are clear, but the time and effort needed to create them are not. It embraces iterative planning, uses milestones to establish a project roadmap.
The project management plan (Plan) is a powerful tool. It describes how the project will be executed. It should be tailored based on the project’s context and needs. A good Plan reduces the likelihood of misunderstanding, conflict, and disappointment. Unfortunately, in the rush to start a project, insufficient time is often devoted to creating the Plan.
Frederick Winslow Taylor shaped the field of management science. He believed systematic and scientific methods could be applied to managing operations and production. His work inspired the formation of the Harvard Business School and the modern assembly line. The Academy of Management named his Principles of Scientific Management as one of the 20th century’s most influential books.
Disciplined Agile® (DA) and the Scaled Agile Framework (SAFe®) are two popular, second-generation agile methodologies. They build on lean-agile thinking; and standard Scrum, Kanban, and DevOps practices. They offer practitioners tools to extend and mature their agility beyond the team to programs and the broader enterprise. They emerged about a decade after the Agile Manifesto.
Servant leadership and self-organizing teams are foundational Agile characteristics. However, defining these principles is like explaining gravity to a child—clear, tangible descriptions are elusive. The image of an English butler still comes to mind when I hear “servant leader.” We can use simple rules to deconstruct, visualize, and describe these abstract concepts.
To successfully transform our organizations and adopt new ways of working, we need to understand how we got here. The study of management is a social science. It influences our thoughts, management practices, and organizational behaviors. Social sciences provide valuable insights. But they are not always testable, timeless, or universally applicable.
Agile was initially conceived to deliver software projects more quickly. We have now learned to apply these principles and practices well beyond technology. Leading enterprises are now focusing on business agility—building the organizational capability to respond more quickly to the ever-changing competitive landscape. Seventeen technology thought-leaders from around the world gathered at the.
Agile is a mindset described by a set of values and principles. It traces its roots to Lean, which is also foundational to other modern management theories. Lean’s primary focus is delivering value quickly and eliminating waste. Toyota was a Lean pioneer. Out of necessity, it needed to be very efficient to compete. It dramatically decreased the cost of rework by building quality into every process.
Conflict exists. It is a natural part of being human. It occurs at home and at work. We disagree. We have different perspectives and opinions. We get upset by things that were said, or not said. These events arouse our emotions. We become angry or afraid. When there is conflict, we cannot control the other person’s behaviors. However, we own our response.
The Gantt Chart is the most widely used project scheduling tool. It visually depicts the project’s activities, when they will occur, and their interdependencies. When used correctly, it is powerful. Unfortunately, most Gantts are poorly constructed, stripping them of their value. Henry Gantt developed the tool a century ago. The original Chart was simply a horizontal bar chart showing the timing.
Agile teams are described as “self-organizing” or “self-managing.” But what does that really mean? The terms are frequently used but not widely understood. For teams to “be” Agile, they need to know how to act. Behaviors describe actions. They are observable and universally evident to all team members. To “be” Agile, teams should identify and clearly label the desired actions and interactions.
Economics is the social science that studies making choices subject to constraints. Project, program, and portfolio managers make economic decisions daily. We try to maximize value delivery subject to the constraints of time, cost, quality, risk, and resource availability. Economics can help project managers make more informed decisions. It provides frameworks to evaluate different options and.
Excellent “soft skills” differentiate the great project managers. Since 90% of a project manager’s time is spent with others, it is no surprise that communications and emotional intelligence are vital traits. They are situationally aware, assess context, and communicate more effectively with their teams, customers, and stakeholders.
Let’s be honest, most project schedules disappoint. They are unrealistic, complicated, and do not help guide execution. For decades, Gantt charts, network diagrams, and the critical path method have been the standard practices. Even with these powerful tools, only about half of all projects are completed on time, as reported in the PMI Pulse of the Profession.
Project managers rarely face ethical dilemmas. We generally do not make life-or-death decisions or need to choose between “right” and “wrong.” However, we need to be prepared and have a framework for confronting these circumstances when they arise. My career is probably more colorful than most: I managed the United States Treasury securities’ auctions when the fabled investment firm.
Assumptions and risks are embedded in our daily lives. We expect the day will unfold as planned, and risks will not materialize. Most of these assumptions are benign, like thinking the weather report will be accurate; or no major calamities will occur. Projects are built on assumptions. Without them, it would be impossible to proceed. But some may lead to unanticipated or even tragic consequences.
Large enterprises struggle to manage their project portfolios effectively. They fall prey to the fallacy of optimizing resource allocation. Or simply stated, they focus on making sure everyone is busy rather than getting things done. Team members are allocated at least 100% to project work, if not more. As a result, people are working on multiple projects—more than they can realistically juggle.
Selecting a project management approach and framework is complicated. Not that long ago, it was like buying a Model-T Ford; you could have any color you wanted, as long as it was black—our only option was Waterfall. Today Waterfall is still a choice. There are also multiple Agile frameworks, or you can mix-and-match and go Hybrid. So many choices.
Project management theory established the Triple Constraint (aka, the Iron Triangle) as the key to project success. If the scope is known and fixed, then the schedule and cost must adjust to accommodate scope changes. The simplicity of this proposition is appealing. At the beginning of the project, all requirements are documented, the design is approved, and nothing should change.
We organize all of the trending information in your field so you don't have to. Join 100,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content