"There isn’t the best or worst project methodology for product development, how you can see every methodology has own pros and cons."

"It is a pluralistic iterative process combining aesthetic, art and science..."

— Coebus

The most compelling design solutions are ones that are simple, natural to use, and completely in tune with users' needs and experiences. Achieving these solutions in the design of technology products and/or e-business applications requires resources such as published research, following guidelines and standards, and involving users throughout the design process. Experience design is a user-centered process that provide guidelines for achieving these compelling designs.



The oldest and most popular project management methodology was first introduced in 1970 by Dr. Winston Royce. The need to outline this methodology arose with software development getting complex. A sequential methodology demands a clear outline of all the requirements before initiating the project, as there is no scope for correction at later stages. Thus, it is the most straightforward approach, and it became the reason for its huge success.

As suggested by the name, the project phases downward while taking input from the previous phase. All the phases in this model are interdependent, which leaves no room for error, resulting in distorted output at the end. This model comprises seven phases: Requirement Gathering, Analysis, Design, Implementation, Testing, Deployment, and Maintenance.

Use Cases

Small scale projects
Projects with clear and rigid requirements
Projects not complex in nature


Rigid and easy-to-follow structure.
Complete documentation
Ease of use


Risk factor
Heavy requirement gathering
No backtracking



Agile software development emerged in the 1990s but was officially manifested in 2001 by 17 software developers. It emerged when software development got too complex for the Waterfall model to handle. In contrast to the Waterfall model, it favored flexible approaches. With no heavy and rigid requirement gathering upfront, it was quite efficient as well.

It favored individuals over processes and customer collaborations over contracts, all due to the flexible approach. Hence, it became quite popular as it allowed small incremental changes with four major phases: Scan, Analyze, Respond and Change.

Use Cases

Projects with no fixed requirements
Projects that require a fast-paced and response schedule


Lower Risk
Customer Satisfaction


No rigid planning and documentation
Multiple collaborations


As suggested by the name, it combines two project management methodologies, namely Agile and Waterfall. Thus, it offers both worlds the best as it combines both methodologies’ flexibility and rigid structure to give an outright seamless experience.

Initially, requirement gathering is emphasized (a trait from the Waterfall model), which is later accompanied by flexibility (a trait from the Agile model) during implementation.

Use Cases

Middle-sized projects
Projects with moderate complexity and fixed budget


High flexibility
Progress tracking
Appropriate documentation


Lacks deliverable tracking.
Continuous administrative intervention
Require certain compromises.