Shams UI Islam HaleemPP Technical Support Engineer Specialist| Saudi Electricity CompanyKarachi, Pakistan
Hello professionals;
I am exploring agile practices and getting impression that Agile Alliance basically adopted that approach or "methodology" for the software development (product) where entire requirements at initial stage are, sometimes, uncertain.
I wonder why PMI include agile approach in all three domains (People, Processes and Business environment). I am of the view that agile approach (adopted) is already considered in the previous framework as Adopted life cycle.
It is clear that Agile is not a methodology, rather it is a philosophy or mindset!
Secondly, what is the difference between 'be agile' and 'being agile' in project management?
If you are referring to the PMP exam and the 50/50 balance of adaptive and predictive content across the domains, I'd suggest that it is not just the life cycle aspects of adaptive delivery that they will test you on, but also the mindset, values and principles side of agile which would fall within the People domain, and perhaps the applicability or the need to tailor agile approaches in specific types of business contexts.
I don't see a different between "be" or "being" agile - the important thing is to recognize that agile is an adjective, not a noun.
Kiron Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
I am with you Shams,
the PMBoK Guide always (since 1996) embraced and supported agile concepts, indeed the interdependencies of the PM process groups are cyclic and embrace 'progressive elaboration' of artefacts.
The process groups do not though represent a lifecycle, they describe merely the PM work, while lifecycles describe the work of the people working on the product. Many small SW projects do not allow to distinguish between PM and specialist work, and so we have many SW PMs who think agile is a better way.
As to your second point, I read 'be agile' as an imperative, a demand to become agile, as you hear it from the agile community, their instructors, consultants and consequently your management if they bought it.
'Being agile' for me means you think you are already agile, I would argue it is an illusion of a stable state which in itself is not agile. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
