Skip to main content


» Agile Project Management

The 5 Vital Relationships That All Agile Leaders Need (part 2)

In my previous post, I introduced the first 3 of 5 relationships that I consider vital for Agile Leaders, or leaders in any context. This post contains the fourth and fifth relationships.

The 5 Vital Relationships That All Agile Leaders Need (part 1)

Success as an Agile Leader is not about Working Harder

If you find yourself working harder than ever but not getting the results you want, perhaps more hard work is not the answer. Leaders today - Agile Leaders or otherwise - need to do more than simply work hard; they need leverage. That leverage comes from building relationships.

The Myth of the Project Manager in Agile Project Management

Between Santa Claus, Big Foot and the Agile Project Manager, which exists? Few people argue for the existence of Big Foot or Santa Claus, though most believe that Agile Project Managers exist. I would contend that none of them exist, especially the Agile project manager. (BTW we used a photo of a Wookie for Big Foot since all the pictures we had of Big Foot were blurry.)

Avoid Agile Shortcuts and Half Measures

We Need an Agile Shortcut or Hack

Project Managers Still Don't 'Get' Agile

I recently published the article below on the Project website (see Project Managers Still Don't Get Agile).  The point that I was trying to make is that while some project managers do understand and apply agile approaches, most project managers don't understand it. They don't want to understand it, and they actually undermine Agile adoption in their organizations.

Are Hybrid Agile Project Management Approaches Effective?

It's interesting to me that the main people who talk about using hybrid agile project management approaches are traditionally trained project managers. They believe there is a special blend of waterfall and agile techniques that will yield better results than either approach alone. They want to take the best of both worlds. I think they are misguided. They may get better results than using waterfall alone, but are unlikely to improve on a more pure agile adoption. They won't get the business agility that their organization needs to compete.

Agile Projects are More Successful than Traditional Projects

Agile projects are more successful than waterfall projects. There, I said it. And I have the statistics from the Standish Group to back it up.

I’ve been a follower of the Standish Group Chaos Studies for a long time. The Standish Group has conducted surveys of IT project success and failure rates every 2 years since 1994. Initially, the statistics were really bad with IT project success rates measured at less than 20%. Thankfully things have improved, though not much. Project success rates for technology projects are still pretty low.

Lessons Learned for Traditional Projects Are Still a Waste of Time

Over the last few months I have been writing about how to improve team retrospectives.  This has been mostly focused on Agile teams.  Recently I've been asked to facilitate a "retrospective" for a traditional project.  I remembered that a few years back, I wrote about why I felt that traditional lessons learned for projects were a waste of time.  My thinking on this topic is still the same - I still feel like those traditional lessons learned activities are a huge waste of time.

Why Agile Projects are Better

As you have probably noticed by now, I am a huge fan of Agile approaches and ways of working. This post is about some of the key aspects of Agile that I really like.  These 12 characteristics really highlight the key benefits of Agile methods, and how they relate to some of the areas of concern I had when leading traditional projects. I hope that you will find them useful as well. 

1. Success