Tag Archives: Waterfall

Busting the myth of Agile for most projects, most of the time – 2

This is the third article on Agile.

  1. The first one covered a discussion on LinkedIn and summarized the key points discussed.
  2. With the second article, we started to demystify the concept that Agile is for most projects most of the time. In this second Article, we highlighted the overview mission of the Agile Manifesto.

Today, we will start covering the various principles, or at least one of them. With each post, we will explain why we think Agile does not work for capital projects and possible other non-software development projects. Continue reading

Do we need agile or Agile? Updated

This is an update from an earlier post. In this update, I will focus only on the comments and other related information.

On 21 March, I started the following discussion on LinkedIn

We keep hearing about the PMBOK Guide sixth edition and that Agile is in every knowledge area. That brings two questions:

  1. Is Agile for ‘most projects most of the time’ and if not, then why is it in the PMBOK Guide in every knowledge area?
  2. If it is ‘most projects most of the time’ and it belongs to the PMBOK Guide, then would we still need PMI-ACP or would the PMP covers the Agile Principles?

Your thoughts?

Continue reading

Busting the myth of Agile for most projects, most of the time – 1

First a disclaimer,

I am not an Agilist

I am not an expert in Agile

My core experience is not software development although I have a project in this area now but as a business and project owner and not an IT guy (developer – service provider ).

I do have three decades of project management experience, mostly on capital projects but also with exposure to numerous other sectors.

So, I write this post with the above in mind – read at your own risk 🙂

Continue reading

CAMMP™ or Agile?

This topic is part of a chapter in an upcoming book

There has not been any significant mention of alternative approaches such as Agile, Scrum, iterative, and incremental in this book so far. The main reason for this is because the CAMMP™ Model is an adaptive model, which can incorporate Agile, Scrum, or Incremental principles. The author does not believe in Agile or Scrum as standalone approaches or methods for managing a project end-to-end from a project owner perspective.

Here is why! Continue reading