I would like to know whether there are any best practices/methods to help decide whether a project should be done using the agile methods or traditional or hybrid method? Saving Changes...
Check out PMI's Disciplined Agile Toolkit: Choose Your WoW (way of working). It has some very well thought through criteria and flow charts.
It includes the traditional predictive "waterfall", continuous improvement, Scrum/sprints-based and others. The DASM certification is primarily about how to choose your WoW based on the context of your project rather than focused on any one delivery approach. Saving Changes...
I'd doubly echo Keith & Rami's support for Disciplined Agile. You also do have a profiling chart at the back of the Agile Practice Guide (free for PMI members) which covers the factors to consider when deciding which approach might be a better fit.
However, the key is to remember that purely predictive and purely adaptive projects are the exception, not the norm. The vast majority of projects will borrow elements from both.
PMI offers certifications such as the PMI-ACP (Agile Certified Practitioner) and PMP (Project Management Professional), which cover different project management approaches.
Agile, Waterfall, or Hybrid approaches should be based on a careful evaluation of these factors, as well as the specific needs and characteristics of the project and the organization.
PMI suggests on the project management approach as follows
Project Requirements
Project Size & Complexity
Stakeholder Involvement
Budget & Time Constraints
Organizational Culture & Capability
Risk Tolerance & Resource availability
Regulatory & Compliance Requirements if any Saving Changes...
I think this is like asking, ‘Is there a best way to cut a watermelon?’ There is no definitive answer to whether to use the waterfall or agile method in project management. If you want to master the art of cutting, the only way is to keep learning and explore its realm. The more knowledge you gain and the more experience you accumulate, the better equipped you’ll be to decide how to cut a watermelon for different purposes, such as party decorations or a casual dinner. PMBOK provides knowledge, yet the field of project management encompasses more than what is outlined in PMBOK itself. While PMBOK offers insights into some of the best practices, we, as humans, need to learn how to apply this knowledge dynamically in the ever-changing world of project management, rather than thinking like programmed robots.
Keep learning, keep exploring.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The problem is the big understaidng that it is outside there. Unfortunatelly the PMI itself contributed to that. Approach is totally independent of the life cycle and method you will use. For example, you can apply agile approach using any type of life cycle, including waterfall (adding to that most of the people confuse waterfall with sequential). On the other side, agile is not software related. The good news: what you are asking for is an accountability of the business analyst. if you take the documentation related to business analysis developed by the PMI you will find a process related to it. Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
It is also worthwhile to look at the broader project context (not a PMI recommendation though)
What project approach is well-known to the team? (If you are an expert with a hammer, everything looks like a nail.) Otherwise, you need to train the team first or hire consultants. It is also easier to adopt a well-known approach.
Which one is comfortable for the sponsor, the customer, the PMO, compliance authorities, and other key (influential) stakeholders?
Community Champion
