Agile complements traditional project management? - but how?!

image source: http://goo.gl/FwSXFp

Agile doesn’t trade places with traditional project management which is centered around water-fall methodology. Hence Agile doesn’t counter against PMI®, long known for its project management credentials through PMP, rather it complements… Let’s get the insight on why do we recommend Agile. It is to be noted that PMI features PMI-ACP® as one of its flagship certification which is fast gaining grounds, if the traction is any indicator. We are one of the leading lights in knowledge and certification of PMI-ACP® and regularly conduct training and workshops on key locations around the globe.  Let’s move on to the narrative.

Cost/Schedule Creep…

Agile talks about how we can be adaptive for changes for the projects which doesn’t have clear scope or which has evolving scope. However Agile doesn’t address about how one should manage the cost/effort against the change and in nutshell Agile talks/encourages the changes of the scope, Cost, effort and in reality as the project runs based on the budget and cost in most cases.  Agile can complement within the schedule/cost however there needs a cap for the cost and schedule to avoid the major creeps on the same. PMI standards protect the projects from these variances or it gives us the better predictability on the same.

Big Picture Vs Progressive evolution

One should have big picture in mind which is very important to achieve the final goal. While agile emphasize on changes and adaptiveness, it doesn’t define the boundary wherein PMI plays a key role . We can be adaptive to changes as long as it is within the final goal of big picture. Without having final frame in mind, one cannot evolve in the right direction which means PMI gives you the right direction to evolve rightly. To my view without high level plan in hand, running the project in agile may never predict any time. We need a high level plan to assess ourselves on where do we stand in terms of goal achievements.

Agility within the project (Scope, Cost & Schedule) is always recommendable so that we always have grip on the project. Project should aim for success and that success is defined based on Scope achievement within agreed time and cost factors.