Last month I did a 20-minute overview of my new Beyond Agile book for the Washington D.C. Lean-Agile MeetUp group hosted by Sanjiv Augustine.

I outline how Beyond Agile grew from studying high-performing teams and trying to distill what they did differently than most other teams. In the video, I cover Agile Myopia, Buffet Syndrome and the need to drop agile processes when they no longer bring enough value to warrant their use.

I would like to thank Sanjiv and the entire team at LitheSpeed for hosting me and allowing me to share this video with you here.

Anyone interested in my Beyond Agile book can get a paperback or electronic version here.

I am excited to announce my new book “Beyond Agile: Achieving success with situational knowledge and skills“ is launching. It is available now from RMC in paperback or electronic form here. This post explains the name and motivation for the book. Future posts will profile the content.

Background

Since helping create DSDM in 1994, I have been working on agile projects for 27 years. In that time, I have personally been a member of around 30 teams, coached and consulted with about 400 organizations and taught agile to over 2,000 team leads and project managers worldwide. Statistically, most were around average, a few were really dysfunctional, and less than 10 were exceptionally productive.

Problems

Around 8 years ago, I noticed many capable teams were adopting agile but still not being very productive. They had embraced the mindset and were doing all the right things, but success still eluded them. As someone who had dedicated their career to spreading the word about agile and helping organizations adopt it, this was extremely concerning for me. What were they doing wrong? What was I doing wrong?

Researching Successful Teams

So I went back to study the small number of exceptionally productive teams to look at what they did differently. While they understood agile remarkably well, they did not emphasize its use. Instead, they used a clever mix of agile, leadership, emotional intelligence and industry-specific knowledge to get the work that needed doing today done.

Patterns and Results Emerge

Patterns emerged, and I explored further. Using these techniques, I was able to help organizations turn around struggling projects and programs. As a result, we outperformed expectations, delighted stakeholders and won a PMI Project of the Year award. One organization documented our approach and submitted it for tax credits in the Canadian research and development SR&D program. It was successful, and they received several millions of dollars in tax credits. The Beyond Agile Model was developed, and this book documents the components.

The Obvious, Non-Obvious Need to Remove Process

The Beyond Agile Model has agile at its core; it also layers in additional ideas while encouraging teams to discontinue practices that no longer add sufficient value. Since there are only so many hours in the day, focussing more effort on delivery requires dropping other activities - even if they are agile. It was obvious once I saw it. The most productive teams I studied spent more time delivering and less time on agile ceremonies and other tasks. The non-obvious part was learning what to drop since it varies from team to team, and the book explains the process.

In future posts, I will explain some of the core ideas. Until then, I just wanted to let you know the book is finally done and available here.

This article explains what a risk-adjusted backlog is, why they are useful, how to create one and how teams work with them.

What is a Risk-Adjusted Backlog?

A risk-adjusted backlog is a backlog that contains activities relating to managing risk in addition to the usual features associated with delivering value.

Agile projects typically prioritize the backlog based on business value or perceived needs. The Product Owner or business representative prioritizes the backlog elevating the highest value features to the top, so they get delivered first.

Taking an Economic View of Decision Making

Prioritizing based on business value is an example of the lean concept of 'Taking an Economic View of Decision Making.' In deciding which feature to develop first, those with the highest economic value are selected. Taking an economic view of decision making has a couple of advantages.

Dolphins are easier to track than submarines. They surface more often and are usually within view of where you last saw them. Subs, on the other hand, can disappear for months or years at a time, and it is difficult to tell where they have gone.

What does this have to do with project communications? Has Mike finally gone mad?

These are valid questions, so let me explain. Many traditional project management deliverables have agile alternatives. For instance, a product backlog is somewhat analogous to a work breakdown structure. A release roadmap contains many of the elements of a Gantt chart. Yet we rarely see agile communications management plans. Why is this?

Finished Netflix? Done with “doom-scrolling” social media? Maybe it’s time to gain those skills you have been putting off.

The expansion of online learning was booming before COVID-19 emerged. Now, with the rise of work from home and homeschooling, the switch to online study has been massively accelerated.

However, before enrolling in some uninspired port of traditional course content to an online platform, let's see what else is out there. What are the emerging trends and good practices? What can we look forward to seeing in the world of online learning for project managers?

Some people say we cannot manage what we cannot measure. I say we cannot solve what we cannot see, or at least visualize somehow.

Projects are problem-solving exercises. The entire project is one big problem. We might be building a new product; that's a problem to solve. Or we might be trying to create something well understood but within a challenging amount of time, to a tight budget, and demanding specification. Or we could be moving our organization forward through a change initiative. These are familiar project environments that are puzzles or problems to solve.

Then within this large problem environments, we have hundreds of everyday challenges to answer, too. "How are we going to manage without the installer today?" or "The pilot group has requested 400 changes, now what do we do?"

It’s easy to believe that work breakdown structures (WBS) have been around since the pyramids were built in Egypt, and that product backlogs are new inventions by youngsters in too much of a hurry to plan correctly. However, like most things, the truth is more complicated.

In 1957, the Program Evaluation and Review Technique (PERT) approach was created by the United States Department of Defense (DoD) and described organizing tasks into product-oriented categories. However, they did not use the term “work breakdown structure” or WBS until 1962 when DoD, NASA and the aerospace industry published a document about PERT that described the WBS approach.

Meanwhile, in 1960, Tom Gilb described his Evolutionary Value Delivery approach (or Evo for short) that is widely accepted to be a forerunner of agile approaches. Evo contains principles such as:

This is the third sample from my new Kindle book “Agile Illustrated: A Visual Learner’s Guide to Agility”. The book is a graphical introduction to the agile mindset and servant leadership behaviors for working with agile teams. If you missed the first two samples you can find them here and here.

Also, just in time for Christmas, Agile Illustrated is now available as a physical paperback book. So if you prefer to hold a physical book rather than read a Kindle book you can now get your hands on a copy. Or, if you would like to give a copy to a manager or executive who is unlikely to read a normal length book on the agile mindset and how to support agile teams then buy them a copy as a gift.

At just 88 pages and mainly pictures it is a quick read that explains the agile values, principles and servant leadership behaviors needed to support agile teams. Available from your local Amazon online store, the US link is here.

Today we will review Team Performance. The Team Performance domain includes Team Formation, Team Empowerment, and Team Collaboration activities. (Anyone taking the PMI-ACP exam should expect to see 18-20 questions on this topic.)

Here is a mindmap showing all the tasks, we will then review them one at a time.

 Team Formation

 Task 1 – Jointly create team norms

Here is the second sample from my new Kindle book “Agile Illustrated: A Visual Learner’s Guide to Agility”. The book is a graphical introduction to the agile mindset and servant leadership behaviors for working with agile teams. If you missed the first sample on the Agile Manifesto, you can find it here.

Today we will revisit the Declaration of Interdependence. A lesser-known cousin to the Agile Manifesto, the Declaration of Interdependence was created in a few years after the Agile Manifesto to describe how to achieve an Agile Mindset in product and project leadership. It describes six principles essential to agile project teams. We will review them one by one.

 1 – We increase return on investment by making a continuous flow of value our focus.

Amaze your customers; keep giving them what they ask for!

Over the next few weeks, I will be featuring samples from my new Kindle book “Agile Illustrated: A Visual Learner’s Guide to Agility”. The book is a graphical introduction to the agile mindset and servant leadership behaviors for supporting agile teams.

Let’s start with the Agile Manifesto:

The Agile Manifesto was created during a meeting in February 2001 that brought together a number of software and methodology experts who were at the forefront of the emerging agile methods. Let’s look at the values one by one.

Value 1 – Individuals and Interactions over processes and tools

While processes and tools will likely be necessary, we should try to focus attention on the individuals and interactions involved. This is because work is undertaken by people, not tools, and problems get solved by people, not processes. Likewise, products are accepted by people, scope is debated by people, and the definition of a successfully “done” project is negotiated by people.

What will help set up a project for success is an early focus on developing the individuals involved and an emphasis on productive and effective interactions. Processes and tools can help, yet projects are ultimately about people. So, to be successful, we need to spend the majority of our time in what may be the less comfortable, messy, and unpredictable world of people.

Value 2 – Working software over comprehensive documentation

This value speaks to the need to deliver. It reminds us to focus on the purpose or business value we’re trying to deliver, rather than on paperwork.

Thanks to everyone who downloaded my new eBook “Agile Illustrated: A Visual Learner's Guide to Agility” you made it #1 Amazon Hot New Releases for “Technical Project Management”, along with #1 Amazon Best Seller in “Computers and Technology Short Reads”, and even #1 Amazon Best Seller in “PMP Exam” - which is odd because it is not even about the PMP exam.

I am excited to announce a new eBook “Agile Illustrated: A Visual Learners Guide to Agility”.

It is a short, graphical overview of agile and agile team leadership published as an Amazon Kindle eBook.

Using mind-maps, cartoons, and short summaries it covers the agile manifesto, the declaration of interdependence for agile project management, and each of the 7 Domains and 60 Tasks covered in the PMI-ACP exam.

It is short and light read but a powerful study aid for anyone preparing for the PMI-ACP exam. It also serves as a great executive summary for instilling an agile mindset and teaching the leadership behaviors to serve agile teams. With over 70 illustrations, mind-maps and cartoons it engages spatial and visual memory making the points easier to recall and explain to others.

If you think in pictures and like to see how ideas fit together this will be a valuable resource.