Author: Andrea Brockmeier

Top 10 Business Trends To Watch For In 2022

By Andrea Brockmeier, Jason Cassidy, Susan Heidorn, Jose Marcial Portilla, and Mike Stuedemann

While 2021 has been better in many ways than 2020, it doesn’t feel much more predictable. Yet, at Educate 360 we have identified some the biggest trends we are seeing and expect organizations to continue experiencing in Project Management, Business Analysis, Agile, Data Science, and Leadership in the year ahead.

Overall, the theme of working remotely comes through loud and clear and we expect it to impact almost every area that we covered.

Here are our Top 10 trends to watch for in 2022. We’d love to hear your thoughts about our observations and prognostications.

Advertisement

Project Management

Project Managers as Project Leaders

The recognition that project managers are both leaders and managers is not new, but the need for the leadership aspect of the role has intensified in the last couple of years and will continue to do so in 2022. In fact, we are hearing more organizations using the title project leader as opposed to project manager.

To be sure, the technical aspects of the job such as scheduling, budgeting, and tracking haven’t been eliminated, but the need for skills like influencing, facilitating, communicating and other “soft” skills associated with the PM as leader has become paramount. Project managers as leaders are going to continue to be challenged in 2022 with distributed teams and all the distractions of ever-changing global and work environments. Leading the team and engaging stakeholders to sustain buy-in is going to continue to be job one for effective PMs in 2022.

More Organizations Using Project Management Tools

In 2022, expect to see a continued increase in the use of project management tools beyond the standard Microsoft Office suite. We used to see only the occasional client using a PM application of any kind and it was almost always Microsoft Project. Whether because people are working remotely, tools have become more cost effective, or tools have become more accessible and easier to use, we see more organizations using PM-specific tools and we’re seeing a wider variety of tools, as well.

At first this may seem contradictory to the previous trend of project leadership getting emphasized over project management; tools are not generally used for the leadership aspects of the PM role. Perhaps these trends are mutually reinforcing in that tools like Asana, Wrike, Easy Project, Smartsheet and others help with project management which allows the PM to tend to the demands of project leadership. Whatever the reason, we look ahead to 2022 as a robust year for PM tool implementation.

Business Analysis

Strong Facilitation and Communication Skills for Remote Business Analysts

We have all have heard about the Great Resignation – employees leaving their jobs in record numbers in search of better pay and career opportunities, a healthier work-life balance, a less toxic working environment, and desire to continue to work remotely. As a result, many companies are reducing their carbon footprint as well as costs, so they either have smaller offices, holding a space for meetings or providing “hoteling” spaces when employees need or want to go into the office to work. Organizations are also realizing that they can hire talent around the globe.

So, what does this mean for business analysts? It means we must get better at communicating and facilitating in a virtual environment. We must learn how to build trust when we can’t directly “see” stakeholders daily. We must be able to facilitate virtually to ensure we elicit inclusive requirements and not just those from a few vocal stakeholders. We need to learn to creatively collaborate with our team members, colleagues, and key stakeholders to ensure we have their buy-in.

BAs need to think about communicating and facilitating with more intention. This calls for mindful facilitation as opposed to simply the ability to use Microsoft Teams, Slack, or other communication platforms. We are already starting to see – and we continue to see in 2022 – more BAs focus on learning how to create safe, trust-laden, and collaborative environments within which stakeholders readily share information in a world that has been changed forever.

Digital Transformation Strategy Supported by Business Analysis

Digital transformation has been a trend for some years, and it is still going full steam ahead. Yet, most of these efforts fail. There are many reasons cited for this failure; among the most common include:

  • NOT understanding the business problem, but instead just throwing solutions or technology at the wall to see what sticks.
  • NOT determining success criteria so organizations have no way of knowing if the initiative has been successful because there was not a shared understanding of what success looked like.
  • NOT realizing that digital transformation introduces cultural changes in the organization (which is also one of the reasons many organizations had difficulty adopting agile).

Because of these failures, organizations moving toward digital transformation will rely more on business analysis capabilities to effectively address root causes of the problems above. BAs will be used on digital transformation initiatives to ensure the business problem or opportunity has been fully analyzed and understood, to verify that the organization is ready to adopt the new culture, and to identify overall success measures as well as identifying smaller, incremental success measures that can be measured throughout the project.

These efforts will also require a business analyst’s in-depth knowledge of agile business analysis approaches, tools, and techniques that will be critical as organizations strive to become more agile in their ability to respond to customers and competitors. Look for lots of opportunities in 2022 for BAs to plug in as key strategic resources on digital transformations.

Agile

Teams Continue to be Distributed – By Choice, Not Necessity

It can be argued that the COVID 19 pandemic did more to transform the world of work than any document, framework, certification approach or technology. One of the lasting impacts of the pandemic is that distributed teams are here to stay. Product development team members and their leaders will need to permanently adjust to working in a distributed fashion.

While many still share the perception that all Agile frameworks require co-located teams (see principle 6 associated with the Agile Manifesto), technology has advanced to the point where a team adopting a framework doesn’t need to all be in the same location. Continued discipline, particularly in the area of communication and team working together agreements, will be required as teams shift from distributed work by necessity to distributed work by choice.

Scaling – Addition by Addition or Addition by Subtraction?

The marketplace continues to see the emergence and growth of a number of Agile scaling frameworks. The Scaled Agile Framework (SAFe), Large Scale Scrum (LeSS), Scrum at Scale ([email protected]) and Disciplined Agile Delivery (DAD) are just a few of the prominent entries in this space. Next year will see organizations continue to adopt these frameworks as they seek to realize the benefits of being more responsive to change at a global level.

Current thoughts are mixed regarding how to achieve this goal. While many of the current frameworks (e.g., SAFe) advocate adding structure and layers, some like LeSS believe that true organizational agility can only be achieved by removing items from the organization that don’t directly contribute to the delivery of customer value. This debate is even more nuanced when the idea that some additional structure might be necessary on a temporary basis while the organization is being transformed. In 2022, we expect to see continued debate as to what steps are actually necessary to achieve agility on a global scale.

Agile Outside of Software

The Agile movement was born in the software development space. After all, it is called the “Manifesto for Agile Software Development”. In recent years, other domains have adopted a number of the values and principles that define the Agile movement in attempt to accrue its benefits. For example, there is currently an Agile Marketing Manifesto as well as efforts to bring an Agile mindset and some of its practices into education.

This trend will accelerate in 2022 as events such as the pandemic, natural disaster, and political and economic shifts remind organizations that the only constant is change.

Data Science

Increasing Application of Artificial Intelligence and Reinforcement Learning

We often hear that Artificial Intelligence is one of the trends that will change the world. This past year certainly validates that sentiment, and 2022 will continue to see evidence of this powerful trend.

But what is actually meant by the term “Artificial Intelligence”? Technically speaking, AI systems typically incorporate a special type of machine learning known as “Reinforcement Learning.” These specialized programs allow a computer to learn the same way a human does, through experience with trial and error.

In 2016, DeepMind (an Alphabet company) made headlines when its computer program AlphaGo beat the world’s best Go player, a feat many previously thought was impossible. The AlphaGo program worked through Reinforcement Learning methods, where the computer played thousands of games against itself, learning the best tactics to win the game of Go.

Fortunately, Reinforcement Learning has applications beyond just board games. In 2021, DeepMind released AlphaFold 2, a computer AI program that can accurately predict protein folding structures, opening up new possibilities in drug discovery and medicine.

The application of AI and reinforcement learning will definitely be a trend to keep an eye on, as the progress has increased exponentially.

Huge Strides to Continue with Natural Language Processing

Natural Language Processing (NLP) is the use of machine learning models to interpret raw text data, such as Wikipedia articles or even code written by humans. Traditionally, NLP technology has been used for classifying text articles into categories or sentiment analysis of reviews. By simply training NLP models on existing text data sets, the models can learn the topic of a new article, or whether a movie review is positive or negative.

Huge strides have recently been made in the capabilities of upcoming NLP technology. In 2020, OpenAI released “Generative Pre-trained Transformed 3,” commonly known as GPT-3, which has the ability to generate text that is nearly indistinguishable from that written by a human. GPT-3 was trained on hundreds of billions of words that were scraped from the internet and is even capable of coding in CSS, JSX, Python, among others.

In 2021, OpenAI further expanded on the idea of an NLP model that can code, by releasing Codex and Github Copilot. These futuristic state-of-the-art models can not only automatically complete large portions of code, but they can also accept a description of what the code should do and produce the corresponding code. Check out this Codex demo launch video.

The future is already here! We are definitely looking for exciting new applications of NLP continue to make headlines in 2022.

Leadership

Attracting & Retaining Talent – But Different Than Before

Attracting and retaining talent is the most prominent topic of conversation we’ve observed in media related to leadership, specifically attracting and retaining talent in a COVID-changed environment. It’s not clear anyone has permanently figured out the solution as the situation is still in flux, so we have listed key points that we hear leaders weighing in with in their decisions related to remote work and its implications for finding quality team members.

Let’s start by making a broad assumption (that certainly can still be refuted) that some jobs cannot be done remotely (e.g., printing and shipping) and some jobs potentially can be done remotely. Below are the key topics of debate that will continue to shape this discussion in 2022:

  • Job Equity: Is it fair to the people whose roles cannot be done remotely and who have to come into the workplace that others can work at home? As this question is discussed topics related to safety, expenses, commute time, flexibility, teamwork, fairness all come into play.
  • Productivity: Even if jobs can be done remotely, what is the level of productivity of remote work versus work in the office? As this question is discussed one hears that people work longer hours at home because they are not commuting, that people are more productive at home because they can focus and not be disturbed. On the other hand, you hear others say that people are less productive at home because they are distracted by non-work items and that people are less productive at home because they are not being watched. You also hear discussion of managers’ ability to manage in-person versus remote team members.
  • Cultural Impact: Even if a job can be done at home, is it better for the organizational culture? As this question is discussed topics related to collaboration, mentoring, camaraderie, organic problem solving and innovation, and work-life balance come into play.

These debates and questions will dominate leadership conversations in the coming year as leaders continue the challenge of finding and hanging on to top talent.

Jason Cassidy, PMP, is CEO of Educate 360, the parent company of Project Management Academy, Watermark Learning, and Pierian Data. – training partners of choice helping organizations improve organizational efficiency and effectiveness, increase cross-functional alignment, and drive results to help meet and exceed business performance goals.

Andrea Brockmeier, PMP, is Director of Project Management at Watermark Learning, an Educate 360 partner company. Dr. Susan Heidorn, PMP, CBAP, BRMP is Director of Business Solutions at Watermark LearningJose Marcel Portilla is Head of Data Science at Pierian Data Inc., an Educate 360 partner. Mike Stuedemann, PMP, CST, is a Scrum-Focused, Agile Agnostic Coach and Trainer at AgilityIRL and partners with Watermark Learning for Scrum courses.

Join our webinar on December 10 to hear our contributors talk about these trends and answer questions.

Hey Project Managers: Got BA?

The tempo of change and level of uncertainty on many levels keeps organizations constantly having to strategize to sustain their customers’ interest and remain competitive.

Similarly, project professionals have to strategize to keep their organizations’ interest in keeping them on board. It’s an effort that constantly requires learning new tools and developing new skills to remain competitive in the workforce.

For project managers these days, this can be a little angsty as it often seems that interest in projects, per se, is yielding to a focus on products and product delivery. Indeed, PMs today can feel a bit adrift trying to find their place in a product-driven world.

Obviously, agile is a key driver to how organizations orient themselves and their team members to achieving organizational goals. If my students are any indication, nearly all organizations are on some kind of agile journey in at least some parts of the organization. At the very least, an agile mindset is resonating with people at all levels of the business, inspiring them to rethink how they respond to change and uncertainty, and informing the decisions about how to apply resources to achieve business goals.

So what is the best investment of time and money for a project manager, particularly one who may have grown up professionally in traditional, project-driven, plan-driven environments? Projects and the skills and tools employed to manage them aren’t going away. Certainly PM training and certification are always good options. And it goes without saying that any training or skills development related to agile is time well spent.

The other discipline that savvy project managers are wise to invest in today is business analysis. Rather than trying to figure out how to be a project manager in an agile, product-oriented environment, PMs serve themselves and their organizations well by evolving their skills and knowledge to include business analysis.


Advertisement

Business analysis, the activities done to support solution delivery, alignment to business goals, and continuous value delivery, has long been a domain distinct and yet inextricably integrated with project management. The BA role that does those activities typically works closely with the PM, but they are separate efforts; the PM is the custodian of the project and the BA is the custodian of the product. Typically, much BA work is done in the context of projects or programs, so it can get messy as to where the boundaries are, as many hybrid PM-BA practitioners can attest.

A key incentive for PMs to develop BA skills is that those skills and tools are heavily used in agile environments. The various agile frameworks used to handle uncertainty and solve complex problems are customer and product-centered, as opposed to project-centered. PMs struggling to figure out how they fit into agile environments often frustrate themselves and others because they are looking through a different, project-oriented lens. The more organizations mature in their agile practice, the more frustrating this can become.

Business analysis, on the other hand, is used ubiquitously in agile environments and is more fundamentally agile than is project management. BA skills and tools are largely about discovery, facilitating conversations, establishing alignment, and getting to consensus. Project management tools and techniques are, of course, employed in agile environments, but the translation of the role is not as simple and clean. BAs don’t have to figure out how they fit in agile environments like PMs do. The work of business analysis is needed everywhere.

Further, and for a variety of reasons, business case development and pre-project activities, as well as solution evaluation and post-project activities, are often done superficially. PMs who can actively engage in these extra-project activities elevate their value proposition for their organizations.

PMs who are paying attention recognize that a top core competency for just about anyone working in organizations today is business analysis. If you are a PM and don’t know much about business analysis, or if you have not had an opportunity to do BA work in your environment, do yourself a favor and explore how you can develop those skills and get experience doing more BA work. The more you learn, the more likely you will be to see where your PM work has included BA activities. Bonus: Refining your understanding of business analysis will make the distinction between the BA and PM roles clearer and make you better at both!

PMs trying to keep their bearings on how they fit into an increasingly agile world must be looking to develop their skills and knowledge in business analysis. If your organization isn’t specifically on an agile journey yet, they are certainly being affected by it. As agile approaches become normalized and less of something everyone is trying to figure out, so too will the need for business analysis skills.

Risk – Early Conversations Make For Better Projects

Every project and every project stakeholder deserves some risk management, no matter how small or simple the project.

That is a sentiment I often share with my project management students, inspired by an experience I had managing a small project years ago.

I was assigned to a project that had to be delivered in a short period of time. Fortunately, the product was very familiar to me and the team, and we had done similar types of projects in the past. Further, team members already knew each other and the SMEs in the organization who would be providing support.

Even though I had worked with the team members previously, I had concerns about one of them, Jon, because we hadn’t used him in this particular role. I did not think that what he was providing on the project played to his strengths. But since no one else seemed concerned and we were in a rush, I decided to move ahead without any discussion around project risks. I didn’t want to be a nay-sayer. We had done this before and these team members were familiar with the product, the organization, and each other. What could possibly go wrong? I figured we would just cross that bridge if, and when, we got to it.

Well, many weeks into the project, we got to that bridge. Jon produced his deliverable – and it was a mess. Way worse than I could have imagined. Total show stopper. What was even messier, however, was having to tell my sponsor about the problem. As much as anything, I was frustrated with having to present what appeared to be a “surprise” to my sponsor. I wasn’t looking to say, “I told you so,” but the burden of the mad scramble to respond felt heavier than it no doubt would have if the sponsor and others had been aware.


Advertisement

Many late-night phone calls and floor pacing ensued along with considerable stress just trying to figure out how to communicate what had happened. Actually, developing a response to the issue felt entirely secondary to the challenge of communicating that it had occurred. I couldn’t see clear to a solution because I was so concerned about my sponsor’s reaction.

For many, the reaction to something like this on projects is often emotional and poorly scaled. Further, the inclination is to spend time figuring out how a problem could have happened, what could have prevented it, what should have been done differently, etc. While the intention of those reactions isn’t always to place blame, they often leave people feeling like they did something wrong and it can create negative energy on the project. That was certainly the case with this project.

Looking back, a conversation with my sponsor about my concern would have better served the interests of the project and the organization, as opposed to ignoring it in order to move faster to meet an aggressive deadline. In fact, I am certain that we would have accepted the risk and not done anything proactive about it. Talking about it early on, however, would have changed the tone of the conversation once it did happen.

Early discussions about potential threats serve to get concerns in the open so that if they do occur, the reaction from the project manager, sponsor, and others can be more constructive and get to problem-solving faster.

It’s the conversation that matters, and having it early about potential problems is a lot easier than having to initiate a conversation mid-project after an issue has already created problems. They help create a project culture of openness and trust. Most importantly, better project decisions get made, resources are used more wisely, and project tempo is sustained when the risks do occur.

I learned a lot from that experience. No matter how small, how familiar, or how “been here done this” I feel about a project, I make sure we take some time early on to talk about what could go wrong. That makes risks a safe topic, and one that’s likely to be revisited throughout the project – in a tone of partnership.

How about you? What has your risk management experience been on small projects?

What the New PMBOK® Guide Means for PMP Certification and How to Digest It – Part 2

This is the second of a two-part article pertaining to the new PMBOK® Guide. In the first part, I highlighted the changes.

In this second part, I suggest an approach to digesting the new version and share some thoughts about the exam changes.

Thoughts About the PMP® Certification Exam Change 

The big day is Monday, March 26, 2018. That is the first day the revised version of the exam will be administered to reflect the latest version of the PMBOK®. Below are a couple of things to keep in mind regarding this, or any PMI exam update:

Except for the CAPM, PMI exams are not specifically based on the PMBOK® or any PMI standard. They are based on analysis of what people do in a particular role as outlined in the Role Delineation Study (RDS) and the Exam Content Outline (ECO) that is created from that study. The PMBOK® and other standards ensure language and terminology consistency and they help ensure that questions are rooted in the profession’s common, best practices. In fact, the biggest changes to a PMI exam are initiated by a change to the RDS and resulting ECO. Theoretically, then, there is no reason to expect huge changes to the exam in March.

The other thing to keep in mind is that the PMBOK® may be over 750 pages, but the PMP exam is still 200 questions. The PMP exam has always been a little bit about a lot of things, and that isn’t changing. To the extent that the PMBOK® is a key source for PMP certification exam prep, the revised exam will now be a little bit about even more…which makes it even shallower and wider.

While I don’t think there’s reason to expect a significantly more difficult exam in March, I would recommend waiting until a couple of months after March and paying attention to informal feedback about the exam on LinkedIn and other social media. People will share their perceptions of the exam in social media groups which can be helpful as one prepares for the test.

How In The World Can I Absorb All These Changes?

First, note that there are three parts to the new PMBOK® Guide.

Part 1 includes the Introduction, Environment, Role of the Project Manager, and the Knowledge Areas. This is the vast majority of the book and goes into detail on the processes, inputs, tools and techniques, and outputs.If you are already familiar with the PMBOK®, you can probably keep track of where you are at while reading this section.

Part 2 If you are new to the PMBOK®, however, you might want to start with Part 2, The Standard for Project Management. This covers many of the same concepts in Part 1 but at a higher level. More importantly, this section goes through the processes by Process Group (PG) rather than by Knowledge Area (KA), which is helpful to understand what project managers really do (PGs), as opposed to what they know (KAs). The PMP exam is organized by PG rather than KA, so this is also a good resource for certification exam prep. Plus, the descriptions of the processes in Part 2 are described along with identification of the inputs and outputs only – without tools and definitions and descriptions of the inputs and outputs, making it less confusing for those not familiar with it.


Advertisement

Part 3 also contains helpful information that might be worth looking at before going into the weeds in Part 1. Previous editions of the PMBOK® included Appendix X1 with the new edition changes. However, in past editions, I was slow to get to the appendices because I wanted to get into the details. With this edition, assessing the enormity of the task quickly led me to these less “popular” sections of the PMBOK. Simply breaking it down will make it less overwhelming, easier to absorb, and will make and your training easier.

The appendices are extremely helpful. Here is a summary:

  • Appendix X1. If you want to know what the changes are from the Fifth Edition, they are handily captured in Part 3’s Appendix X1. Not only are the changes identified, but the rules around construction of the PMBOK® are listed here which is helpful. For example, “Outputs from one process should become an input into another process unless the output is a terminal output or embedded within another input such as project documents.” (page 640). That’s handy to know! This is discussed in Part 1, but it is easier to catch in Part 3.
  • Appendix X3, X4, and X5 are very helpful in their summary presentation of information that is included at the beginning of each KA chapter. Specifically, X3 goes into how the project life cycle (adaptive, iterative, hybrid, etc.) impacts the processes described in Part 1, but it does so by Process Group. Again, this is helpful from the standpoint of understanding how project management really works.
  • Appendix X4 and X5. These include all the Key Concepts that are presented at the beginning of each KA in Part 1. And Appendix X5 includes all the Tailoring Considerations needed for adaptive, iterative, and other life cycles that were identified at the beginning of each KA in Part 1. It is very helpful to have these sections consolidated in one place to review together, as opposed to reading the Key Concepts and Tailoring Considerations specific to each KA one chapter at a time.
  • Appendix X6 presents a matrix summarizing which process utilizes each tool. It includes a reference guide for all the Tools and Techniques described in Part 1. Throughout Part 1, the tools are defined and described in detail the first time they are mentioned, then subsequent inclusions of the tool reference the original section where it was defined. Getting a sense of where and how the tools are used can be challenging. Appendix X6 shows where to find the detailed description of each tool. This makes it easy to look up where the tool is defined and where it is used.

Overall, even for those of us who have been steeped in PMBOK-ese for many years, this new edition is a lot to digest. Taking a little time to assess how it’s organized yields a better approach to understanding it.

I’d love to hear what your plans are for certification and your exam experience. Good luck!

The New PMBOK® Guide – What It Means for PMP Certification and More – Part 1

Here we are on the eve of another Project Management Institute Project Management Professional (PMP)® exam change following release of PMI’s new edition of the Guide to the Project Management Body of Knowledge (PMBOK® Guide).

This is the first in a two-part article in which I highlight some changes to the PMBOK® Guide. In the second part, I will suggest an approach to digesting the new version and share some thoughts about the exam changes.

PMBOK® Guide – Sixth Edition – What’s New

First, the changes to the processes and how they are organized is not changed substantially. A couple of processes have been renamed to create better consistency, and a couple of new processes have been added. But the overall structure with Knowledge Areas (KA) and Process Groups (PG) is the same. To be sure, details with inputs and outputs have been modified, but that would make for some very tedious reading, so I will talk about more interesting changes.

Three new sections are included at the beginning of each KA: Trends and Emerging Practices, Tailoring Considerations, and Considerations for Agile/Adaptive Environments. Each KA now addresses these topics with specifics pertinent to that KA.

Trends and emerging practices include tools like earned schedule in the Cost Management KA, which is not a new practice, per se, but is something that wasn’t mentioned in the PMBOK® Guide – Fifth Edition. Another example is use of multiple contractors and standard contract forms amenable to large, international megaprojects in Procurement Management. The idea of self-organizing teams is identified as an emerging practice in Resource (formerly called HR) Management. An expanded the view of who a stakeholder is and involving all team members in the effort to engage stakeholders is a trend in the Stakeholder Management KA.
Tailoring considerations make explicit what was more subtly implied in previous PMBOK® Guide editions. Questions help define how to make these processes work given the uniqueness of the organization such as constraints and stakeholders. For example, regarding Communications Management, how many languages are used among project team members, and are the team members geographically distributed? How much certainty is there around the requirements and how will that impact Scope Management processes? How will project size and complexity impact Risk Management processes?

Advertisement

The idea of tailoring isn’t new to the PMBOK® Guide, but inclusion of these sections with questions specific to each KA brings tailoring to the fore and makes the document feels much more like the flexible framework that it is, and much less like a prescriptive methodology that it is often misunderstood to be.
Considerations for Agile/Adaptive Environments is the third new section in each KA chapter. These high-level, brief sections provide project lifecycle context for understanding the processes. The impact of uncertainty on the processes and the benefits of doing things like chunking work and getting regular feedback are touched on in these sections. This brief section is enough to keep the project type in mind for the reader who is evaluating how to apply the processes and tools. Of course, the details pertaining to projects in an adaptive environment are now covered in The Agile Practice Guide, developed in collaboration with Agile Alliance, which now ships with the PMBOK® Guide – Sixth Edition.

In addition to those new sections, some old concepts get new emphasis and some new concepts and artifacts appear. The role of the project manager, for example, gets emphasized more than in past editions. The groundwork for this was laid years ago with PMI’s Talent Triangle™. Leadership skills and soft skills like navigating politics to get things done get more attention. Also, business documents including the project business case and project business management plan get addressed and are springboards for emphasis on making sure that projects are aligned with the business and delivering business value.

Overall, I think the PMBOK® Guide has become more consistent with each revision. In addition, the diagrams are much cleaner and most are easier to understand. The grey-colored pages are not particularly pleasant to read, although I appreciate that it is due to preventing illegal copies and protecting intellectual property.

Whatever you have to say about it, there is no disputing that it continues to grow. It is now a whopping 756 pages long! My next article will suggest an approach to digesting the new PMBOK® Guide edition.

In the meantime, I’d love to hear what your thoughts are. What do you like or dislike about the PMBOK® Guide – Sixth Edition?